Official local-authority snapshot as at 2025-12-31. This page keeps live route data and local hotel evidence on one place-level surface so pressure can be read in context.
Quarter-end place series to Dec 2025. All visible points are official quarter-end values.
-6.4% by the latest quarter-on-quarter step.
+33800% from the first visible point to Dec 2025.
The visible trend line is built entirely from official quarter-end supported asylum values in the local area series.
Switch metric and comparison frame to read Reigate and Banstead as a pressure leader, rate outlier, contingency site, or three-pathway case without leaving the page.
Reigate and Banstead ranks 9 of 64 in South East; Portsmouth currently leads this regional measure.
Reigate and Banstead ranks 107 of 361 nationally on supported asylum.
Reigate and Banstead ranks 7 of 64 in South East; Reading currently leads this regional measure.
Reigate and Banstead ranks 77 of 361 nationally on supported asylum rate.
Reigate and Banstead ranks 8 of 64 in South East; Mid Sussex currently leads this regional measure.
Reigate and Banstead ranks 59 of 361 nationally on contingency accommodation.
Reigate and Banstead ranks 20 of 64 in South East; Buckinghamshire currently leads this regional measure.
Reigate and Banstead ranks 130 of 361 nationally on three-pathway total.
The local picture only becomes legible when supported asylum, contingency use, Ukraine arrivals, and Afghan programme population are kept distinct.
339 people are on asylum support here, with a rate of 21.3 per 10,000 residents. 187 are in contingency accommodation.
This combines supported asylum, Homes for Ukraine arrivals, and Afghan programme population, representing 0.51% of the local population.
No named current hotel site is attached to this area in the starter ledger yet.
These strips show where Reigate and Banstead sits in the national distribution for the most important place-level pressure measures.
National distribution across all local-authority rows.
Rate per 10,000 residents.
Hotel and other contingency placements.
South East is highlighted so this place can be read inside the wider regional supported asylum map.
These cards translate the data into the most defensible local claims the site can make right now.
Reigate and Banstead ranks 107 nationally and 9 in South East for supported asylum count, placing it around the 71th percentile of local authorities by volume.
The supported asylum rate here is 21.3 per 10,000 residents, around the 79th percentile nationally. This matters because smaller places can carry a sharper load than bigger city totals imply.
187 people are in contingency accommodation here, around 55.2% of the supported asylum population and roughly the 84th percentile by contingency count.
No named current site or unnamed acknowledged count is attached to this area yet, which is itself a reminder that absence of public evidence is not evidence of absence.
The area profile should show route composition, not force users to infer it from a single asylum count.
The regional ranking matters because high-pressure areas compete for attention with their nearest peers, not just with the national top ten.
Reigate and Banstead sits 107 nationally by supported asylum count and 9 within South East. The raw volume is 339, but the rate of 21.3 per 10,000 residents gives a cleaner sense of local intensity than the headline count on its own.
Homes for Ukraine is the largest non-asylum pathway in this area at 431. That matters because the local story is not just about one route family; it is about how asylum support, humanitarian schemes, and historic resettlement stack together in one place.
South East as a whole currently carries 7,472 people on supported asylum, with a weighted regional rate of 7.75 per 10,000 residents. This page puts Reigate and Banstead inside that wider regional pressure field instead of treating it as an isolated case.
Place pages should merge live route data with the named and unnamed hotel evidence already on the public record.
That does not mean the area has no hotel use. It means the ledger has no publishable public evidence row attached yet.