Spotting
 Timeline
 Travel Tip
 Trip
 Race
 Social
 Greeting
 Poll
 Img
 PNR
 Pic
 Blog
 News
 Conf TL
 RF Club
 Convention
 Monitor
 Topic
 #
 Rating
 Correct
 Wrong
 Stamp
 PNR Ref
 PNR Req
 Blank PNRs
 HJ
 Vote
 Pred
 @
 FM Alert
 FM Approval
 Pvt
Forum Super Search
 ↓ 
×
HashTag:
Freq Contact:
Member:
Posting Date From:
Posting Date To:
Blog Category:
Train Type:
Train:
Station:
Pic/Vid:   FmT Pic:   FmT Video:
Sort by: Date:     Word Count:     Popularity:     
Public:    Pvt: Monitor:    Topics:    

Search
  Go  
dark modesite support
 
Mon Oct 21 18:43:24 IST
Home
Trains
ΣChains
Atlas
PNR
Forum
Quiz
Topics
Gallery
News
FAQ
Trips
Login
RailCal Android App
RailCal iPhone App
Post PNRPost BlogAdvanced Search
Filters:

Page#    36028 Blog Entries  <<prev  next>>
PREDICTIONS: 39
confirm: 97%
rac: 3%
wl: 0%
PREDICT



Journey: Sat Nov 02, 2024
Dep: ANVT/Anand Vihar Terminal @ 17:20 PF#: 6
Arr: DBG/Darbhanga Junction @ 12:00 +1 night
Distance: 1185 km / 1252 km
Class: AC 3-tier - 3A   |   Tot Seats: Avbl-0736#   |   Charting @13:20
12436/Anand Vihar Terminal - Jaynagar Garib Rath Express (PT)
 

PNR: 231-xxxxxxx   |   Similar PNRs
Entry# 6114880        
NO PENDING REQUEST
Posted: Jul 05 (09:15:31)  View Posted Status
Passenger 1: Waiting: WL:30 (Booking Status: WL:34:GN)
Passenger 2: Waiting: WL:31 (Booking Status: WL:35:GN)
Passenger 3: Waiting: WL:32 (Booking Status: WL:36:GN)
Passenger 4: Waiting: WL:33 (Booking Status: WL:37:GN)
Total Fare:  4040
Chart NOT Prepared
refreshed by: 2182678/Harsha_12627^~

Latest Status: Yesterday (19:05:53) 
Passenger 1: Waiting: WL:15 (Booking Status: WL:34:GN)
Passenger 2: Waiting: WL:16 (Booking Status: WL:35:GN)
Passenger 3: Waiting: WL:17 (Booking Status: WL:36:GN)
Passenger 4: Waiting: WL:18 (Booking Status: WL:37:GN)
Total Fare:  4040
Chart NOT Prepared
refreshed by: 718732/Rai_abhi^~

Full PNR Status History (31 statuses)
Status as of: Oct 19 (18:05:12)
Passenger 1: Waiting: WL:15 (Booking Status: WL:34:GN)
Passenger 2: Waiting: WL:16 (Booking Status: WL:35:GN)
Passenger 3: Waiting: WL:17 (Booking Status: WL:36:GN)
Passenger 4: Waiting: WL:18 (Booking Status: WL:37:GN)
Total Fare:  4040
Chart NOT Prepared
refreshed by: 718732/Rai_abhi^~

Status as of: Oct 16 (02:06:51)
Passenger 1: Waiting: WL:15 (Booking Status: WL:34:GN)
Passenger 2: Waiting: WL:16 (Booking Status: WL:35:GN)
Passenger 3: Waiting: WL:17 (Booking Status: WL:36:GN)
Passenger 4: Waiting: WL:18 (Booking Status: WL:37:GN)
Total Fare:  4040
Chart NOT Prepared
refreshed by: 1243573/Siddharth98^~

Status as of: Oct 10 (22:02:33)
Passenger 1: Waiting: WL:15 (Booking Status: WL:34:GN)
Passenger 2: Waiting: WL:16 (Booking Status: WL:35:GN)
Passenger 3: Waiting: WL:17 (Booking Status: WL:36:GN)
Passenger 4: Waiting: WL:18 (Booking Status: WL:37:GN)
Total Fare:  4040
Chart NOT Prepared
refreshed by: 1108853/Brandon12663^~

Status as of: Oct 09 (08:03:47)
Passenger 1: Waiting: WL:16 (Booking Status: WL:34:GN)
Passenger 2: Waiting: WL:17 (Booking Status: WL:35:GN)
Passenger 3: Waiting: WL:18 (Booking Status: WL:36:GN)
Passenger 4: Waiting: WL:19 (Booking Status: WL:37:GN)
Total Fare:  4040
Chart NOT Prepared
refreshed by: 841346/SreeNdl^~

Status as of: Oct 07 (12:15:21)
Passenger 1: Waiting: WL:16 (Booking Status: WL:34:GN)
Passenger 2: Waiting: WL:17 (Booking Status: WL:35:GN)
Passenger 3: Waiting: WL:18 (Booking Status: WL:36:GN)
Passenger 4: Waiting: WL:19 (Booking Status: WL:37:GN)
Total Fare:  4040
Chart NOT Prepared
refreshed by: 2141220/Chintu_5^~

Status as of: Oct 06 (13:38:25)
Passenger 1: Waiting: WL:16 (Booking Status: WL:34:GN)
Passenger 2: Waiting: WL:17 (Booking Status: WL:35:GN)
Passenger 3: Waiting: WL:18 (Booking Status: WL:36:GN)
Passenger 4: Waiting: WL:19 (Booking Status: WL:37:GN)
Total Fare:  4040
Chart NOT Prepared
refreshed by: 2053772/Puneri_Railfan^~

Status as of: Oct 06 (12:37:09)
Passenger 1: Waiting: WL:16 (Booking Status: WL:34:GN)
Passenger 2: Waiting: WL:17 (Booking Status: WL:35:GN)
Passenger 3: Waiting: WL:18 (Booking Status: WL:36:GN)
Passenger 4: Waiting: WL:19 (Booking Status: WL:37:GN)
Total Fare:  4040
Chart NOT Prepared
refreshed by: 2141220/Chintu_5^~

Status as of: Oct 05 (07:13:14)
Passenger 1: Waiting: WL:16 (Booking Status: WL:34:GN)
Passenger 2: Waiting: WL:17 (Booking Status: WL:35:GN)
Passenger 3: Waiting: WL:18 (Booking Status: WL:36:GN)
Passenger 4: Waiting: WL:19 (Booking Status: WL:37:GN)
Total Fare:  4040
Chart NOT Prepared
refreshed by: 1777975/jishnuthakur12301^~

Status as of: Sep 29 (12:33:48)
Passenger 1: Waiting: WL:16 (Booking Status: WL:34:GN)
Passenger 2: Waiting: WL:17 (Booking Status: WL:35:GN)
Passenger 3: Waiting: WL:18 (Booking Status: WL:36:GN)
Passenger 4: Waiting: WL:19 (Booking Status: WL:37:GN)
Total Fare:  4040
Chart NOT Prepared
refreshed by: 2228377/AbhinavKr^~

Status as of: Sep 22 (08:56:19)
Passenger 1: Waiting: WL:18 (Booking Status: WL:34:GN)
Passenger 2: Waiting: WL:19 (Booking Status: WL:35:GN)
Passenger 3: Waiting: WL:20 (Booking Status: WL:36:GN)
Passenger 4: Waiting: WL:21 (Booking Status: WL:37:GN)
Total Fare:  4040
Chart NOT Prepared
refreshed by: 2053772/Puneri_Railfan^~

Status as of: Sep 22 (08:40:39)
Passenger 1: Waiting: WL:18 (Booking Status: WL:34:GN)
Passenger 2: Waiting: WL:19 (Booking Status: WL:35:GN)
Passenger 3: Waiting: WL:20 (Booking Status: WL:36:GN)
Passenger 4: Waiting: WL:21 (Booking Status: WL:37:GN)
Total Fare:  4040
Chart NOT Prepared
refreshed by: 1243573/Siddharth98^~

Status as of: Sep 17 (22:51:22)
Passenger 1: Waiting: WL:18 (Booking Status: WL:34:GN)
Passenger 2: Waiting: WL:19 (Booking Status: WL:35:GN)
Passenger 3: Waiting: WL:20 (Booking Status: WL:36:GN)
Passenger 4: Waiting: WL:21 (Booking Status: WL:37:GN)
Total Fare:  4040
Chart NOT Prepared
refreshed by: 42126/Jayashree^

Status as of: Sep 13 (17:02:02)
Passenger 1: Waiting: WL:19 (Booking Status: WL:34:GN)
Passenger 2: Waiting: WL:20 (Booking Status: WL:35:GN)
Passenger 3: Waiting: WL:21 (Booking Status: WL:36:GN)
Passenger 4: Waiting: WL:22 (Booking Status: WL:37:GN)
Total Fare:  4040
Chart NOT Prepared
refreshed by: 1243573/Siddharth98^~

Status as of: Sep 08 (08:42:50)
Passenger 1: Waiting: WL:19 (Booking Status: WL:34:GN)
Passenger 2: Waiting: WL:20 (Booking Status: WL:35:GN)
Passenger 3: Waiting: WL:21 (Booking Status: WL:36:GN)
Passenger 4: Waiting: WL:22 (Booking Status: WL:37:GN)
Total Fare:  4040
Chart NOT Prepared
refreshed by: 2141220/Chintu_5^~

Status as of: Sep 01 (16:58:04)
Passenger 1: Waiting: WL:20 (Booking Status: WL:34:GN)
Passenger 2: Waiting: WL:21 (Booking Status: WL:35:GN)
Passenger 3: Waiting: WL:22 (Booking Status: WL:36:GN)
Passenger 4: Waiting: WL:23 (Booking Status: WL:37:GN)
Total Fare:  4040
Chart NOT Prepared
refreshed by: 1243573/Siddharth98^~

Status as of: Sep 01 (08:58:49)
Passenger 1: Waiting: WL:20 (Booking Status: WL:34:GN)
Passenger 2: Waiting: WL:21 (Booking Status: WL:35:GN)
Passenger 3: Waiting: WL:22 (Booking Status: WL:36:GN)
Passenger 4: Waiting: WL:23 (Booking Status: WL:37:GN)
Total Fare:  4040
Chart NOT Prepared
refreshed by: 12/moderator^~

Status as of: Aug 31 (06:19:17)
Passenger 1: Waiting: WL:20 (Booking Status: WL:34:GN)
Passenger 2: Waiting: WL:21 (Booking Status: WL:35:GN)
Passenger 3: Waiting: WL:22 (Booking Status: WL:36:GN)
Passenger 4: Waiting: WL:23 (Booking Status: WL:37:GN)
Total Fare:  4040
Chart NOT Prepared
refreshed by: 248735/ForeverRailfan^~

Status as of: Aug 30 (16:01:54)
Passenger 1: Waiting: WL:20 (Booking Status: WL:34:GN)
Passenger 2: Waiting: WL:21 (Booking Status: WL:35:GN)
Passenger 3: Waiting: WL:22 (Booking Status: WL:36:GN)
Passenger 4: Waiting: WL:23 (Booking Status: WL:37:GN)
Total Fare:  4040
Chart NOT Prepared
refreshed by: 12/moderator^~

Status as of: Aug 26 (19:59:17)
Passenger 1: Waiting: WL:22 (Booking Status: WL:34:GN)
Passenger 2: Waiting: WL:23 (Booking Status: WL:35:GN)
Passenger 3: Waiting: WL:24 (Booking Status: WL:36:GN)
Passenger 4: Waiting: WL:25 (Booking Status: WL:37:GN)
Total Fare:  4040
Chart NOT Prepared
refreshed by: 1243573/Siddharth98^~

Status as of: Aug 26 (14:18:51)
Passenger 1: Waiting: WL:22 (Booking Status: WL:34:GN)
Passenger 2: Waiting: WL:23 (Booking Status: WL:35:GN)
Passenger 3: Waiting: WL:24 (Booking Status: WL:36:GN)
Passenger 4: Waiting: WL:25 (Booking Status: WL:37:GN)
Total Fare:  4040
Chart NOT Prepared
refreshed by: 718732/Rai_abhi^~

Status as of: Aug 24 (13:48:35)
Passenger 1: Waiting: WL:22 (Booking Status: WL:34:GN)
Passenger 2: Waiting: WL:23 (Booking Status: WL:35:GN)
Passenger 3: Waiting: WL:24 (Booking Status: WL:36:GN)
Passenger 4: Waiting: WL:25 (Booking Status: WL:37:GN)
Total Fare:  4040
Chart NOT Prepared
refreshed by: 2141220/Chintu_5^~

Status as of: Aug 18 (23:23:06)
Passenger 1: Waiting: WL:23 (Booking Status: WL:34:GN)
Passenger 2: Waiting: WL:24 (Booking Status: WL:35:GN)
Passenger 3: Waiting: WL:25 (Booking Status: WL:36:GN)
Passenger 4: Waiting: WL:26 (Booking Status: WL:37:GN)
Total Fare:  4040
Chart NOT Prepared
refreshed by: 2053772/CivilEngineer_cum_Railfan^~

Status as of: Aug 09 (15:25:57)
Passenger 1: Waiting: WL:23 (Booking Status: WL:34:GN)
Passenger 2: Waiting: WL:24 (Booking Status: WL:35:GN)
Passenger 3: Waiting: WL:25 (Booking Status: WL:36:GN)
Passenger 4: Waiting: WL:26 (Booking Status: WL:37:GN)
Total Fare:  4040
Chart NOT Prepared
refreshed by: 1243573/Siddharth98^~

Status as of: Jul 22 (21:17:17)
Passenger 1: Waiting: WL:26 (Booking Status: WL:34:GN)
Passenger 2: Waiting: WL:27 (Booking Status: WL:35:GN)
Passenger 3: Waiting: WL:28 (Booking Status: WL:36:GN)
Passenger 4: Waiting: WL:29 (Booking Status: WL:37:GN)
Total Fare:  4040
Chart NOT Prepared
refreshed by: 1243573/Siddharth98^~

Status as of: Jul 22 (18:10:21)
Passenger 1: Waiting: WL:26 (Booking Status: WL:34:GN)
Passenger 2: Waiting: WL:27 (Booking Status: WL:35:GN)
Passenger 3: Waiting: WL:28 (Booking Status: WL:36:GN)
Passenger 4: Waiting: WL:29 (Booking Status: WL:37:GN)
Total Fare:  4040
Chart NOT Prepared
refreshed by: 2141220/Chintu_5^~

Status as of: Jul 21 (07:59:37)
Passenger 1: Waiting: WL:26 (Booking Status: WL:34:GN)
Passenger 2: Waiting: WL:27 (Booking Status: WL:35:GN)
Passenger 3: Waiting: WL:28 (Booking Status: WL:36:GN)
Passenger 4: Waiting: WL:29 (Booking Status: WL:37:GN)
Total Fare:  4040
Chart NOT Prepared
refreshed by: 1332893/TAGEERUANUBHARADWAJ^

Status as of: Jul 11 (22:23:23)
Passenger 1: Waiting: WL:26 (Booking Status: WL:34:GN)
Passenger 2: Waiting: WL:27 (Booking Status: WL:35:GN)
Passenger 3: Waiting: WL:28 (Booking Status: WL:36:GN)
Passenger 4: Waiting: WL:29 (Booking Status: WL:37:GN)
Total Fare:  4040
Chart NOT Prepared
refreshed by: 1243573/Siddharth98^~

Status as of: Jul 10 (12:04:47)
Passenger 1: Waiting: WL:26 (Booking Status: WL:34:GN)
Passenger 2: Waiting: WL:27 (Booking Status: WL:35:GN)
Passenger 3: Waiting: WL:28 (Booking Status: WL:36:GN)
Passenger 4: Waiting: WL:29 (Booking Status: WL:37:GN)
Total Fare:  4040
Chart NOT Prepared
refreshed by: 248735/ForeverRailfan^~

Status as of: Jul 07 (04:33:40)
Passenger 1: Waiting: WL:26 (Booking Status: WL:34:GN)
Passenger 2: Waiting: WL:27 (Booking Status: WL:35:GN)
Passenger 3: Waiting: WL:28 (Booking Status: WL:36:GN)
Passenger 4: Waiting: WL:29 (Booking Status: WL:37:GN)
Total Fare:  4040
Chart NOT Prepared
refreshed by: 12/moderator^~

Status as of: Jul 05 (09:21:18)
Passenger 1: Waiting: WL:30 (Booking Status: WL:34:GN)
Passenger 2: Waiting: WL:31 (Booking Status: WL:35:GN)
Passenger 3: Waiting: WL:32 (Booking Status: WL:36:GN)
Passenger 4: Waiting: WL:33 (Booking Status: WL:37:GN)
Total Fare:  4040
Chart NOT Prepared
refreshed by: 2182678/Harsha_12627^~

Status as of: Jul 05 (09:15:31)


PREDICTIONS
Status
Date
Member
Stars
Accuracy
confirm
Jul 05 (09:23)
 
confirm
Jul 05 (09:41)
confirm
Jul 05 (11:04)
 
confirm
Jul 05 (11:47)
 
confirm
Jul 05 (12:19)
 ★★
confirm
Jul 05 (16:31)
 ★★★
confirm
Jul 05 (16:44)
confirm
Jul 05 (18:47)
 
confirm
Jul 05 (22:21)
 ★★
confirm
Jul 07 (16:15)
confirm
Jul 07 (23:26)
confirm
Jul 08 (13:35)
 ★★
confirm
Jul 08 (23:06)
guest
 
confirm
Jul 09 (00:04)
 
confirm
Jul 09 (06:47)
confirm
Jul 09 (09:13)
 
confirm
Jul 09 (13:04)
 
confirm
Jul 09 (19:59)
confirm
Jul 11 (06:49)
 
confirm
Aug 03 (11:04)
 ★★
confirm
Aug 10 (15:15)
confirm
Aug 15 (21:39)
 ★★
confirm
Sep 01 (21:27)
confirm
Sep 04 (17:54)
 
confirm
Sep 09 (00:38)
guest
confirm
Sep 16 (18:57)
confirm
Sep 30 (23:43)
 
confirm
Oct 09 (08:43)
 
confirm
Oct 14 (17:46)
 
confirm
Yday (10:57:48)
 
confirm
Yday (10:58:11)
 
confirm
Yday (11:22:10)
 
confirm
Yday (14:14:08)
 
confirm
Yday (15:08:20)
confirm
Yday (19:04:13)
 ★★★

1 Public Posts - Mon Jul 08, 2024

1 Public Posts - Wed Oct 09, 2024

4555 views
0

Oct 14 (17:09)
Ritikwa08
Ritikwa08   0 blog posts
Re# 6114880-3              
High chances of getting confirmation
Translate to English
Translate to Hindi

1 Public Posts - Mon Oct 14, 2024

1 Public Posts - Yesterday
Social
2278 views
0

Oct 14 (01:53)  
SekarMadras~
SekarMadras~   947 blog posts
Entry# 6218546               Past Edits
Unusually high rain reported in karaikudi, madurai, salem, pudukottai. Chennai to see rains on 15-18. Coimbatore also received good rainfall, we could see heavy traffic in Avinashi road with vehicles literally swimming in water. My area (Sholavaram) already seeing rain now.
Translate to English
Translate to Hindi
General Travel
28940 views
2

Oct 11 (23:10)   12578/Bagmati Superfast Express (PT)
Rail12345
Rail12345   2647 blog posts
Entry# 6216546            Tags  
Another accident. Another derailment happened today. Major accident, LHB coaches climbed one above another and also fire in LVP. Our ACCIDENT SPECIALIST RAILWAY MINISTER will still not Resign. Still greedy RM will hold his chair after so many accidents in his kitty in the history of IR.
Pics colect.
Translate to English
Translate to Hindi

1 Public Posts - Fri Oct 11, 2024

1 Public Posts - Sat Oct 12, 2024

12456 views
2

Oct 12 (17:26)
Baaz_SGUJ_WDP4~
Baaz_SGUJ_WDP4~   0 blog posts
Re# 6216546-3               Past Edits
A couple of similarities be noted about this accident:
1. Last year on the same day and around same time, NorthEast Express derailed at Raghunathpur station. The train was full LHB and its coaches toppled in similar manner as Bagmati
2. One of the reasons of collision is said to be signal failure. Earlier, Kanchanjungha express collided with goods train in similar manner and the reason was said to be signal failure. Likewise, Coromandel Express rammed to a goods train standing on loop line couple of years back.
...
more...


It is high time that Railway starts taking accountability. The morale thing that IR can do is to disclose the information about signal failures, and all the other limitations in advance to public so that people can decide whether they want to take the risk of travelling. But as we all know, no govt no politicalparty would do this as that would question their accountability towards their duties etc. Accountability is the last thing politicians would take.

Translate to English
Translate to Hindi
Travelogue
57484 views
28

★★★
Oct 12 (13:16)   12032/Amritsar - New Delhi Shatabdi Express | JUC/Jalandhar City Junction (5 PFs)
GaganB~
GaganB~   1316 blog posts
Entry# 6216971            Tags   Past Edits
20 compliments
Great Great:Nice writeup. Great Great:Amazing writeup! Totally enjoyed :) Great Great Great Great:Wow bro Great Great Useful Great Great Great Great Great Great Great Great:Awesome writeup 🎉⚡🔥 Great
#Travelogue
My first solo long distance train journey in India

After spending around 2.5 years in Canada, I came back to India on October 1, 2023. Even though the friendship between me and trains date back to my childhood, but I had never travelled in a long distance train alone.
...
more...

So, I decided to do a solo trip to Mangalore. It was the time between Dussehra and Diwali, in November of 2023. I decided to book my tickets in 22656 NZM - ERS SF Express, which was in waiting but I still decided to go for it as the W/L was just 3 and it was still more than a week for my journey. The journey was from Nizamuddin while I am living in Jalandhar district, so it was time to book for my second train, the first of the journey, to go to Delhi. I had a lot of options like Golden Temple Mail and Chhattisgarh Express that would take me directly to Nizamuddin without station hopping. But my father suggested me to book for an earlier train, so i booked in 12032 ASR - NDLS Shatabdi Express making it my first journey in a premium train.

Now the journey day, 3rd of November 2023. I left my home at 4 in the evening and caught a bus towards Jalandhar. De-boarded the bus 2 km before my scheduled stop. I was to get off at Pathankot Chowk/Bypass, but I de-boarded 2 kms before when my bus stopped. Started walking and got an auto to reach Jalandhar City JN just 5 minutes later. The train arrived 10 minutes after the scheduled time i was allotted an aisle seat on the 2 seat side, but seeing the window seat empty, i sat on it thinking I will get up when my co-passenger shows up and asks me to leave his/her seat. My co passenger came at Phagwara but he didn’t say anything about me occupying his seat and started to do his work. The train’s next halts were Ludhiana, Rajpura and Ambala Cantt, didn’t make any unscheduled halts and after Ambala Cantt, the train continued its high speed run up to Sabzi Mandi. Then it crawled all the way up to New Delhi, stopping a few times in that 4-5 km journey eventually arriving 10-20 minutes delayed.

After arriving at New Delhi, I decided to take the NDLS - PLWL EMU that leaves at 00:15 hrs from NDLS as i had seen on IRI but the platform of that keeps changing as informed by one staff member at NDLS “Bhai wo kahi pe bhi aa jaati hai” and told me to follow the LED boards on the foot over bridge. I followed and saw the number 04440 over platform number 8 if I remember correctly. Its rake was getting placed on the platform as I was walking with it. Found an empty cabin and sat on a seat. The EMU departed and after 10-12 minutes, I was at Hazrat Nizamuddin station.

Now, the real wait begins.

I decided to wait on the platform instead of going to a waiting room. The station was fairly empty as the passenger movement and train movement is quite less in the middle of the night. At 4 in the morning, I was pretty sure that the rake will be placed by 4:30 but the wait wasn’t over. And did I tell you that my ticket got confirmed. Yes it did and I got Side Lower berth yay 🥳.

Anyways, the rake was placed exactly at 5 am, at the time of departure. I quickly found my seat in A1 coach and did my bedding. I laid down as the train departed at 5:35, 35 minutes delayed. I slept soon enough as I hadn’t slept the whole night. The train halted at its usual halts Mathura and Bharatpur as I was catching some zzzzzzzzz. At Bharatpur, I saw some train overtaking us, It was 22414 NZM - MAO Rajdhani Express. The delay was quite much when the train left Sawai Madhopur but it was mostly covered till Kota JN. My eyes were wide open looking through the window enjoying the views as the train was continuously running at 130 kmph. Ulysse Speedometer rocks haha. Most of the delay was covered until Vadodara and now it was time to get some food. I decided to go for e-catering at Surat. I opened the app and decided to order from Tipsy - Topsy restaurant as I had heard about it a lot. I got my food delivered at Surat and it took me 10 minutes just to open the plastic seal yes the heat seal was too much but the taste of the food made up for the frustration. After Surat, my co passenger, the passenger from the upper berth got down as his stop as approaching, we talked for a bit about our destinations and he eventually got off at Vapi, I lied down for the night and the train arrived at Vasai Road at almost its scheduled time, albeit a few minutes delayed. The coach was half empty at this point and at Panvel, some ladies came to their allotted adjacent seats. I slept soon enough and woke up when the train was traversing through the mountains, rivers and forests of Konkan region. I was mesmerised by all of it and clicked a lot of pictures and made some videos. Now the train was more than an hour delayed, reason i don’t know. The train halted at Karmali for good 10 minutes and covered a lot of its delay until Madgaon. It was a great humid experience in Goa in November, thanks to Arabian Sea. After departure from Madgaon, the train soon entered in Karnataka, the first halt of the state was, Karwar, a small but beautiful station. The train had some unscheduled halts between Karwar and Udupi but the real torture began after departure from Udupi. Even though, the train gained a respectable speed of 100 kmph but it lasted for a couple of minutes until Nandikoor, the train halted there for quite some time and the story of unscheduled halts continued until my destination, Mangaluru JN. Now, the reason of all the unscheduled halts was 01185 LTT - MAJN Special Express, kinda unbelievable as the special train was getting more priority than our SuperFast train. Anyways, the train arrived Mangaluru after a delay of more than an hour.

Took me quite some time to envision and pen down.

Thanks for reading such a long article

-Gagan

Translate to English
Translate to Hindi

5 Public Posts - Sat Oct 12, 2024

20996 views
2

Oct 12 (16:43)
ManikBaashha^~
ManikBaashha^~   3546 blog posts
Re# 6216971-7              
1 compliments
Thanks
Lucid writing, well written. I wondered how you whiled away your time of 240+ minutes at night in NZM. IMO, your travelogue was brief and crisp (since you have mentioned it was a lengthier one). Also, you have chosen one of the best months to travel through konkan to witness it's beauty (post monsoon) in which both high speed run in and the lush greenery both could be witnessed. The pristine beauty of konkan is such that it will make us to take more photos. It has been very long since I have travelled via konkan.
Translate to English
Translate to Hindi

3 Public Posts - Sat Oct 12, 2024
Travel Question
32308 views
3

Oct 11 (09:48)   02269/Chhapra - Lucknow Special Fare Vande Bharat Festival Special
kirk781^~   4510 blog posts
Entry# 6215780            Tags  
1 compliments
Agree
This train will have sitting coaches like normal VB? Alternatively, why not run a normal M/E train; often the best solution is the simplest one. Run something that suits everyone.
Translate to English
Translate to Hindi

2 Public Posts - Fri Oct 11, 2024

14098 views
7

Oct 11 (12:05)
deepak.yerr~
deepak.yerr~   6772 blog posts
Re# 6215780-3              
2 compliments
Agree Useful
The seats of VB have an inclination or recline angle of 19.5 deg where as in Volvo or night service buses the recline angle is 40 deg, lighting is put off which help in sleep while in train ACC you have full lighting with high lux. So buses cannot be compared with night ACC. Further night buses in past 10 years have upgraded to AC sleeper buses all over India.

As Merrut Lucknow is running with 2 rakes this spl is introduced and returning in night to have regular 4
...
more...
hrs maintainance schedule in morning before departing to Merrut in afternoon.

Translate to English
Translate to Hindi

3 Public Posts - Fri Oct 11, 2024

2 Public Posts - Sat Oct 12, 2024

11014 views
2

Oct 12 (10:29)
GomtinagarTerminal~
GomtinagarTerminal~   0 blog posts
Re# 6215780-9              
Exactly. Vande Bharats are good, but not beyond 4-5 hours. The cons, imo, are lack of privacy or the silence you want in travelling (CC Coaches), passengers talking in the front is clearly audible in the back rows. The sounds get amplified if group of people/families are travelling in this together (Some of this maybe related to lack of civic sense, which i hope we will learn eventually), nonetheless, it becomes sheer discomfort for lone passenger. The problem aggravates if you are sitting in the middle in 3 seat configuration. (These are some of the issues i faced when i travel in ANVT-AY VB).

Although,
...
more...
the LKO Tejas, which probably due to high fares( probably runs with 20-30% occupancy in weekdays), is quite a pleasure, but it burns your pocket. For 8-10 hour journeys, i feel night riders are best.

(Personal opinion, no offence intended)
Happy Dussehra

Translate to English
Translate to Hindi

1 Public Posts - Sat Oct 12, 2024

9799 views
2

Oct 12 (11:49)
deepak.yerr~
deepak.yerr~   6772 blog posts
Re# 6215780-11              
Executive class seats have more recline then normal ACC, more leg space or seat pitch, wide seat with arm rests, better cushioning and high head rest.
Translate to English
Translate to Hindi

1 Public Posts - Sat Oct 12, 2024

1 Public Posts - Mon Oct 14, 2024
Page#    36028 Blog Entries  <<prev  next>>

Travel SAFE

1. RailFanning does NOT MEAN dangerous pics/videos.
2. Doorplating pics/youtube videos are strictly FORBIDDEN in IRI.
3. Take plenty of food pics and other safe pics.
4. Write human interest narratives to make the pics interesting.
5. Enjoy blogging and travelling SAFELY.

REMEMBER: YOUR LIFE is the most precious thing, NOT RailFanning.

Leading Polls

Rail News

New Trains

Site Announcements

  • Entry# 5648027
    Mar 01 2023 (12:44AM)


    In response to past confusions with Train/Station updates and resulting fights and controversies, the following clear and objective guidelines are being issued, with no room for any arguments or debates about validity. Also, included, some other changes with respect to Ratings. 1. All Red Ratings will require further explanation. Red Ratings won't...
  • Entry# 5388512
    Jun 24 2022 (08:45AM)


    As announced previously, there are a few changes coming to IRI user accounts, based on past practices. 1. As before, you will be able to quickly DELETE your IRI User account at ANY time. However, the menu option for this was hidden in the profile page, and could not easily be located....
  • Entry# 5148000
    Nov 29 2021 (06:40AM)


    A new feature will be released soon, whereby you can follow blogs tagged with specific Trains & Stations. If you have already posted blogs tagged with some Train/Station, then you will be set to automatically follow that Train/Station. Thereafter, any future news/blogs tagged with those Trains/Stations will be marked to your...
  • Entry# 5093784
    Oct 13 2021 (07:04AM)


    These days, every other day, we are getting requests from members to allow email login to their FB-based IRI account. 10 years ago, we had given the option for users to login through FaceBook - in retrospect, this was a mistake. These days, apparently, users are quitting FaceBook in droves because...
  • Entry# 4906979
    Mar 14 2021 (01:12AM)


    Followup to: Fmt Changes The new version of FmT 2.0 will soon be here - in about 2 weeks. As detailed in the previous announcement, many of the old FmT features like Train TT, Speedometer, Geo Location, etc. will be REMOVED. It will be a bare-bones simple app, focused on trip blogging. It...
  • Entry# 4898771
    Mar 06 2021 (10:33PM)


    There are some changes coming to FMT. Many of the features of FMT, like station arrival, TT, speed, geo, passing times, station time, etc. are ALREADY available in OTHER railway apps. So all of these features will be REMOVED. We'll have ONLY BLOGGING - quick upload of pics/videos/audio, etc. You may attach...
Scroll to Top
Scroll to Bottom
Go to Mobile site
Important Note: This website NEVER solicits for Money or Donations. Please beware of anyone requesting/demanding money on behalf of IRI. Thanks.
Disclaimer: This website has NO affiliation with the Government-run site of Indian Railways. This site does NOT claim 100% accuracy of fast-changing Rail Information. YOU are responsible for independently confirming the validity of information through other sources.
India Rail Info Privacy Policy