Disclaimer   
Forum Super Search
 ♦ 
×
HashTag:
Member:
Posting Date From:
Posting Date To:
Train Type:
Train:
Station:
ONLY with Pic/Vid:
Sort by: Date:     Word Count:     Popularity:     
Public:    Pvt: Monitor:    RailFan Club:    

Search
  Go  
Full Site Search
  Search  
 
Thu Jan 19, 2017 14:26:23 ISTHomeTrainsΣChainsAtlasPNRForumGalleryNewsFAQTripsLoginFeedback
Thu Jan 19, 2017 14:26:23 IST

Blog Entry# 1938718  
Posted: Jul 23 2016 (11:17)

No Responses Yet
  
Predictions: 11
confirm: 11
rac: 0
wl: 0
Journey: Mon Aug 08, 2016 @ 11:37
Class: Sleeper - SL   |   Tot Seats: Avbl >82
Travel: VZM/Vizianagaram Junction   to   TPTY/Tirupati Main   |   798 km / 1921 km
12867/Howrah - Puducherry (Aurobindo) SF Express (PT)
Entry# 1938718

Posted by: sktravelsvzm   1 blog posts   226 correct pred (66% accurate)
PNR: 675-xxxxxxx (E-Ticket)   |   Similar PNRs
Posted Status as of: Jul 23 2016 (11:17)
Passenger 1: RAC 66 (Booking Status: RAC 67,GNWL)
Passenger 2: RAC 67 (Booking Status: RAC 68,GNWL)
Passenger 3: RAC 68 (Booking Status: RAC 69,GNWL)
Passenger 4: RAC 69 (Booking Status: RAC 70,GNWL)
Passenger 5: RAC 70 (Booking Status: RAC 71,GNWL)
Passenger 6: RAC 71 (Booking Status: RAC 72,GNWL)
Total Fare:  3465
Chart NOT Prepared
Please analyze this PNR, and predict the final Charting Status. Thanks.

Latest Status as of: Aug 07 2016 (18:38)
Passenger 1: S5,18 [MB] (Booking Status: RAC 67,GNWL)
Passenger 2: S5,19 [UB] (Booking Status: RAC 68,GNWL)
Passenger 3: S5,42 [MB] (Booking Status: RAC 69,GNWL)
Passenger 4: S5,43 [UB] (Booking Status: RAC 70,GNWL)
Passenger 5: S5,45 [MB] (Booking Status: RAC 71,GNWL)
Passenger 6: S5,48 [SU] (Booking Status: RAC 72,GNWL)
Total Fare:  3465
Chart PREPARED

Full PNR Status History (8 statuses)
Status as of: Aug 07 2016 (18:38)
Passenger 1: S5,18 [MB] (Booking Status: RAC 67,GNWL)
Passenger 2: S5,19 [UB] (Booking Status: RAC 68,GNWL)
Passenger 3: S5,42 [MB] (Booking Status: RAC 69,GNWL)
Passenger 4: S5,43 [UB] (Booking Status: RAC 70,GNWL)
Passenger 5: S5,45 [MB] (Booking Status: RAC 71,GNWL)
Passenger 6: S5,48 [SU] (Booking Status: RAC 72,GNWL)
Total Fare:  3465
Chart PREPARED

Status as of: Aug 07 2016 (13:51)
Passenger 1: RAC 39 (Booking Status: RAC 67,GNWL)
Passenger 2: RAC 40 (Booking Status: RAC 68,GNWL)
Passenger 3: RAC 41 (Booking Status: RAC 69,GNWL)
Passenger 4: RAC 42 (Booking Status: RAC 70,GNWL)
Passenger 5: RAC 43 (Booking Status: RAC 71,GNWL)
Passenger 6: RAC 44 (Booking Status: RAC 72,GNWL)
Total Fare:  3465
Chart NOT Prepared

Status as of: Aug 05 2016 (22:59)
Passenger 1: RAC 43 (Booking Status: RAC 67,GNWL)
Passenger 2: RAC 44 (Booking Status: RAC 68,GNWL)
Passenger 3: RAC 45 (Booking Status: RAC 69,GNWL)
Passenger 4: RAC 46 (Booking Status: RAC 70,GNWL)
Passenger 5: RAC 47 (Booking Status: RAC 71,GNWL)
Passenger 6: RAC 48 (Booking Status: RAC 72,GNWL)
Total Fare:  3465
Chart NOT Prepared

Status as of: Aug 01 2016 (13:12)
Passenger 1: RAC 52 (Booking Status: RAC 67,GNWL)
Passenger 2: RAC 53 (Booking Status: RAC 68,GNWL)
Passenger 3: RAC 54 (Booking Status: RAC 69,GNWL)
Passenger 4: RAC 55 (Booking Status: RAC 70,GNWL)
Passenger 5: RAC 56 (Booking Status: RAC 71,GNWL)
Passenger 6: RAC 57 (Booking Status: RAC 72,GNWL)
Total Fare:  3465
Chart NOT Prepared

Status as of: Jul 31 2016 (18:56)
Passenger 1: RAC 56 (Booking Status: RAC 67,GNWL)
Passenger 2: RAC 57 (Booking Status: RAC 68,GNWL)
Passenger 3: RAC 58 (Booking Status: RAC 69,GNWL)
Passenger 4: RAC 59 (Booking Status: RAC 70,GNWL)
Passenger 5: RAC 60 (Booking Status: RAC 71,GNWL)
Passenger 6: RAC 61 (Booking Status: RAC 72,GNWL)
Total Fare:  3465
Chart NOT Prepared

Status as of: Jul 30 2016 (19:16)
Passenger 1: RAC 57 (Booking Status: RAC 67,GNWL)
Passenger 2: RAC 58 (Booking Status: RAC 68,GNWL)
Passenger 3: RAC 59 (Booking Status: RAC 69,GNWL)
Passenger 4: RAC 60 (Booking Status: RAC 70,GNWL)
Passenger 5: RAC 61 (Booking Status: RAC 71,GNWL)
Passenger 6: RAC 62 (Booking Status: RAC 72,GNWL)
Total Fare:  3465
Chart NOT Prepared

Status as of: Jul 27 2016 (11:52)
Passenger 1: RAC 59 (Booking Status: RAC 67,GNWL)
Passenger 2: RAC 60 (Booking Status: RAC 68,GNWL)
Passenger 3: RAC 61 (Booking Status: RAC 69,GNWL)
Passenger 4: RAC 62 (Booking Status: RAC 70,GNWL)
Passenger 5: RAC 63 (Booking Status: RAC 71,GNWL)
Passenger 6: RAC 64 (Booking Status: RAC 72,GNWL)
Total Fare:  3465
Chart NOT Prepared

Status as of: Jul 23 2016 (11:17)
Passenger 1: RAC 66 (Booking Status: RAC 67,GNWL)
Passenger 2: RAC 67 (Booking Status: RAC 68,GNWL)
Passenger 3: RAC 68 (Booking Status: RAC 69,GNWL)
Passenger 4: RAC 69 (Booking Status: RAC 70,GNWL)
Passenger 5: RAC 70 (Booking Status: RAC 71,GNWL)
Passenger 6: RAC 71 (Booking Status: RAC 72,GNWL)
Total Fare:  3465
Chart NOT Prepared

ARP (Advanced Reservation Period) Calculator

Reservations Open Today @ 8am for:
Trains with ARP 10 Dep on: Sun Jan 29
Trains with ARP 15 Dep on: Fri Feb 3
Trains with ARP 30 Dep on: Sat Feb 18
Trains with ARP 120 Dep on: Fri May 19

  
  

Rail News

New Trains

Site Announcements

  • Entry# 2126247
    Jan 13 (11:57PM)


    Here are some guidelines for members regarding the new Report button and the revamped FM system: 1. If you have ANY complaint about a blog or ANY other issues, please USE the Report button and file a Complaint. Most complaints are resolved by FMs within seconds/minutes. (Some require further discussion). FMs have...
  • Entry# 2125399
    Jan 13 (08:58AM)


    Often we have some TL Entries seemingly in WaitList forever. Usually, the reason for this is that TLMs have already looked at the TL Entry but are not confident enough to Confirm it or are looking for more inputs from the Member regarding the source, etc. And this delay eventually causes...
  • Entry# 2122843
    Jan 10 (10:15PM)


    This is to address persistent and lingering questions about FM Appointments: . 1. Being an FM is a service. It is NOT supposed to be some kind of "reward" or "medal" to "deserving" members. The ULTIMATE OBJECTIVE of the process is to promptly handle/look into Reports filed by members, which is expected to...
  • Entry# 2115377
    Jan 04 (12:30AM)


    There are some changes to the Forum section. . The Objection feature is now completely GONE. We now only have a "Report Abuse" button. When the Report button is used, an alert is sent to the "Forum Monitor" group. ALL FMs will see an "FM Alert" notification at the top. Thereafter, they will...
  • Entry# 2095722
    Dec 18 2016 (11:34PM)


    Very soon, we shall have a points-system for Timeline updates, Atlas updates, News updates, Blog Tagging, News Tagging, Blog Tagging, etc. The reason for this is that some kinds of updates require more hard work and are more useful than others. Up-to-date News about late-running trains, updating TTs of trains only...
  • Entry# 2034010
    Oct 24 2016 (12:18AM)


    This is to address queries in the Forum about our various Groups - Admin, TL Monitor, FAQ Monitor, etc. . We are not appointing Admins anymore. Before Monitors, we had just one group called the Admin group. Now, we have the various Monitor groups. Our Admins themselves are members of the various Monitor...
Scroll to Top
Scroll to Bottom


Go to Mobile site