Trackside
MARC

MARC — July 2026

Every service problem and tracking or data issue Trackside counted this month. Repeats on the same train are grouped, with the affected dates.

Service problems

Possibly cancelled (no train was ever tracked on it)

  • Train 641 (Jul 31): was possibly cancelled (no train was ever tracked on it) — we found no MARC alert naming this train. Train 641 →
  • Train 642 (Jul 31): was possibly cancelled (no train was ever tracked on it) — we found no MARC alert naming this train. Train 642 →
  • Train 855 (Jul 17): was possibly cancelled (no train was ever tracked on it) — we found no MARC alert naming this train. Train 855 →
  • Train 856 (Jul 17): was possibly cancelled (no train was ever tracked on it) — we found no MARC alert naming this train. Train 856 →

Cancelled

  • Train 427 (Jul 23): was cancelled — we found no MARC alert naming this train. Train 427 →
  • Train 438 (Jul 31): was cancelled — we found no MARC alert naming this train. Train 438 →
  • Train 439 (Jul 23): was cancelled — we found no MARC alert naming this train. Train 439 →
  • Train 449 (Jul 31): was cancelled — we found no MARC alert naming this train. Train 449 →
  • Train 517 (Jul 31): was cancelled — we found no MARC alert naming this train. Train 517 →
  • Train 612 (Jul 17): was cancelled — we found no MARC alert naming this train. Train 612 →
  • Train 642 (Jul 16): was cancelled — we found no MARC alert naming this train. Train 642 →
  • Train 844 (Jul 17): was cancelled — we found no MARC alert naming this train. Train 844 →
  • Train 846 (Jul 29): was cancelled — we found no MARC alert naming this train. Train 846 →
  • Train 879 (Jul 17): was cancelled — we found no MARC alert naming this train. Train 879 →

Left the first station 20+ min late

  • Train 407 (Jul 20): left 30+ min late — we found no MARC alert naming this train. Train 407 →
  • Train 410 (Jul 20): left 20+ min late — we found no MARC alert naming this train. Train 410 →
  • Train 424 (Jul 23): left 20+ min late — we found no MARC alert naming this train. Train 424 →
  • Train 454 (Jul 21): left 30+ min late — we found no MARC alert naming this train. Train 454 →
  • Train 492 (Jul 18): left 30+ min late — we found no MARC alert naming this train. Train 492 →
  • Train 536 (Jul 31): left 30+ min late — we found no MARC alert naming this train. Train 536 →
  • Train 613 (Jul 17): left 20+ min late — we found no MARC alert naming this train. Train 613 →
  • Train 634 (Jul 31): left 20+ min late — we found no MARC alert naming this train. Train 634 →
  • Train 844 (Jul 29): left 30+ min late — we found no MARC alert naming this train. Train 844 →
  • Train 854 (Jul 17): left 20+ min late — we found no MARC alert naming this train. Train 854 →
  • Train 859 (Jul 17): left 20+ min late — we found no MARC alert naming this train. Train 859 →
  • Train 860 (Jul 28): left 30+ min late — we found no MARC alert naming this train. Train 860 →
  • Train 877 (Jul 17): left 20+ min late — we found no MARC alert naming this train. Train 877 →
  • Train 891 (Jul 17): left 30+ min late — we found no MARC alert naming this train. Train 891 →

Tracking and data issues

Tracking stayed active after arrival

  • Train 537 — 2 days (Jul 24, Jul 27): tracking stayed active after the train arrived. Train 537 →
  • Train 419 (Jul 30): tracking stayed active for 97 min after it arrived at Union Station, the vehicle moved away while the trip was still active, and an arrival was published 100 min later than the train actually arrived. Train 419 →
  • Train 511 (Jul 31): tracking stayed active for 20 min after it arrived at Union Station, the vehicle moved away while the trip was still active, and an arrival was published 3 min later than the train actually arrived. Train 511 →
  • Train 880 (Jul 22): tracking stayed active for 13 min after it arrived at Union Station, the vehicle moved away while the trip was still active, and an arrival was published 34 min later than the train actually arrived. Train 880 →

Trip data ended before the final stop

  • Train 878 — 11 days (Jul 17, Jul 20–24, Jul 27–31): trip data never listed the final stop, although the train kept going. Train 878 →

No position published

  • Train 871 — 2 days (Jul 17, Jul 24): no position was published for part of the trip. Train 871 →
  • Train 440 (Jul 16): no position was published for 16 min while the train covered about 10.3 mi. Train 440 →
  • Train 858 (Jul 28): no position was published for 94 min while the train covered about 4 mi. Train 858 →
  • Train 879 (Jul 24): no position was published for 19 min while the train covered about 7.4 mi. Train 879 →
  • Train 883 (Jul 21): no position was published for 17 min while the train covered about 7.3 mi. Train 883 →

Position published, no trip data

  • Train 511 (Jul 17): no trip data was published for the train, although its position showed it running about 12.4 mi along its route. Train 511 →

Positions in two places at once

  • Train 424 (Jul 23): the trip showed positions in two places at once, about 13.9 mi apart. Train 424 →
  • Train 494 (Jul 18): the trip showed positions in two places at once, about 35 mi apart. Train 494 →
  • Train 511 (Jul 17): the trip showed positions in two places at once, about 7.3 mi apart. Train 511 →
  • Train 877 (Jul 31): the trip showed positions in two places at once, about 7.3 mi apart. Train 877 →

Tracking and data issues describe what the feed showed, not who caused it. See About for methodology.

← All months · MARC