If you open a UK crime map and a whole city-region looks almost empty, the usual reaction is that the area got safer. Often that is the wrong reading.

Street-level figures on data.police.uk are not a complete count of crime. They are the subset each force chooses to publish that month. When a force pauses or severely reduces publishing, the map goes quiet even if reporting and recording have not.

CrimeMapsUK treats that as a publication gap. This article explains how we detect gaps, why they matter, and which forces have months missing, using the official data.police.uk archive files for September 2021 to August 2026.

What a publication gap is

A healthy force series produces a fairly stable monthly volume of published street-crime records for years. A gap is when that volume collapses relative to the force’s own history.

Our rule of thumb (in code under apps.data.coverage):

That rule is deliberately blunt. It is meant to catch “used to publish tens of thousands a month, now publishes almost nothing,” not gentle year-to-year change.

A gap is not the same as:

A force can also send nothing at all for a month. The changelog then notes “crime data not provided”, and that month is missing from the files. We show a missing month as unavailable, not as zero, and a report gives no trend comparison across it.

Why the map can mislead

Hex maps and force totals only show what was published. In a gap:

Greater Manchester is the clearest public example. The current data.police.uk archive files hold no street-level crime from Greater Manchester Police for any month from September 2021 to August 2026 except August 2022, whose file holds 14 records, all mapped to one street in Leicester. So the map shows almost nothing for Manchester, Salford, Bolton, Stockport and the other Greater Manchester boroughs.

Forces with missing months (crime data)

This snapshot comes from the official data.police.uk archive files for September 2021 to August 2026. In those files, three forces have months with no street-level crime:

Force Months with no street-level crime What data.police.uk says
Greater Manchester Police Every month from September 2021 to August 2026 except August 2022, whose file holds 14 records “Currently no crime, outcome or stop and search data is available”
British Transport Police February 2025 to August 2026 Monthly “crime data not provided” notes from March 2025
Gloucestershire Constabulary February 2026 to August 2026 “Crime data not provided” for each of those months

Every other force has a street-crime file for every month in that window. In the most recent twelve months, each published at least three quarters of the volume of its own busiest earlier year, judged by the size of its published files.

The methodology page lists the forces with missing months from the data we have loaded, and it updates after each fortnightly data load.

Correction, 30 October 2026

Earlier versions of this article listed Northumbria, North Yorkshire, Northern Ireland and South Wales as forces whose data stopped in 2023. They said British Transport Police had no street-level crime after early 2023, when its files run to January 2025. They also listed Cleveland, Thames Valley, West Midlands, Hampshire and Isle of Wight, Cumbria, Nottinghamshire, Lancashire, Kent, Norfolk and Dyfed-Powys as publishing far below their own history from about May 2023. All of that was wrong, and the mistake was ours, not the forces’. We had loaded those months through the data.police.uk street-crime API, which is searched by map area. Our searches left out British Transport Police, North Yorkshire and Northern Ireland entirely, filed some crimes under the force whose area they fell in rather than the force that reported them, and stored far fewer records than several forces had published. The official monthly archive files hold complete files for all of those forces. In October 2026 we reloaded those months from the archive files, and new months now load from them too.

Are there public explanations?

Greater Manchester is the well-documented case. Local reporting and HMICFRS material describe long-running problems after GMP’s iOPS / records-management change: the force has often been unable to supply a clean street-level feed to data.police.uk even while other Home Office returns continued. The data.police.uk changelog has carried repeated “crime data not provided” notes for GMP, and GMP has said publicly that aligning its systems to the police.uk return is complex.

For British Transport Police and Gloucestershire, the changelog carries a note for each missing month: “crime data not provided… The force will provide a data refresh as soon as possible.” It gives no reason. A refresh can arrive months later in a newer archive file, and our monthly load picks up a force’s file for an earlier month when it appears. Until a force publishes a reason, the honest reading is simply: those months are missing from the open data; we do not know why from the public record.

What this does not mean

For the wider limits of the source (approximate locations, outcomes, reporting), see the methodology page and why we don’t predict crime.

How to check an area that might be affected

  1. Open the relevant force area page and look at the monthly chart, not just the latest total.
  2. Compare recent months with 2021-2022 (or earlier) for the same force.
  3. If the line falls off a cliff and never recovers, treat the map as incomplete publishing, not as a safety score.
  4. For a single postcode, try the free check on the reports page - if we detect a gap, we say so plainly instead of selling a misleading PDF.

Will this list change?

Yes. Forces resume, thin out, or pause again. The gap rule is re-evaluated from the monthly series whenever derived stats are rebuilt. This article is a readable snapshot for October 2026, not a permanent league table. The methodology page keeps the current list.

If you need the precise definition used in product decisions (district publishing, report sales), the implementation lives in the coverage helper documented from the methodology page.