MARC — November 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 495 (Nov 1): was possibly cancelled (no train was ever tracked on it) — we found no MARC alert naming this train. Train 495 →
Left the first station 20+ min late
- Train 449 (Nov 4): left 30+ min late — MARC posted an alert covering it. Train 449 →
- Train 490 (Nov 7): left 30+ min late — MARC posted an alert covering it. Train 490 →
- Train 520 (Nov 3): left 30+ min late — MARC posted an alert covering it. Train 520 →
- Train 537 (Nov 6): left 30+ min late — MARC posted an alert covering it. Train 537 →
- Train 579 (Nov 4): left 20+ min late — MARC posted an alert covering it. Train 579 →
- Train 612 (Nov 6): left 30+ min late — MARC posted an alert covering it. Train 612 →
- Train 613 (Nov 6): left 30+ min late — we found no MARC alert naming this train. Train 613 →
- Train 642 (Nov 4): left 20+ min late — we found no MARC alert naming this train. Train 642 →
- Train 853 (Nov 5): left 20+ min late — MARC posted an alert covering it. Train 853 →
- Train 859 (Nov 2): left 20+ min late — MARC posted an alert covering it. Train 859 →
- Train 860 (Nov 6): left 20+ min late — MARC posted an alert covering it. Train 860 →
Tracking and data issues
Tracking stayed active after arrival
- Train 892 — 2 days (Nov 4–5): tracking stayed active after the train arrived. Train 892 →
- Train 413 (Nov 9): tracking stayed active for 26 min after it arrived at Union Station, the vehicle moved away while the trip was still active, and an arrival was published 30 min later than the train actually arrived. Train 413 →
- Train 841 (Nov 10): tracking stayed active for 25 min after it arrived at Union Station, the vehicle moved away while the trip was still active, and an arrival was published 26 min later than the train actually arrived. Train 841 →
- Train 880 (Nov 2): tracking stayed active for 12 min after it arrived at Union Station, the vehicle moved away while the trip was still active, and an arrival was published 33 min later than the train actually arrived. Train 880 →
Tracking ended before arrival
- Train 849 — 4 days (Nov 3–5, Nov 10): the trip disappeared from tracking before the train reached its final stop. Train 849 →
- Train 851 — 4 days (Nov 4, Nov 9–11): the trip disappeared from tracking before the train reached its final stop. Train 851 →
- Train 845 — 2 days (Nov 3, Nov 9): the trip disappeared from tracking before the train reached its final stop. Train 845 →
- Train 890 — 2 days (Nov 4, Nov 11): the trip disappeared from tracking before the train reached its final stop. Train 890 →
- Train 415 (Nov 6): the trip disappeared from tracking about 1.1 mi short of Union Station, with its arrival still shown 6 min away. Train 415 →
- Train 421 (Nov 5): the trip disappeared from tracking about 1.1 mi short of Union Station, with its arrival still shown 7 min away. Train 421 →
- Train 427 (Nov 9): the trip disappeared from tracking about 0.9 mi short of Union Station, with its arrival still shown 8 min away. Train 427 →
- Train 497 (Nov 7): the trip disappeared from tracking about 0.9 mi short of Union Station, with its arrival still shown 10 min away. Train 497 →
- Train 505 (Nov 6): the trip disappeared from tracking about 1.1 mi short of Union Station, with its arrival still shown 5 min away. Train 505 →
- Train 511 (Nov 6): the trip disappeared from tracking about 0.6 mi short of Union Station, with its arrival still shown 7 min away. Train 511 →
- Train 520 (Nov 6): the trip disappeared from tracking about 36.1 mi short of Perryville, with its arrival still shown 44 min away. Train 520 →
- Train 698 (Nov 7): the trip disappeared from tracking about 7.2 mi short of Martin State Airport, with its arrival still shown 20 min away. Train 698 →
- Train 841 (Nov 3): the trip disappeared from tracking about 2.1 mi short of Union Station, with its arrival still shown 9 min away. Train 841 →
- Train 843 (Nov 3): the trip disappeared from tracking about 1.6 mi short of Union Station, with its arrival still shown 7 min away. Train 843 →
- Train 870 (Nov 4): the trip disappeared from tracking about 1.1 mi short of Union Station, with its arrival still shown 11 min away. Train 870 →
- Train 872 (Nov 4): the trip disappeared from tracking about 2 mi short of Union Station, with its arrival still shown 16 min away. Train 872 →
- Train 878 (Nov 3): the trip disappeared from tracking about 1.6 mi short of Union Station, with its arrival still shown 5 min away. Train 878 →
- Train 880 (Nov 3): the trip disappeared from tracking about 1.2 mi short of Union Station, with its arrival still shown 22 min away. Train 880 →
No position published
- Train 490 (Nov 1): no position was published for 23 min while the train covered about 15.2 mi. Train 490 →
- Train 537 (Nov 6): no position was published for 20 min while the train covered about 10.3 mi. Train 537 →
- Train 830 (Nov 6): no position was published for 39 min while the train covered about 28.6 mi. Train 830 →
- Train 881 (Nov 6): no position was published for 15 min while the train covered about 8.2 mi. Train 881 →
Predicted times stopped updating
- Train 438 (Nov 4): predicted times stopped updating for 16 min, and the time shown for Odenton passed before the train got there. Train 438 →
- Train 537 (Nov 6): predicted times stopped updating for 38 min while the train moved about 14.3 mi, and the time shown for Edgewood passed before the train got there. Train 537 →
- Train 843 (Nov 3): predicted times stopped updating for 24 min, and the time shown for Dorsey passed before the train got there. Train 843 →
- Train 852 (Nov 2): predicted times stopped updating for 15 min, and the time shown for Muirkirk passed before the train got there. Train 852 →
- Train 853 (Nov 5): predicted times stopped updating for 19 min while the train moved about 11.1 mi, and the time shown for Dorsey passed before the train got there. Train 853 →
Tracking and data issues describe what the feed showed, not who caused it. See About for methodology.