Search results

I speculate that Amtrak would just combine trains at that point...but I don't know the answer offhand.

Good point about the origin station already having a delay in the reply I posted earlier....I missed that. It looks like this is the winner for the train departing on-time having the biggest delay: History for Amtrak 1 originating 02/06/2012 (Mo) * THIS TRAIN EXPERIENCED A SERVICE...

According to ASMAD the latest train in the Amtrak Status Maps records is #8 that departed Seattle on March 17, 2017 (we have data back to 2006). At Williston, ND (WTN) #8 was 40 hours and 29 minutes late, but ended up arriving into Chicago just 39 hours late. So there is still recovery time...

And my archive records are JB's records. :)

Regarding the timetables, I see what they did. Even though Train Schedules & Timetables | Amtrak has the timetables listed they all go to a temporary page. I keep an archive of them at Amtrak Timetable Archives - Home so you can always browse them there. They are current as of the last...

Yes, I see 7/8 are back. Although they are both missing their final destination.....unless they aren't running all the way to SEA or CHI. :)

I don't retrieve the data for the maps - I just know it is 2 different sources and the source with the GPS data is not showing 7/8.

But 7/8 are still showing up on the map at Amtrak Status Maps - West

The author of NA Intercity Rail Tools noticed that problem, too. He believes it's because 7 and 8 have added MKA and SVT to make up for the Hiawatha cutbacks. So a bug on Amtrak's side. I emailed them last week but just got a generic response.

I maintain an archive of Amtrak timetables back to 2009. They are at Amtrak Timetable Archives - Home If you search "amtrak timetables archives" in Google or Bing, etc. it usually shows up near the top of the results.

I think the estimated time is better, too. PRR60, I didn't know Acela dropped "Express". Thanks for that tidbit.

I also see it working again using Chrome and Microsoft Edge on Windows 10. I couldn't get it to work in Firefox, either.

Here ya go....about 1 hr, 45 min late on average since May 1st. https://juckins.net/amtrak_status/archive/html/historychart.php?train_num=92&station=nyp&date_start=05/01/2019&date_end=08/10/2019&sort=d_ar&chartsize=2&smooth=0

Anderson may be well-meaning but I don't like the LD cut plans in favor of corridor service. Can you imagine trying to run a Charlotte-Atlanta-Birmingham corridor under NS? Instead of 2 trains 3 hours late you'd have a dozen. Also, unless the hosts get a massive amount of funding they won't...

In the hearing on June 26, Anderson said something about the Hoosier state and "running with extra empty cars to fix the problem". I didn't understand his answer. It was in reference from a Senator's question about "short shunting", I think. Did anyone catch that exchange and know what he...

Thanks, webarchive, and there is also a link to old National Timetables at: https://juckins.net/amtrak_timetables/archive/home.php#Amtrak_National_System_Timetables

I also keep a list of current and past timetables at https://juckins.net/amtrak_timetables/archive/home.php When Amtrak gets an updated version I post it there.

ASMAD can tell you... That is a solid connection. Here's a link with the data for past 90 days or so...

That's sad to hear - mom and I met Joe on the westbound Zephyr several summers ago.  He was a wonderfully personable guy and let us tour his office car.  Although not everyone agreed with all of his decisions, he seemed to be respected by many in the company.

With the NB consist originating in ATL, does anyone know if the diner will serve dinner those days? I can probably guess the answer...