Current page call
Translate fire, rescue, and disaster-response sources into a practical public-access page.
7 source layers
2026-05-09 updated
Privacy matters
Public-safety intelligence
Thailand Fire and Rescue Data.
Fire and rescue pages should distinguish urban fire stations, disaster-response offices, wildfire layers, ambulance overlap, and rescue-foundation contacts instead of implying one universal rescue feed.
Before you book
Use the Safety page with the current trip checks
This safety page is not claiming a page-specific current score. Use it as the static guide, then check Today, route, and comparison pages before paying for anything hard to change.
Decision fields
A strong safety page says which part is police access, which part is crash risk, which part is emergency response context, and which part is only a slower statistical or protest signal.
| Field | Answer |
|---|---|
| Page type | fire and rescue guide |
| Primary use | Translate fire, rescue, and disaster-response sources into a practical public-access page. |
| Updated | 2026-05-09 |
| Core caveat | station POIs are not live readiness |
- 199
- fire stations
- rescue context
- station POIs are not live readiness
- wildfire is a separate agency layer
- DDPM disaster data catalog
- BMA fire station data
- GISTDA disaster fire
- DNP wildfire data
- NASA FIRMS
- NIEMS 1669 ITEMS
- OSM Thailand emergency POI
Why this page matters more now
Safety pages now sit inside the broader Thailand demand picture. Route confidence, border news, earthquake trust, and festival movement pressure all changed what travelers and residents needed from the public surface.
Canonical record checklist
Agency, office or station type, emergency phone, incident family, period, privacy level, source confidence, observed or publication time, location confidence, and whether the record is police access, road crash, disaster alert, ambulance system context, or external protest-risk signal.
Station
Alert
Risk