@AGTL   10m early
@AGTL: Agartala &0 km/h Way To Out PF 1

@AGTL   8m early
@AGTL: Agartala &0 km/h Way To Out AGTL Agartala 🤩😍🤩

@AGTL   8m early
@AGTL: Agartala &0 km/h Ticket Counters Entrance AGTL Agartala 🤩

@AGTL   6m early
@AGTL: Agartala &0 km/h Entrance AGTL Agartala 😍🤩🤩

@AGTL   5m early
That's It Guys..!!!! Ending This Trip... Bye Bye...!!! The End 🤩 👋❣️👋

@CTC   1h 1m late
@CTC: Cuttack Jn &0 km/h departs

@GBK 5 km <--> 1 km @BRAG   46m late
@BRAG: Barang Jn &71 km/h #12822: Dhauli Express .

@BBSN   45m late
@BBSN: Bhubaneswar New &92 km/h ..m

@MCS   36m late
@MCS: Mancheswar &57 km/h #18463: Prasanti Express parked here with 37191 VSKP WAP 7

@BBS   31m late
@BBS: Bhubaneswar &18 km/h arrived on 4

@HWH   40m late
That's It Guys..!! Ending This Trip.... Bye Bye 👋👋👋 😀

No

How is the occupancy of this train ? TPTY-VSKP and overall ?

80% To 85%

In This Journey

Sunday evening convenient dep time at 1600 to reach early morning Vskp at 400 and North Andhra in morning has made the occupancy levels up after extending to Tirupati.

Two suggestions from my side. 1st is the app crashing while taking photos. This doesn't happen in all the occassions. but maximum time it happens.

Sorry about that, and thanks for bearing with the bugs. The app is in active development - there's a whole year's worth of features yet to be built into the app!!!

Bugs will eventually be gone, and many, many more features are coming in the next few months/years.
Thanks.

That's great. We are absolutely okay with it. Another aspect sir I felt worth mentioning. When a train is entering in range of 1 km of the next station, the arrival time in that station is being set in that time when it touched 1 km mark. e.g, here in this case train arrived howrah at 4:35 whereas in route arrival time is well before it. Similar is tha case for departure from big stations where it requires time to leave 1 km radius due to speed restrictions. That I noticed in timing of Khurda, Bbs and Kgp. I am not aware of the technical aspects, but felt to mention it.

Yes, for now, we are going with this general scheme, as the signals themselves sometimes have a + or -1 km accuracy. In such cases, any accurate calculations are meaningless. So, we assume a safe conservative value for accuracy, and stamp the Arr/Dep time accordingly.

But yes, sometimes signals are much stronger, and in such cases, we can be more precise with arrival times. This will be refined as the app gets better over time.
Thanks.

I also observed the same . When train approaches station , before 1 km the update come from app As "The train is at XYZ Station" meanwhile the actual Arrival is different but in case of mps action train skips that station in few seconds so update is quite correct. Well this feature is partially correct and partially less correct. But giving manual updates makes it more correct.

However UI is a bit complex , needs to have proper instructions to use it .