Chinese test data is especially valuable because it exercises code paths that ASCII-only fixtures never touch: multi-byte character encoding, byte-versus-character field limits, family-name-first name order, and forms that must accept two different scripts. Below the generator you will find a practical reference to how Chinese addresses, postal codes, and phone numbers are structured, so you can check your validation logic against reality.
How a Chinese address is structured
Chinese addresses are written from largest unit to smallest — the reverse of Western convention. The sequence runs province (省), city (市), district or county (区/县), street or road (街道/路), street number (号), then building, unit, and room (楼/单元/室). A complete example: 北京市朝阳区建国路88号2号楼3单元502室 — Beijing, Chaoyang District, Jianguo Road No. 88, Building 2, Unit 3, Room 502. The four municipalities — 北京 (Beijing), 上海 (Shanghai), 天津 (Tianjin), and 重庆 (Chongqing) — sit at province level, so their addresses start directly with the city name; everywhere else the address opens with a province such as 广东省 (Guangdong) or 浙江省 (Zhejiang).
For international forms, addresses are romanized in pinyin and usually reordered small-to-large to fit Western fields: Room 502, Unit 3, Building 2, No. 88 Jianguo Road, Chaoyang District, Beijing. This creates the two-script problem that trips up many systems: the same address exists in Chinese characters and in pinyin, and software must decide which form to store, display, and validate. A form that rejects non-Latin input will lock out native users; one that assumes small-to-large ordering will mangle addresses pasted in the domestic format.
Six-digit postal codes
Chinese postal codes are exactly six digits with no separators. The first two digits identify the province-level region — 10 is Beijing, 20 is Shanghai, 30 is Tianjin — the middle digits narrow down to a prefecture or postal zone, and the final digits point to a local delivery office. Beijing city center is 100000 and central Shanghai is 200000. Validation is simple: exactly six ASCII digits. The bugs worth testing for are subtler — codes accepted with spaces or Chinese full-width digits pasted from other software, or a shared "postal code" field whose length check was written for five-digit US ZIP codes.
Chinese phone number formats
Mobile numbers are 11 digits and always start with 1, with prefixes running from 13x through 19x, allocated across China Mobile, China Unicom, and China Telecom. In international notation they are written with the +86 country code, commonly grouped 3-4-4: +86 138 0013 8000. Landlines use an area code plus a seven- or eight-digit local number: 010 for Beijing, 021 for Shanghai, 0755 for Shenzhen; the leading zero of the area code is dropped after +86. Numbers generated here follow these structural rules with randomized digits, which makes them ideal for testing input masks and libraries like libphonenumber — but they should never be dialed or used for SMS verification.
Why CJK test data matters
Chinese data stresses systems in ways Latin-only fixtures cannot. Each Chinese character takes three bytes in UTF-8, so a database column sized in bytes holds far fewer characters than its designer assumed, and legacy GBK-encoded integrations corrupt anything outside their character set. Chinese names put the family name first — in 王小明, the surname is 王 — with no space between family and given name, which breaks forms that demand separate first-name and last-name fields or a minimum name length. Sorting, truncation, and search all behave differently on CJK text, and only realistic fixtures will surface those bugs before users do.
Each generated record also includes a national ID number (身份证号) that follows the official 18-digit structure — six digits for the region, eight for the birthdate, three for the sequence, and a final checksum character that can be an X. The structure is correct and internally consistent with the generated birthday, but the number itself is random: it is not issued by any authority and does not belong to anyone, making it safe for testing checksum logic, input masks, and storage.
Frequently Asked Questions
Are these real Chinese addresses? +
No. Provinces, cities, districts, road names, and building numbers are combined at random. A generated address may coincidentally resemble a real place, but it is not taken from any database of real addresses or residents, and it is not guaranteed to be deliverable.
Can I use a generated address to receive parcels or verify an account? +
No. The data is for software testing, form validation, and demos only. It will not pass real-name or identity verification, cannot receive mail or deliveries, and using invented data to mislead a service or person may violate that service’s terms or the law.
Is the generated national ID number (身份证号) real? +
No. It follows the official 18-digit format — region code, birthdate, sequence, and checksum — so it will pass structural validation, but the digits are random. It is not issued by any government authority and does not belong to anyone.
Should I test with Chinese characters or pinyin? +
Both. Domestic users type addresses in Chinese characters in large-to-small order, while international forms expect pinyin in small-to-large order. Testing both scripts catches encoding bugs, byte-length limits, and layout issues that only appear with CJK text.