Trackside
MARC

MARC — August 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 413 (Aug 12): was possibly cancelled (no train was ever tracked on it) — MARC posted an alert covering it. Train 413 →
  • Train 445 (Aug 19): was possibly cancelled (no train was ever tracked on it) — MARC posted an alert covering it. Train 445 →
  • Train 841 (Aug 17): was possibly cancelled (no train was ever tracked on it) — MARC posted an alert naming this train, but not a cancellation. Train 841 →
  • Train 873 (Aug 24): was possibly cancelled (no train was ever tracked on it) — we found no MARC alert naming this train. Train 873 →

Cancelled

  • Train 852 — 2 days (Aug 19, Aug 26): was cancelled — MARC posted an alert covering each of them. Train 852 →
  • Train 413 (Aug 31): was cancelled — MARC posted an alert covering it. Train 413 →
  • Train 423 (Aug 24): was cancelled — MARC posted an alert covering it. Train 423 →
  • Train 428 (Aug 19): was cancelled — MARC posted an alert covering it. Train 428 →
  • Train 439 (Aug 19): was cancelled — MARC posted an alert covering it. Train 439 →
  • Train 440 (Aug 10): was cancelled — MARC posted an alert covering it. Train 440 →
  • Train 446 (Aug 17): was cancelled — MARC posted an alert covering it. Train 446 →
  • Train 495 (Aug 30): was cancelled — we found no MARC alert naming this train. Train 495 →
  • Train 548 (Aug 19): was cancelled — MARC posted an alert covering it. Train 548 →
  • Train 610 (Aug 31): was cancelled — MARC posted an alert covering it. Train 610 →
  • Train 613 (Aug 12): was cancelled — MARC posted an alert covering it. Train 613 →
  • Train 688 (Aug 29): was cancelled — MARC posted an alert covering it. Train 688 →
  • Train 842 (Aug 3): was cancelled — we found no MARC alert naming this train. Train 842 →
  • Train 848 (Aug 12): was cancelled — MARC posted an alert covering it. Train 848 →
  • Train 855 (Aug 12): was cancelled — MARC posted an alert covering it. Train 855 →

Cut short before its last stop

  • Train 517 (Aug 27): was cut short before its last stop — MARC posted an alert covering it. Train 517 →
  • Train 613 (Aug 31): was cut short before its last stop — MARC posted an alert covering it. Train 613 →

Left the first station 20+ min late

  • Train 439 — 2 days (Aug 5–6): left 20+ min late — we found no MARC alert naming it on those days. Train 439 →
  • Train 848 — 2 days (Aug 19, Aug 26): left 20+ min late — MARC posted an alert covering each of them. Train 848 →
  • Train 854 — 2 days (Aug 10, Aug 19): left 20+ min late — MARC posted an alert covering each of them. Train 854 →
  • Train 859 — 2 days (Aug 7, Aug 10): left 20+ min late — MARC posted an alert covering each of them. Train 859 →
  • Train 407 (Aug 14): left 20+ min late — we found no MARC alert naming this train. Train 407 →
  • Train 412 (Aug 12): left 20+ min late — MARC posted an alert covering it. Train 412 →
  • Train 414 (Aug 19): left 20+ min late — MARC posted an alert covering it. Train 414 →
  • Train 415 (Aug 12): left 30+ min late — MARC posted an alert covering it. Train 415 →
  • Train 418 (Aug 10): left 20+ min late — MARC posted an alert covering it. Train 418 →
  • Train 445 (Aug 17): left 20+ min late — MARC posted an alert covering it. Train 445 →
  • Train 448 (Aug 6): left 30+ min late — MARC posted an alert covering it. Train 448 →
  • Train 449 (Aug 6): left 30+ min late — MARC posted an alert covering it. Train 449 →
  • Train 451 (Aug 14): left 20+ min late — MARC posted an alert covering it. Train 451 →
  • Train 454 (Aug 11): left 20+ min late — MARC posted an alert covering it. Train 454 →
  • Train 455 (Aug 19): left 30+ min late — MARC posted an alert covering it. Train 455 →
  • Train 486 (Aug 23): left 20+ min late — MARC posted an alert covering it. Train 486 →
  • Train 491 (Aug 29): left 30+ min late — MARC posted an alert covering it. Train 491 →
  • Train 492 (Aug 29): left 30+ min late — MARC posted an alert covering it. Train 492 →
  • Train 494 (Aug 22): left 20+ min late — MARC posted an alert covering it. Train 494 →
  • Train 511 (Aug 13): left 20+ min late — MARC posted an alert covering it. Train 511 →
  • Train 537 (Aug 12): left 30+ min late — MARC posted an alert covering it. Train 537 →
  • Train 554 (Aug 28): left 30+ min late — MARC posted an alert covering it. Train 554 →
  • Train 641 (Aug 19): left 30+ min late — MARC posted an alert covering it. Train 641 →
  • Train 675 (Aug 1): left 20+ min late — we found no MARC alert naming this train. Train 675 →
  • Train 842 (Aug 21): left 20+ min late — MARC posted an alert covering it. Train 842 →
  • Train 853 (Aug 19): left 30+ min late — MARC posted an alert covering it. Train 853 →
  • Train 875 (Aug 10): left 20+ min late — MARC posted an alert covering it. Train 875 →
  • Train 894 (Aug 24): left 20+ min late — MARC posted an alert covering it. Train 894 →

Tracking and data issues

Tracking stayed active after arrival

  • Train 517 (Aug 3): tracking stayed active for 95 min after it arrived at Union Station, the vehicle moved away while the trip was still active, and an arrival was published 6 min later than the train actually arrived. Train 517 →
  • Train 525 (Aug 18): tracking stayed active for 40 min after it arrived at Union Station, the vehicle moved away while the trip was still active, and an arrival was published 42 min later than the train actually arrived. Train 525 →
  • Train 641 (Aug 27): tracking stayed active for 75 min after it arrived at Union Station, the vehicle moved away while the trip was still active, and an arrival was published 76 min later than the train actually arrived. Train 641 →
  • Train 874 (Aug 25): tracking stayed active for 103 min after it arrived at Union Station, the vehicle moved away while the trip was still active, and an arrival was published 120 min later than the train actually arrived. Train 874 →
  • Train 890 (Aug 28): tracking stayed active for 37 min after it arrived at Union Station, the vehicle moved away while the trip was still active, and an arrival was published 41 min later than the train actually arrived. Train 890 →
  • Train 892 (Aug 19): tracking stayed active for 10 min after it arrived at Union Station, and published an arrival 21 min later than the train actually arrived. Train 892 →

Trip data ended before the final stop

  • Train 878 — 21 days (Aug 3–7, Aug 10–14, Aug 17–21, Aug 24–28, Aug 31): trip data never listed the final stop, although the train kept going. Train 878 →

Tracking ended before arrival

  • Train 851 — 6 days (Aug 13–14, Aug 17–18, Aug 26–27): the trip disappeared from tracking before the train reached its final stop. Train 851 →
  • Train 880 — 5 days (Aug 11, Aug 18, Aug 20, Aug 24, Aug 31): the trip disappeared from tracking before the train reached its final stop. Train 880 →
  • Train 685 — 4 days (Aug 8, Aug 15, Aug 22, Aug 29): the trip disappeared from tracking before the train reached its final stop. Train 685 →
  • Train 698 — 4 days (Aug 8, Aug 15, Aug 22, Aug 29): the trip disappeared from tracking before the train reached its final stop. Train 698 →
  • Train 845 — 4 days (Aug 10–11, Aug 13, Aug 21): the trip disappeared from tracking before the train reached its final stop. Train 845 →
  • Train 894 — 4 days (Aug 7, Aug 11, Aug 24–25): the trip disappeared from tracking before the train reached its final stop. Train 894 →
  • Train 857 — 3 days (Aug 25–26, Aug 28): the trip disappeared from tracking before the train reached its final stop. Train 857 →
  • Train 419 — 2 days (Aug 7, Aug 26): the trip disappeared from tracking before the train reached its final stop. Train 419 →
  • Train 423 — 2 days (Aug 20–21): the trip disappeared from tracking before the train reached its final stop. Train 423 →
  • Train 429 — 2 days (Aug 7, Aug 10): the trip disappeared from tracking before the train reached its final stop. Train 429 →
  • Train 431 — 2 days (Aug 10, Aug 12): the trip disappeared from tracking before the train reached its final stop. Train 431 →
  • Train 843 — 2 days (Aug 17, Aug 21): the trip disappeared from tracking before the train reached its final stop. Train 843 →
  • Train 849 — 2 days (Aug 12, Aug 14): the trip disappeared from tracking before the train reached its final stop. Train 849 →
  • Train 892 — 2 days (Aug 12, Aug 20): the trip disappeared from tracking before the train reached its final stop. Train 892 →
  • Train 403 (Aug 28): the trip disappeared from tracking about 1.1 mi short of Union Station, with its arrival still shown 7 min away. Train 403 →
  • Train 409 (Aug 20): the trip disappeared from tracking about 1.5 mi short of Union Station, with its arrival still shown 17 min away. Train 409 →
  • Train 421 (Aug 7): the trip disappeared from tracking about 0.7 mi short of Union Station, with its arrival still shown 5 min away. Train 421 →
  • Train 427 (Aug 7): the trip disappeared from tracking about 2.5 mi short of Union Station, with its arrival still shown 12 min away. Train 427 →
  • Train 511 (Aug 7): the trip disappeared from tracking about 1.2 mi short of Union Station, with its arrival still shown 8 min away. Train 511 →
  • Train 517 (Aug 28): the trip disappeared from tracking about 1.2 mi short of Union Station, with its arrival still shown 11 min away. Train 517 →
  • Train 681 (Aug 23): the trip disappeared from tracking about 1.3 mi short of Union Station, with its arrival still shown 4 min away. Train 681 →
  • Train 853 (Aug 25): the trip disappeared from tracking about 1.2 mi short of Union Station, with its arrival still shown 3 min away. Train 853 →
  • Train 855 (Aug 26): the trip disappeared from tracking about 2.5 mi short of Union Station, with its arrival still shown 10 min away. Train 855 →
  • Train 859 (Aug 28): the trip disappeared from tracking about 0.9 mi short of Union Station, with its arrival still shown 4 min away. Train 859 →
  • Train 874 (Aug 24): the trip disappeared from tracking about 1 mi short of Union Station, with its arrival still shown 15 min away. Train 874 →
  • Train 875 (Aug 10): the trip disappeared from tracking about 3.7 mi short of Martinsburg, with its arrival still shown 30 min away. Train 875 →
  • Train 876 (Aug 12): the trip disappeared from tracking about 1.6 mi short of Union Station, with its arrival still shown 15 min away. Train 876 →
  • Train 881 (Aug 27): the trip disappeared from tracking about 0.9 mi short of Martinsburg, with its arrival still shown 11 min away. Train 881 →
  • Train 895 (Aug 26): the trip disappeared from tracking about 1 mi short of Frederick, with its arrival still shown 3 min away. Train 895 →

No position published

  • Train 879 — 2 days (Aug 7, Aug 13): no position was published for part of the trip. Train 879 →
  • Train 891 (Aug 10): no position was published for 40 min while the train covered about 18.5 mi. Train 891 →

Position published, no trip data

  • Train 409 (Aug 13): no trip data was published for the train, although its position showed it running about 21.6 mi along its route. Train 409 →
  • Train 840 (Aug 17): no trip data was published for the train, although its position showed it running about 27 mi along its route. Train 840 →

Positions in two places at once

  • Train 407 — 2 days (Aug 12, Aug 14): the trip showed positions in two places at once. Train 407 →
  • Train 426 — 2 days (Aug 11, Aug 26): the trip showed positions in two places at once. Train 426 →
  • Train 511 — 2 days (Aug 13, Aug 24): the trip showed positions in two places at once. Train 511 →
  • Train 430 (Aug 14): the trip showed positions in two places at once, about 8 mi apart. Train 430 →
  • Train 455 (Aug 17): the trip showed positions in two places at once, about 34.1 mi apart. Train 455 →
  • Train 532 (Aug 19): the trip showed positions in two places at once, about 4 mi apart. Train 532 →
  • Train 537 (Aug 12): the trip showed positions in two places at once, about 28 mi apart. Train 537 →
  • Train 613 (Aug 31): the trip showed positions in two places at once, about 6.6 mi apart. Train 613 →
  • Train 848 (Aug 10): the trip showed positions in two places at once, about 3.8 mi apart. Train 848 →
  • Train 858 (Aug 6): the trip showed positions in two places at once, about 18.8 mi apart. Train 858 →

Predicted times stopped updating

  • Train 403 (Aug 25): predicted times stopped updating for 15 min while the train moved about 0.6 mi, and the time shown for West Baltimore passed before the train got there. Train 403 →
  • Train 430 (Aug 11): predicted times stopped updating for 19 min while the train moved about 16.3 mi, and the time shown for BWI Airport passed before the train got there. Train 430 →
  • Train 536 (Aug 24): predicted times stopped updating for 25 min, and the time shown for Perryville passed before the train got there. Train 536 →
  • Train 841 (Aug 10): predicted times stopped updating for 18 min, and the time shown for Union Station passed before the train got there. Train 841 →
  • Train 843 (Aug 21): predicted times stopped updating for 42 min, and the time shown for Union Station passed before the train got there. Train 843 →
  • Train 852 (Aug 28): predicted times stopped updating for 17 min, and the time shown for Dorsey passed before the train got there. Train 852 →
  • Train 853 (Aug 10): predicted times stopped updating for 27 min while the train moved about 0.2 mi, and the time shown for Greenbelt passed before the train got there. Train 853 →
  • Train 873 (Aug 10): predicted times stopped updating for 73 min, and the time shown for Point of Rocks passed before the train got there. Train 873 →
  • Train 877 (Aug 10): predicted times stopped updating for 17 min, and the time shown for Dickerson passed before the train got there. Train 877 →
  • Train 879 (Aug 10): predicted times stopped updating for 19 min, and the time shown for Barnesville passed before the train got there. Train 879 →
  • Train 891 (Aug 10): predicted times stopped updating for 18 min, and the time shown for Washington Grove passed before the train got there. Train 891 →
  • Train 893 (Aug 10): predicted times stopped updating for 24 min, and the time shown for Barnesville passed before the train got there. Train 893 →
  • Train 895 (Aug 10): predicted times stopped updating for 22 min, and the time shown for Germantown passed before the train got there. Train 895 →

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

← All months · MARC