Class I rail performance, every week.
Surface Transportation Board weekly service metrics are period-labeled and parser/backlog guarded; freight-flow priors stay planned context. Train speed, terminal dwell, carloads by commodity, and intermodal performance.
Before broad source-level claims, users should check /v1/sources sourceClaimAudit plus claimBearing and sourceFactHealth. Raw-current, non-live, stale, no-row, planned, future, missing-parser-policy, and embedding-backlog rows stay context-only unless packet evidence proves exact claim use. Free no-key access covers reports, feeds, manifests, discovery pages, and current public crossing pages; raw rows, historical exports, and feature windows require scoped server-side access.
Rail monitoring layer
Corridor observations and source status are kept separate from claim-bearing evidence.
Cross-Border Trade Sector Report - May 5, 2026
**Dunvale Intelligence: Weekly Cross-Border Trade Sector Report** **Date:** May 5, 2026
Cross-Border Trade Sector Report - April 28, 2026
**Dunvale Intelligence: Weekly Cross-Border Trade Sector Report** **Date:** April 28, 2026
Cross-Border Trade Sector Report - April 21, 2026
**DUNVALE INTELLIGENCE: WEEKLY CROSS-BORDER TRADE SECTOR REPORT** **Date:** Tuesday, April 21, 2026
Cross-Border Trade Sector Report - April 14, 2026
**DUNVALE INTELLIGENCE: WEEKLY CROSS-BORDER TRADE SECTOR REPORT** **Date:** Tuesday, April 14, 2026
STB Class I Service Metrics
WeeklySurface Transportation Board
Train speed, terminal dwell, carloads by commodity, intermodal volumes for the seven Class I railroads.
Evidence use: Weekly rail facts need report-period labels, parser-lag-free sourceFactHealth, hash-current or deterministic evidence, and packet/report citations.
FAF / TransBorder rail context
ScheduledFHWA / BTS
Historical commodity-flow context for rail and intermodal pressure near border corridors.
Evidence use: Scheduled rail context only until source rows, source health, and citations exist.
STB service metrics are pulled weekly from agency filings. Time series are stored at the railroad x measure x week granularity, with metadata identifying each commodity, terminal, or operational dimension. Claim use requires report-period labels, parser-lag-free sourceFactHealth, hash-current or deterministic evidence, and packet/report citations. Anomaly detection flags deviations beyond historical norms.
“How is BNSF terminal dwell trending vs UP?”
Returns side-by-side weekly dwell metrics for both carriers.
“Are intermodal carloads recovering?”
Surfaces intermodal carload volumes against four-week and year-ago baselines.
Build with the rail domain.
Email reports, scoped REST API, feeds, and webhooks — choose the integration that fits how your team or system works.