Trackside
MARC

MARC — September 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 440 — 2 days (Sep 4, Sep 16): was possibly cancelled (no train was ever tracked on it) — we found no MARC alert naming it on those days. Train 440 →
  • Train 438 (Sep 17): was possibly cancelled (no train was ever tracked on it) — we found no MARC alert naming this train. Train 438 →
  • Train 449 (Sep 17): was possibly cancelled (no train was ever tracked on it) — we found no MARC alert naming this train. Train 449 →
  • Train 451 (Sep 24): was possibly cancelled (no train was ever tracked on it) — MARC posted an alert naming this train, but not a cancellation. Train 451 →

Cancelled

  • Train 449 — 2 days (Sep 9, Sep 24): was cancelled — MARC posted an alert covering each of them. Train 449 →
  • Train 423 (Sep 28): was cancelled — MARC posted an alert covering it. Train 423 →
  • Train 438 (Sep 25): was cancelled — MARC posted an alert covering it. Train 438 →
  • Train 440 (Sep 1): was cancelled — MARC posted an alert covering it. Train 440 →
  • Train 446 (Sep 24): was cancelled — MARC posted an alert covering it. Train 446 →
  • Train 478 (Sep 20): was cancelled — MARC posted an alert covering it. Train 478 →
  • Train 485 (Sep 20): was cancelled — MARC posted an alert covering it. Train 485 →
  • Train 486 (Sep 20): was cancelled — MARC posted an alert covering it. Train 486 →
  • Train 544 (Sep 3): was cancelled — MARC posted an alert covering it. Train 544 →
  • Train 642 (Sep 25): was cancelled — MARC posted an alert covering it. Train 642 →
  • Train 849 (Sep 3): was cancelled — we found no MARC alert naming this train. Train 849 →
  • Train 858 (Sep 24): was cancelled — MARC posted an alert covering it. Train 858 →

Cut short before its last stop

  • Train 536 (Sep 24): was cut short before its last stop — MARC posted an alert covering it. Train 536 →
  • Train 634 (Sep 24): was cut short before its last stop — MARC posted an alert covering it. Train 634 →
  • Train 677 (Sep 20): was cut short before its last stop — MARC posted an alert covering it. Train 677 →
  • Train 874 (Sep 23): was cut short before its last stop — MARC posted an alert covering it. Train 874 →

Left the first station 20+ min late

  • Train 443 (Sep 24): left 20+ min late — MARC posted an alert covering it. Train 443 →
  • Train 454 (Sep 24): left 20+ min late — MARC posted an alert covering it. Train 454 →
  • Train 482 (Sep 20): left 20+ min late — MARC posted an alert covering it. Train 482 →
  • Train 544 (Sep 24): left 30+ min late — MARC posted an alert covering it. Train 544 →
  • Train 634 (Sep 11): left 20+ min late — MARC posted an alert covering it. Train 634 →
  • Train 642 (Sep 11): left 30+ min late — MARC posted an alert covering it. Train 642 →
  • Train 851 (Sep 16): left 20+ min late — MARC posted an alert covering it. Train 851 →
  • Train 856 (Sep 22): left 20+ min late — MARC posted an alert covering it. Train 856 →
  • Train 857 (Sep 30): left 30+ min late — MARC posted an alert covering it. Train 857 →
  • Train 858 (Sep 30): left 20+ min late — MARC posted an alert covering it. Train 858 →
  • Train 894 (Sep 24): left 30+ min late — MARC posted an alert covering it. Train 894 →

Tracking and data issues

Tracking stayed active after arrival

  • Train 880 — 2 days (Sep 3, Sep 11): tracking stayed active after the train arrived. Train 880 →
  • Train 511 (Sep 28): tracking stayed active for 63 min after it arrived at Union Station, the vehicle moved away while the trip was still active, and an arrival was published 67 min later than the train actually arrived. Train 511 →

Trip data ended before the final stop

  • Train 878 — 18 days (Sep 1–4, Sep 8–11, Sep 14–18, Sep 21–25): trip data never listed the final stop, although the train kept going. Train 878 →

Tracking ended before arrival

  • Train 851 — 9 days (Sep 1–2, Sep 11, Sep 16–17, Sep 22–23, Sep 28, Sep 30): the trip disappeared from tracking before the train reached its final stop. Train 851 →
  • Train 685 — 4 days (Sep 5, Sep 12, Sep 19, Sep 26): the trip disappeared from tracking before the train reached its final stop. Train 685 →
  • Train 698 — 4 days (Sep 5, Sep 12, Sep 19, Sep 26): the trip disappeared from tracking before the train reached its final stop. Train 698 →
  • Train 415 — 3 days (Sep 2, Sep 9–10): the trip disappeared from tracking before the train reached its final stop. Train 415 →
  • Train 423 — 3 days (Sep 2, Sep 10, Sep 16): the trip disappeared from tracking before the train reached its final stop. Train 423 →
  • Train 511 — 3 days (Sep 17, Sep 24, Sep 30): the trip disappeared from tracking before the train reached its final stop. Train 511 →
  • Train 845 — 3 days (Sep 1, Sep 3, Sep 30): the trip disappeared from tracking before the train reached its final stop. Train 845 →
  • Train 849 — 3 days (Sep 16, Sep 23, Sep 30): the trip disappeared from tracking before the train reached its final stop. Train 849 →
  • Train 894 — 3 days (Sep 4, Sep 16, Sep 22): the trip disappeared from tracking before the train reached its final stop. Train 894 →
  • Train 403 — 2 days (Sep 2, Sep 24): the trip disappeared from tracking before the train reached its final stop. Train 403 →
  • Train 409 — 2 days (Sep 4, Sep 18): the trip disappeared from tracking before the train reached its final stop. Train 409 →
  • Train 505 — 2 days (Sep 2, Sep 25): the trip disappeared from tracking before the train reached its final stop. Train 505 →
  • Train 579 — 2 days (Sep 2, Sep 9): the trip disappeared from tracking before the train reached its final stop. Train 579 →
  • Train 878 — 2 days (Sep 28, Sep 30): the trip disappeared from tracking before the train reached its final stop. Train 878 →
  • Train 413 (Sep 16): the trip disappeared from tracking about 0.8 mi short of Union Station, with its arrival still shown 6 min away. Train 413 →
  • Train 419 (Sep 4): the trip disappeared from tracking about 1.3 mi short of Union Station, with its arrival still shown 8 min away. Train 419 →
  • Train 431 (Sep 22): the trip disappeared from tracking about 1.7 mi short of Union Station, with its arrival still shown 12 min away. Train 431 →
  • Train 433 (Sep 25): the trip disappeared from tracking about 1.6 mi short of Union Station, with its arrival still shown 9 min away. Train 433 →
  • Train 439 (Sep 29): the trip disappeared from tracking about 0.7 mi short of Union Station, with its arrival still shown 8 min away. Train 439 →
  • Train 452 (Sep 25): the trip disappeared from tracking about 1.3 mi short of Baltimore Penn Station, with its arrival still shown 5 min away. Train 452 →
  • Train 525 (Sep 11): the trip disappeared from tracking about 0.8 mi short of Union Station, with its arrival still shown 5 min away. Train 525 →
  • Train 681 (Sep 13): the trip disappeared from tracking about 16.3 mi short of Union Station, with its arrival still shown 30 min away. Train 681 →
  • Train 831 (Sep 30): the trip disappeared from tracking about 33 mi short of Brunswick, with its arrival still shown 57 min away. Train 831 →
  • Train 841 (Sep 1): the trip disappeared from tracking about 1.7 mi short of Union Station, with its arrival still shown 7 min away. Train 841 →
  • Train 874 (Sep 16): the trip disappeared from tracking about 1.1 mi short of Union Station, with its arrival still shown 16 min away. Train 874 →
  • Train 880 (Sep 8): the trip disappeared from tracking about 1.1 mi short of Union Station, with its arrival still shown 22 min away. Train 880 →
  • Train 892 (Sep 28): the trip disappeared from tracking about 1.2 mi short of Union Station, with its arrival still shown 21 min away. Train 892 →

No position published

  • Train 448 (Sep 17): no position was published for 26 min while the train covered about 16.3 mi. Train 448 →
  • Train 642 (Sep 28): no position was published for 61 min while the train covered about 40 mi. Train 642 →
  • Train 831 (Sep 30): no position was published for 16 min while the train covered about 20.1 mi. Train 831 →

Positions in two places at once

  • Train 412 (Sep 2): the trip showed positions in two places at once, about 9.4 mi apart. Train 412 →
  • Train 418 (Sep 1): the trip showed positions in two places at once, about 23.9 mi apart. Train 418 →
  • Train 424 (Sep 3): the trip showed positions in two places at once, about 14.5 mi apart. Train 424 →
  • Train 433 (Sep 1): the trip showed positions in two places at once, about 5 mi apart. Train 433 →
  • Train 454 (Sep 28): the trip showed positions in two places at once, about 34.5 mi apart. Train 454 →
  • Train 455 (Sep 28): the trip showed positions in two places at once, about 4.8 mi apart. Train 455 →
  • Train 482 (Sep 20): the trip showed positions in two places at once, about 28.8 mi apart. Train 482 →
  • Train 520 (Sep 23): the trip showed positions in two places at once, about 9 mi apart. Train 520 →
  • Train 634 (Sep 11): the trip showed positions in two places at once, about 12.4 mi apart. Train 634 →
  • Train 681 (Sep 20): the trip showed positions in two places at once, about 9.9 mi apart. Train 681 →

Predicted times stopped updating

  • Train 424 (Sep 30): predicted times stopped updating for 17 min while the train moved about 0.1 mi, and the time shown for Seabrook passed before the train got there. Train 424 →
  • Train 579 (Sep 17): predicted times stopped updating for 21 min, and the time shown for Edgewood passed before the train got there. Train 579 →
  • Train 831 (Sep 30): predicted times stopped updating for 20 min, and the time shown for Laurel passed before the train got there. Train 831 →
  • Train 878 (Sep 4): predicted times stopped updating for 15 min while the train moved about 0.1 mi, and the time shown for Point of Rocks passed before the train got there. Train 878 →
  • Train 890 (Sep 16): predicted times stopped updating for 51 min, and the time shown for Dickerson passed before the train got there. Train 890 →

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

← All months · MARC