A weekly view of rail service.

Follow a railroad’s train speed, terminal dwell and operating activity over time, using its reports to the Surface Transportation Board.

CSX Transportation495 weekly reporting slotsMarch 24, 2017–September 11, 2026
CSX logo
REPORTING RAILROADCSX TransportationOne railroad at a time
REPORTING PERIOD
Read this as a CSX trend. Railroads may measure service differently. This page does not rank railroads or establish that their measures are directly comparable.

Loading weekly service data…

Weekly snapshot

Values reported by CSX to STB · Changes calculated by RailStats.org

Select one to four cards to compare measures. One measure shows original units; two or more show relative change.

WITHIN-RAILROAD TREND

Coverage: weeks ending March 24, 2017–September 11, 2026. Starts with the report dated March 29, 2017. Flagged values appear as gaps, never zero.

Swipe horizontally to see the full chart.

Trains held: reported causesCrew, locomotive power and other

Average trains holding per day

Reported values · Weekly average

How to read this

Why a decimal?
CSX counts trains holding at approximately 3:30 a.m. each day, then averages the daily counts across the week.
What does “Crew” mean here?
It is the railroad’s reported cause category. This report does not provide the specific circumstances behind each hold.
What does the number leave out?
It does not measure hours of delay or count all unique trains delayed during the week.

Reported causes over time

Swipe horizontally to see all reporting weeks.

Weekly values by reported cause
Average trains holding per day · Two decimal places
Week endingCrewLocomotive powerOtherTotalOfficial source
Selected-week details by train type
Train typeCrewLocomotive powerOtherReported totalRailroad note
Reporting details and limitations

CSX reports weekly averages from daily snapshots. The same train may appear in more than one day’s snapshot. The three reported cause categories are crew, locomotive power and other; “Other” combines causes outside the first two categories.

CSX’s methodology says a train-type category is reported only when at least four trains of that type operated during the week. Railroad collection methods and reporting populations can differ.

Open selected official workbook ↗

CSX reporting methodology ↗

Exact reported values and calculated changes
Source review notes

Charts use the individual CSX workbooks. Material numerical disagreements with STB’s consolidated file, unreconciled totals and questionable reporting periods are withheld pending review. Rounding-compatible differences retain the individual workbook’s precision. No corrections are invented.

STB consolidated reference ↗

A CLOSER LOOK

Terminal dwell, by location

Average hours at the ten terminals listed in the selected CSX report. The terminal list can change over time. Cars on run-through trains are excluded. Locations stay in source order; this is not a terminal ranking.

The system average is reported separately. It is not calculated here by averaging these ten locations.

SOURCES AND MEANING

Know what each number measures.

This page uses 494 available CSX weekly workbooks and STB’s consolidated reference, retrieved September 19, 2026. One linked weekly workbook was unavailable. Some historical values are withheld pending source review. The file date and the reporting week are shown separately.

Open selected official workbook ↗STB Rail Service Data page ↗
Reported values and calculated changes

The four measures come from the “Rail Service (Item Nos. 1–6)” worksheet: system train speed (B13), system terminal dwell (B27), total cars online (B38), and total trains holding (E59).

Weekly change = selected week − preceding week. Percent change = weekly change ÷ preceding week × 100. A zero or unavailable prior value leaves the percentage unavailable. Displayed values are rounded; calculations use source precision.

When two or more measures are selected, index = reported value ÷ value in the first displayed week × 100. The baseline is the same reporting week for every selected measure and resets when the displayed starting week changes. A zero or missing starting value leaves that measure’s index unavailable. Original units remain in the cards and table. An increase is not automatically an improvement, and shared movement does not establish cause.

What these measures do—and do not—tell you

Train speed is an operating measure, not an end-to-end delivery promise. Terminal dwell describes time at terminals and is separate from train speed. Cars online is a weekly average, not carloads originated or delivered. Trains held is an average number per day, not a weekly total.

More or less activity is not automatically better or worse service. No composite score or national average is calculated.

Coverage and source limitations

This release covers CSX only. Twenty weekly slots have one or more values withheld, including one unavailable workbook. Conflicting figures remain visible in source review notes but are excluded from charts and calculated changes.

Reporting populations and terminal lists can change. The source material does not establish unchanged collection methods throughout the entire history. These are descriptive within-CSX trends, not rankings or adjusted comparisons with other railroads.

CSX methodology and validation review · Download data and source records (JSON) · Download reconciliation notes (JSON)