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.
+1.1% by the latest quarter-on-quarter step.
+37600% 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 Windsor and Maidenhead as a pressure leader, rate outlier, contingency site, or three-pathway case without leaving the page.
Windsor and Maidenhead ranks 7 of 64 in South East; Portsmouth currently leads this regional measure.
Windsor and Maidenhead ranks 97 of 361 nationally on supported asylum.
Windsor and Maidenhead ranks 5 of 64 in South East; Reading currently leads this regional measure.
Windsor and Maidenhead ranks 66 of 361 nationally on supported asylum rate.
Windsor and Maidenhead ranks 4 of 64 in South East; Mid Sussex currently leads this regional measure.
Windsor and Maidenhead ranks 26 of 361 nationally on contingency accommodation.
Windsor and Maidenhead ranks 12 of 64 in South East; Buckinghamshire currently leads this regional measure.
Windsor and Maidenhead ranks 109 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.
377 people are on asylum support here, with a rate of 23.72 per 10,000 residents. 358 are in contingency accommodation.
This combines supported asylum, Homes for Ukraine arrivals, and Afghan programme population, representing 0.58% of the local population.
No named current hotel site is attached to this area in the starter ledger yet.
These strips show where Windsor and Maidenhead 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.
Windsor and Maidenhead ranks 97 nationally and 7 in South East for supported asylum count, placing it around the 74th percentile of local authorities by volume.
The supported asylum rate here is 23.72 per 10,000 residents, around the 82th percentile nationally. This matters because smaller places can carry a sharper load than bigger city totals imply.
358 people are in contingency accommodation here, around 95% of the supported asylum population and roughly the 93th 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.
Windsor and Maidenhead sits 97 nationally by supported asylum count and 7 within South East. The raw volume is 377, but the rate of 23.72 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 524. 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 Windsor and Maidenhead 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.