Format guide
How do you write a Russia address?
Domestic forms often use a single line: `6-digit indeks, g. City, ul./pr./per. street, d. house`, optional `k.`/`str.`, then `kv.` Apartment. Envelope order usually puts street and apartment first, then city and federal subject, then the 6-digit indeks and country. Moscow and Saint Petersburg are federal cities (city name = federal subject). Samples are Cyrillic with a Latin transliteration line for international form testing only—not official romanization.
Typical field order
| indeks (6) | 6-digit pochtovyy indeks; validate as `^\d{6}$` |
|---|---|
| Federal subject | oblast / krai / republic or federal city — not a US-style State |
| g. city | populated place; federal cities share the subject name (Moskva, Sankt-Peterburg) |
| rayon | district; indeks prefixes stay bound to the city’s district list |
| ul. / pr. / per. | ulitsa / prospekt / pereulok |
| d. / k. / str. / kv. | dom / korpus / stroenie / kvartira |
| Cyrillic vs Latin | samples include Latin transliteration (ul./d./kv./g.) for international forms only |
| Phone | +7; Moscow often 495/499, Saint Petersburg 812 (fictional 555 test block) |
Postal codes
Russian postal codes (pochtovyy indeks) are 6 digits (e.g. 101000, 125009, 190000). This site binds city → rayon → prefix pools (e.g. Arbat prefers 119xxx/121xxx). Samples are fictional and not a Pochta Rossii endorsement.
Form testing checklist
Accept postcodes as `^\d{6}$` strings; keep Cyrillic UTF-8 length; use RU / Russia / RUSSIAN FEDERATION; cover +7 495, +7 499, and +7 812. For more address form cases, see US address form test cases
Typical use cases
Useful for validating `^\d{6}$` as a string, Cyrillic UTF-8 field length, country RU / Russia / RUSSIAN FEDERATION, and +7 phones (Moscow landlines often +7 495 or +7 499; Saint Petersburg +7 812—this site uses a fictional 555 block). Do not use for shipping, registration, payment, or identity checks.
How to use test data
In development you can use these samples to check field length, line breaks, international characters, and responsive layouts. For payment, identity, logistics, or compliance flows, use official sandbox data from your provider—do not submit these samples to live systems.