SINGLE STOREY SIDE AND REAR EXTENSIONS
37 BORRAS PARK ROAD, WREXHAM, LL12 7TE
Planning application coverage
PlanWire tracks 695 planning records for Wrexham County Borough Council, spanning 22 Jan 2018 to 31 Aug 2026. Search the underlying applications and source links through one monitored API.
Live near Wrexham County Borough Council? Set up a planning alert and get an email when an application is submitted close to your postcode. Building a product instead? The same records are available through the API.
Records tracked
695
History begins
22 Jan 2018
Latest dated app
6 days ago
Source checked
2 days ago
Latest cached dated application: 31 Aug 2026. Use API date filters for exact recent counts.
Recent application preview
Five recent dated applications. API responses include fuller machine-readable fields and pagination.
37 BORRAS PARK ROAD, WREXHAM, LL12 7TE
BRYN HAUL, 4 HILL STREET, NEWBRIDGE, WREXHAM, LL14 3JQ
STONEWAYS, 12 LITTLE ACTON DRIVE, WREXHAM, LL12 8DH
LAND ADJACENT TO LLEWELYN ROAD, VRON, TANYFRON, WREXHAM, LL11 3LG
CHURCH, CADNEY LANE, BETTISFIELD, WHITCHURCH, SY13 2LN
Local record profile
Wrexham County Borough Council is a focused local planning history, with 695 records tracked. The public record spans 2018 to 2026, so the page is useful for recent monitoring as well as historic checks around sites and addresses.
Authority context
Wrexham County Borough Council is a borough planning authority, with local applications normalised for search, alerting and API workflows.
Recent activity pattern
Wrexham County Borough Council has a cached latest dated application of 6 days ago. Use API date filters for exact recent counts when sizing local monitoring or alerting workflows.
Monitoring fit
Wrexham County Borough Council has cached latest-date coverage in this public summary. API users can combine council filters, date filters and freshness metadata for exact operational checks.
Freshness status
Latest dated application is 6 days ago.
Completeness signal
Latest checked, latest dated application and API source metadata are published with the council record. Document metadata is exposed where the source supplies it.
Machine-readable access
Use GET /v1/councils for coverage metadata and GET /v1/applications?council_id=wrexham for application records with an API key.