livetra.app valid

LiveTRA

為通勤族設計的台灣鐵路（台鐵）即時時刻表與誤點查詢服務。提供車站時刻表、單車次完整停靠站、誤點即時動態與最長 90 日的歷史誤點統計，並整合台北捷運即時到站與中央氣象署天氣資訊。支援 8 種語言。

For agents: Taiwan Railway (TRA) real-time timetables, live delay lists, 90-day delay history, and Taipei Metro arrivals for commuters. Supports 8 languages.

taiwan railwaytra timetabletrain delaystaipei metrodelay compensation

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-23T12:16:16.990Z. Cached copy · Source on livetra.app

# LiveTRA

> 為通勤族設計的台灣鐵路（台鐵）即時時刻表與誤點查詢服務。提供車站時刻表、單車次完整停靠站、誤點即時動態與最長 90 日的歷史誤點統計，並整合台北捷運即時到站與中央氣象署天氣資訊。支援 8 種語言。

LiveTRA is a real-time Taiwan Railway (TRA) timetable and delay tracking service designed for commuters. It provides station timetables, full stop-by-stop train details, live delay information, and historical delay statistics going back up to 90 days, and integrates Taipei Metro arrivals and Central Weather Administration weather data. Available in 8 languages.

## Unique Data

LiveTRA is not just a live lookup tool — it continuously collects TRA real-time operation data (liveboard polled every 2 minutes, snapshotted to database every 30 minutes) to build a historical delay record per train.

- Per-train historical delay statistics: 7-day daily breakdown, or 30/90-day average trend
- Multi-train delay comparison: overlay delay curves for up to 3 trains on the same date (`/delay-compare`)
- Delay data goes back up to 90 days per train

## Core Pages

- [Home / 首頁](https://livetra.app/): Site introduction, station search, recent and favorite stations
- [Liveboard / 誤點列表](https://livetra.app/liveboard): All currently delayed TRA trains, color-coded by delay
- [Delay Compare / 誤點比較](https://livetra.app/delay-compare): Compare delay trends across multiple trains
- [National Railway Museum / 國家鐵道博物館](https://livetra.app/nrm): Museum train timetable
- [Compensation Rules / 誤點補償](https://livetra.app/compensation): TRA delay compensation policy
- [Emergency Guidelines / 緊急應變](https://livetra.app/emergency): What to do in train emergencies

## URL Patterns

- `/{stationId}-{stationName}` — Station timetable. Example: `/1001-基隆`, `/1080-板橋`. Routing only validates `stationId` (the dash-prefixed name is decorative)
- `/train/{trainNo}` — Single train detail with all stops. Example: `/train/123`
- `/{lang}/...` — Localized variant. Locale prefixes: `jp` (日本語), `ko` (한국어), `en` (English), `th` (ไทย), `vi` (Tiếng Việt), `in` (Bahasa Indonesia), `id` (हिन्दी). Default 正體中文 has no prefix.

## Data Sources

- TDX (Ministry of Transportation, Taiwan) — TRA timetable, real-time delays, alerts, suspensions
- TRTC (Taipei Rapid Transit Corporation) — Taipei Metro real-time arrivals
- CWA (Central Weather Administration) — Per-station weather forecasts

## Update Frequencies

- TRA delay liveboard: every 2 minutes (cron) → 20s client polling
- TRA alerts and suspensions: every 5–10 minutes
- Taipei Metro arrivals: every 10 seconds
- TRA timetable: rebuilt nightly for the next 7 days

## Common Questions

Q: Which trains are currently delayed?
A: `/liveboard` — all currently delayed TRA trains, color-coded by delay severity.

Q: How delayed is a specific train, and what are all its stops?
A: `/train/{trainNo}` — full stop-by-stop detail with live delay for one train.

Q: How does a train's delay compare across dates, or against other trains?
A: `/delay-compare` — pick up to 3 train numbers and a date to overlay their delay curves; supports 7/30/90-day histori
…

Related sites

Find similar publishers by meaning →

Other listed sites in Travel. See the whole category →

Machine-readable: GET /v1/resolve?q=livetra.app · GET /v1/domain/livetra.app · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for livetra.app:
1. POST https://agentwebmap.com/v1/sites/livetra.app/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://livetra.app/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/livetra.app/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/livetra.app).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.