Methodology
How we source, calculate, and present crime statistics across New Zealand suburbs and regions.
What we show
We present crime victimisations by suburb and region, normalised per 1,000 residents, along with trends across common time windows.
Why per 1,000
Raw counts can be misleading. Normalising by population helps compare areas of different sizes more fairly.
Safety Score
The Safety Score is a relative 0–100 percentile based on harm per 1,000 residents, using NZ-CHI harm weights.
Data sources
Monthly offence counts used for suburb and regional totals and trends.
Used to normalise counts and harm per 1,000 residents for fair comparisons.
Harm weights measured in prison-days, applied to offences to compute harm-based Safety Scores.
Calculations and definitions
Crime rate per 1,000
Crime rate is calculated as:
Where offence_count is aggregated over the chosen time window for the suburb or region.
Time windows
We compute common windows for trends and comparisons:
“As at” refers to the latest month included in the dataset.
Harm per 1,000 and Safety Score
Safety Score uses the NZ Crime Harm Index NZ-CHI v7.3. Each offence is assigned a harm weight measured in prison-days. We compute harm per 1,000 as:
harm_per_1k = (harm / population) × 1,000
Scores are relative percentiles per window. Higher score means lower harm relative to other suburbs.
Percentiles and stabilisation
To reduce the impact of extreme outliers, harm_per_1k is winsorised before percentile ranking:
safety_score = round((1 - percent_rank) × 100)
A suburb with zero harm in a window is treated as best-case for that window.
Population edge cases
Geography and grouping
Statistics are grouped to suburb and region using consistent boundaries. In some cases, the way data is reported or aggregated may not perfectly match informal suburb naming or local perceptions of suburb borders.
Offences are also grouped into higher-level categories to make charts and comparisons easier to understand. Exact groupings may evolve as official classifications or mappings change.
Update cadence and versioning
Monthly refresh
Data is refreshed monthly after Police releases and internal processing completes. “As at” reflects the latest month included.
Stable scoring runs
Safety Scores are computed from the same harm logic each run and tied to a weights version to keep results auditable and comparable over time.