Full Site Search  
Sun Jun 25, 2017 04:03:49 IST
PostPostPost Trn TipPost Trn TipUpload Train PicUpload Train PicAdvanced Search
Forum Super Search
Blog Entry#:

Posting Date From:
Posting Date To:
Train Type:
ONLY with Pic/Vid:
Sort by: Date:     Word Count:     Popularity:     
Public:    Pvt: Monitor:    RailFan Club:    

Details Edit
Large TB;
Entry# 615993-0
Details Edit
Large TB;
Entry# 1429279-0
Details Edit
Large TB;
Entry# 1673069-0
Details Edit
Close-up; Front-facing; Large TB; Outside of Train; Standing at Station;
Entry# 2177876-0
Refresh Live Status (not updated)

12825/Jharkhand Sampark Kranti Express
     झारखंड संपर्क क्रांति एक्सप्रेस

RNC/Ranchi Junction --> NDLS/New Delhi

Updated: Oct 01 2016 (02:11) by Nitish kumar*^~
Oct 01 2016 (02:11)

Train Forum

Page#    281 blog entries  next>>
General Travel
Jun 03 2017 (16:48)   12825/Jharkhand Sampark Kranti Express

Apporv   17 blog posts   8 correct pred (78% accurate)
Entry# 2305902            Tags   Past Edits
See the difference how a superfast train gets priority in SER & ECR zones as compared to NCR zone.

Jun 22 2017 (14:32)
DhnEcr~   5358 blog posts
Re# 2305902-1            Tags   Past Edits
The down story. Covered Mgs-GMO in 4hr 50 mins at 80avg speed
General Travel
May 24 2017 (19:21)   12826/Jharkhand Sampark Kranti Express | ALD/Allahabad Junction (10 PFs)

Akshay gupta~   560 blog posts   4 correct pred (44% accurate)
Entry# 2291121            Tags   Past Edits
GZB WAP1 #22037 with Jharkkhand sampark kranti
General Travel
Apr 10 2017 (09:29)   12825/Jharkhand Sampark Kranti Express

xxxx~   799 blog posts   36 correct pred (56% accurate)
Entry# 2229132            Tags   Past Edits
It should be extended to Jemshedpur

22 posts - Apr 2017

Jun 02 2017 (01:49)
Sachin Sinha   532 blog posts   5 correct pred (53% accurate)
Re# 2229132-23            Tags   Past Edits
Is saal ban jaayega

Jun 02 2017 (02:02)
Sachin Sinha   532 blog posts   5 correct pred (53% accurate)
Re# 2229132-24            Tags   Past Edits
Ji ji le jaaiye sab kuch le jaaiye
GR K time mein bhi ghatiya politics ki gayi thi.. aur kya kya chalana h dto tori route pe?
Purushottam neelanchal even BBS Raj.. 12817 ko bhi usi route pe chalaiye saato din

Jun 02 2017 (10:50)
May i have your attention plzz~   807 blog posts   3 correct pred (100% accurate)
Re# 2229132-25            Tags   Past Edits
Avi to chance kam hai banne ka, last year karib 15 crore ki revenue tha BKSC ka aur A1 banne k liye atleast 60core revenue ka jarurat hai

Jun 02 2017 (10:59)
Sachin Sinha   532 blog posts   5 correct pred (53% accurate)
Re# 2229132-26            Tags   Past Edits
Paper mein aaya tha idhar isliye bol rhe hain

Jun 02 2017 (11:01)
May i have your attention plzz~   807 blog posts   3 correct pred (100% accurate)
Re# 2229132-27            Tags   Past Edits
Paper wall ne to VS ko 1saal pehle hi LHB de diya tha lekin avi tak kuch nhi mila usse, so never trust Indian newspapers
Predictions: 22
confirm: 21
rac: 0
wl: 1
Journey: Wed May 03, 2017 @ 06:55
Class: AC 2-tier - 2A   |   Tot Seats: Avbl 10   |   Charting: < 23:15
Travel: NDLS/New Delhi   to   CNB/Kanpur Central   |   440 km / 1307 km
12826/Jharkhand Sampark Kranti Express
Entry# 2259310

Posted by: amitramsharma   744 blog posts   3982 correct pred (71% accurate)
PNR: 271-xxxxxxx   |   Similar PNRs
Posted Status as of: May 02 2017 (11:50)
Passenger 1: Waitlist# 3 (Booking Status: W/L 4,PQWL)
Total Fare:  1045
Chart NOT Prepared
Please analyze this PNR, and predict the final Charting Status. Thanks.

Latest Status as of: May 02 2017 (23:11)
Passenger 1: A1,8 [UB] (Booking Status: W/L 4,PQWL)
Total Fare:  1045

Full PNR Status History (2 statuses)
Status as of: May 02 2017 (23:11)
Passenger 1: A1,8 [UB] (Booking Status: W/L 4,PQWL)
Total Fare:  1045

Status as of: May 02 2017 (11:50)
Passenger 1: Waitlist# 3 (Booking Status: W/L 4,PQWL)
Total Fare:  1045
Chart NOT Prepared

May 02 2017 (22:28)
amitramsharma   744 blog posts   3982 correct pred (71% accurate)
Re# 2259310-1            Tags   Past Edits
When chart will prepare

May 02 2017 (23:24)
Mr Ocean   154 blog posts   1637 correct pred (69% accurate)
Re# 2259310-2            Tags   Past Edits
Happy Journey.
★★  Travelogue
Apr 13 2017 (02:14)   12825/Jharkhand Sampark Kranti Express | NDLS/New Delhi (16 PFs)

DhnEcr~   5358 blog posts
Entry# 2233030            Tags   Past Edits
My First trip to Delhi May 2009
I needed to take admission in Dehradun college and had to come to Gurgaon campus for Direct interview/Admission. We decided to go unreserved like the millions of migrants from WB,UP, Bihar etc, but the only difference I chose a train with that ensured the most comfortable ride aka 12825 RNC-NDLS Sampark Kranti SF. With my brother as co-passenger who already had a wretched ride in 12817 but that later.
So in month of May, my jouney started off from KMME at 11 pm at night. There
had been heavy rains that day, trains from HWH were running late, high speed winds had uprooted couple of trees so we walked to KKME barely a 1 km from my home. I requested for ticket to NDLS and booking clerk told me "Beta Kalka Mail goes to Old Delhi not NDLS". I told him I knew it but I wanted ticket to NDLS and explained I am not using Kalka Mail. He gave me a ticket Rs 195 (damn cheap)
We had to reach GMO to catch 12825. As per the plan we were to catch ASN-DHN pgr and 13009 Doon for DHN-GMO. Instead we had honors of 12339 HWH-DHN Coalfield SF which ran as passenger as local Memu was cancelled. Damn it with Kalka mail chasing it we feared it would ot us but it didnt. Instead we had to wait for 30 mins for it to arrive at DHN. When it finally moved in at DHN pf 3 its general was as usual jam packed and somehow we squeezed at Gate only praying that the 30 min. journey DHN-GMO ends quickly. It felt as eternity though but we reached at 1.30 am at GMO. The train was expected at 3.10 am but was announced late. No regular trains crossed as Doon and Mumbai mail were late. Around 4.15 12307 HWH-JU SF crossed us.
At 4.55 am our train was announced, it rushed in and without caring to check all coaches we boarded the First SLR coach. Surprisingly all its single seats were empty, (imagining what I had just seen in Kalka Mail) Good Gracious.
RNC SK dpearted at 5.05 am with morning slowly lighting up the sky. The Red engine then (WAP-4 now) honked madly as it raced ahead skipped PNME halted at HZD and KQR but Skipped Gaya. My bro told me how his train 12817 had been ransacked by Unreserved passengers at Gaya. Meanwhile I thanked my stars that my train chose to skip it. Despite late by 2 hours it slammed GMO-MGS in 5 hours flat. We covered 1 hour delay as we moved in at pf 4 at MGS while 12307 had gone ahead. (Just few months back in January I had my longest ride in 13009 HWH DDN Don express which had taken full 10 hours for DHN-MGS). My brother got down at MGS bought some water and snacks and asked me to shift to 2 coaches behind. I was like "Are u kidding me". Why shift when we have a side seat already. He said Trust me u wont regret it. As an true General guy I left my seat, keeping some paper on seat to still claim it back but bro told me none can now board this train from MGS as it is Jharkhand SK while we are in UP. When I reached 3rd coach I was most amazed to see an entire long berth section empty. So we slept on long berth (cushioned) and had a sleeping journey better than any Sleeper train ever I had amazed at this awesome train.
We departed MGS post a 30 min halt. We OT 12307 at Chunar (WOW SF ot SF). Then I had a long sleep, crossed ALD in afternoon (only remember the Yamuna crossing). It was terribly hot and train too moved quickly. We covered MGS-CNB in 5 hours to reach CNB at 3.35pm pf 1. There was a water riot on station literally with passengers fighting for every drop. Some NGO or station ppl had arranged additional containers to provide water. Our train departed after a 15 min halt and quickly flew through the fastest section storming through Phaphund, Etawah and station with suffix bad. (Firozabad and Shikohabad). I enjoyed the evening at and at 7pm had a halt at Tundla jn on leftmost pf. I wondered how so much daylight at 7pm while it gets pitch dark at my area.
Then I hard a loud engine noise and grand Wap-7 moved in with 12003 LKO Swarna Shatabdi with LHB (at that time it did not halt there though).
Post TDL started the crossing of mighty Rajdhani gang back to back while I counted 4 that crossed one after the other. The train kept on slowing down as we approached ALJN. My bro told me when you smell a terrible unbearable odour you know its ALJN. Soon the odour came and so did the station. While it stopped in outer it skipped the station at 8.45pm.
From ALJN began real crawling where train would run, halt run. Close to CYZ it was so congested that I could see train ahead rear light and engine light behind. We again skipped GZB stn with me wondering it halts at outer, why not stop at station silly train. It took full 3 hours for ALJN-NDLS. As we corssed bridges and underpass ROads of Delhi I was just Dazzled with the amount of Cars on Delhi Roads of out glorious Capital. We reached NDLS at 11.45 pm, unfourtunately missed the last metro by 15 minutes (the only sad part of my journey). My brother mobile phone hanged up and it took another 15 minutes to get it up. We called our local cousin who came with bike and we had a tripling ride to Uttamnagar below the Metro pillars carefully avoiding the traffic cops. We had a late dinner and slept off.
Thanks for Reading.!!! Do share your first metropolitan city ride

Apr 14 2017 (23:47)
12817 Jharkhand Swarna Jayanti 12818~   1493 blog posts   47 correct pred (72% accurate)
Re# 2233030-1            Tags   Past Edits
Bahut badhiya...

Apr 14 2017 (23:53)
High Time for LKOCNB section~   2345 blog posts
Re# 2233030-2            Tags   Past Edits
Great one..loved the OT with 12307 and LKO swrna Shtabdi part..😁
Page#    281 blog entries  next>>

Scroll to Top
Scroll to Bottom

Go to Desktop site
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.