Households in temporary accommodation
Central Bedfordshire · 31 December 2025
On 31 December 2025, 259 households in Central Bedfordshire were living in temporary accommodation — 148 of them with children.
Read from MHCLG’s detailed local authority tables, table TA1, in the vintage we archived on 11 August 2026.
259
households
In temporary accommodation in Central Bedfordshire on 31 December 2025
310 children were living in those 259 households.
That is 2.0 households in temporary accommodation for every 1,000 households in the area, of which there are about 130,444. The rate across England was 5.5.
That is the 25th-highest rate of the 60 unitary authorities in the table.
That is 1 more than on 30 September 2025, when it was 258.
Rate among the unitary authorities, October to December 2025
- … 14 councils between
- out of 60 unitary authorities in the table
Households in temporary accommodation for every 1,000 households in the area, which is the publisher’s own figure. Councils are compared with councils of their own kind — the table’s only classification is the ONS code — because a London borough beside a rural district is arithmetic without meaning. Councils that did not return data are absent from the ranking rather than counted as nil.
Every quarter we hold
| Quarter | Households | Of those, with children | Children | Per 1,000 households |
|---|---|---|---|---|
| 2024 Q2 | 282 | 145 | 309 | 2.3 |
| 2024 Q3 | 245 | 135 | 305 | 2.0 |
| 2024 Q4 | 237 | 130 | 290 | 1.9 |
| 2025 Q1 | 230 | 132 | 290 | 1.8 |
| 2025 Q3 | 258 | 152 | 313 | 2.0 |
| 2025 Q4 | 259 | 148 | 310 | 2.0 |
April to June 2025 is missing from this table. MHCLG published that quarter in a spreadsheet format this pipeline cannot read, so we do not hold it. It is a gap in our record, not a quarter in which nothing was counted, and any comparison on this page names the quarter it actually used.
Each row is a count on one day at the end of the quarter, not a total for the quarter, and it counts households rather than people. A council that did not return data is shown as such; it is never read as nil.