NorthMock · Developer and QA utility
Nunavut Address Generator
Generate random Nunavut (NU) Canadian test addresses with fictional contact details for QA and sandbox forms.
Address workspace
Free to use. No account needed.Loading test data…
Your test record
- Name
- —
- Gender
- —
- Safe phone (national)
- —
- Safe phone (E.164)
- —
- Real assigned prefix line number masked
- —
- Address line
- —
- City / municipality
- —
- State / province
- —
- ZIP / postal code
- —
Fictional contacts. Reserved 555 test numbers.
Location preview
Google MapsGoogle Maps loads automatically when the generated address is ready.
- Full address
- —
Generated batch
The first record is displayed above.
| # | Name | Phone | Location | Full address | Inbox |
|---|
Local export: CSV and JSON files are assembled in this browser from the current session. The tool does not upload an export file or save a batch history.
Random Nunavut address generator for testing
Use this Nunavut address generator when a form, checkout, CRM, or onboarding test needs region-formatted data. Canadian test records use a street, municipality, two-letter province code, and alphanumeric postal code. The current pool includes locality labels such as Iqaluit, Cambridge Bay, Rankin Inlet, and every new result keeps NU selected.
Nunavut address coverage snapshot
The current generator pool contains 60 deduplicated Nunavut address records. Automated format parsing found 3 normalized locality labels; the most frequently represented labels are shown below.
Coverage interpretation: Iqaluit is the largest locality group with 54 of 60 records (90%); X0A is the leading FSA with 54 records. Use a batch to exercise the pool's actual variation, but do not interpret these fixture shares as population or postal-volume statistics.
Most represented localities
The five most frequent normalized locality labels in this snapshot are listed with their record counts.
- Iqaluit54 records
- Cambridge Bay3 records
- Rankin Inlet3 records
Nunavut postal FSA prefixes in this pool
Frequently represented three-character FSA prefixes are X0A, X0B, X0C. They describe the validated generator pool, not a population ranking or a complete postal directory.
- X0A54 records
- X0B3 records
- X0C3 records
Observed locality and FSA pairings
These are the five most frequent locality and three-character FSA combinations parsed from the current Nunavut generator pool. They help QA teams choose internally consistent city and postal-prefix fixtures without implying complete postal coverage.
- IqaluitFSA X0A · 54 records
- Cambridge BayFSA X0B · 3 records
- Rankin InletFSA X0C · 3 records
Snapshot: August 12, 2026. 60 of 60 records passed the expected NU format and Canada Post FSA allocation check (100%). This check does not prove street-level deliverability, and no individual address is published in this coverage summary.
Nunavut address format for test forms
Use this field order when a checkout, CRM, or onboarding sandbox needs a sample Nunavut address. It shows the expected Canada layout without publishing a source address or creating a complete identity.
Field template
[Street number] [Street name]
Iqaluit, NU [A1A 1A1 postal code]
Canada
What each field should contain
- Address line 1
- Street number and street name; add a unit only if the form supports a separate apartment or suite value.
- Municipality
- Use a locality represented in the regional pool, such as Iqaluit, Cambridge Bay, Rankin Inlet.
- Province
- Use the two-letter region code
NU. - Postal code
- Use the Canadian letter-number-letter, number-letter-number pattern with a space in the middle.
- Country
- Use Canada.
Locality note: Use one of the locality labels represented in the current Nunavut pool, such as Iqaluit, Cambridge Bay, Rankin Inlet.
Need country-wide field rules and edge cases? Read the Canadian address format and examples guide.
Template only: This format example is not a deliverable mailing address. Generate a record above for legitimate development and QA testing, and do not use it for mail, impersonation, or identity verification.
How to test forms with Nunavut data
- Keep the region fixed. This page sends
NUto the API so every generated address remains in Nunavut; choose 1, 5, 10, or 25 records for a single test or a small batch. - Validate the postal field. Expect a postal code and the standard Canada address layout described above. The current pool includes locality labels such as Iqaluit, Cambridge Bay, Rankin Inlet.
- Use the safe phone value. Copy-ready numbers use a local 867 area code with the reserved 555-01XX range.
- Exercise verification flows. Open the generated gravityengine.cc inbox in a new tab without using a personal email account.
Nunavut test-data questions
Are these complete real identities?
No. Names, addresses, phone values, and emails are assembled independently for legitimate QA and development workflows.
Will the phone number call a real subscriber?
The copy-ready number uses the reserved 555-0100 through 555-0199 fictional range. Assigned local prefixes are shown separately with the subscriber digits masked.
Can I generate another Nunavut record?
Yes. Select “Generate another” to request a new record while preserving region code NU.
Designed for legitimate testing
- The complete copy-ready phone number uses a local area code and the reserved 555-0100 through 555-0199 fictional range.
- The real-prefix preview comes from current NANPA or CNA assignment data; its final four digits stay masked because they may belong to a real subscriber.
- Email addresses use gravityengine.cc and link to the matching disposable inbox.
- Fictional names are independently assembled from 400 aggregate SSA popular first names and 1,000 US Census surnames, providing 400,000 gender-tagged combinations without copying complete identities.
- Supplemental address data includes © OpenStreetMap contributors, data made available through OpenAddresses, information licensed under the Open Government Licence – Yukon, and public sector datasets under the City of Yellowknife Open Data License v1.
- Generated records are intended for development, demos, and sandbox validation only.
- Do not use generated data to impersonate people, receive physical mail, or bypass identity checks.
Full details are available in the NorthMock test-data methodology.