Amtrak time zones: why the clock looks wrong on long trips
Every time in an Amtrak timetable is the local time at that stop, not the time where the train started. On a trip that stays in one zone you will never notice. On a trip that crosses a zone line, the arithmetic stops working unless you allow for it.
A real example: 26 minutes that take 86
The Southwest Chief, train 3, leaves Garden City, Kansas at 5:05 AM Central and reaches Lamar, Colorado at 5:31 AM Mountain. Read as plain clocks that is 26 minutes. The state line sits in between, so the train is really moving for 1 hour 26 minutes.
Long trips: count from the timetable, not the clock
The Empire Builder, train 7, leaves Chicago at 3:05 PM Central and reaches Seattle at 11:29 AM Pacific on day 3. Subtract the clocks and you get 44 hours 24 minutes. The journey is 46 hours 24 minutes, because Pacific time is two hours behind Central.
The Coast Starlight, train 11, stays in Pacific time the whole way, so its 9:55 AM departure from Seattle and 9:11 PM arrival in Los Angeles the next day add up directly to 35 hours 16 minutes.
How to avoid a missed connection
If you change trains or meet someone at a stop, use the time printed for that stop. It is already local. Your phone will also switch zones by itself somewhere along the line, and that can happen some way from where the timetable changes zone, so the timetable is the better guide while you are on board.
On our train pages each stop is labelled ET, CT, MT or PT, and a note appears at the top when a train crosses a zone. Long-distance timetables can change, so check the page for your own date before you rely on a connection.