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  
 
Wed Mar 29, 2017 03:19:57 ISTHomeTrainsΣChainsAtlasPNRForumGalleryNewsFAQTripsLoginFeedback
Wed Mar 29, 2017 03:19:57 IST
PostPostPost Trn TipPost Trn TipPost Stn TipPost Stn TipAdvanced Search
Filters:

Blog Posts by Kartheeswaran
Page#    294 Blog Entries  next>>
  
Predictions: 14
confirm: 9
rac: 5
wl: 0
Journey: Tue Jun 14, 2016 @ 18:15
Class: Sleeper - SL   |   Tot Seats: Avbl 300
Travel: PLNI/Palani   to   MAS/Chennai Central   |   552 km / 552 km
22652/Palani - Chennai Central SF Express
Entry# 1893310

Posted by: Kartheeswaran   469 blog posts   1416 correct pred (75% accurate)
PNR: 463-xxxxxxx (E-Ticket)   |   Similar PNRs
Posted Status as of: Jun 13 2016 (18:45)
Passenger 1: RAC 88 (Booking Status: W/L 59,GNWL)
Passenger 2: RAC 89 (Booking Status: W/L 60,GNWL)
Total Fare:  690
Chart NOT Prepared
Please analyze this PNR, and predict the final Charting Status. Thanks.

Latest Status as of: Jun 14 2016 (22:02)
Passenger 1: RS9 39 (Booking Status: W/L 59,GNWL)
Passenger 2: RS9 39 (Booking Status: W/L 60,GNWL)
Total Fare:  690
Chart PREPARED

Full PNR Status History (10 statuses)
Status as of: Jun 14 2016 (14:10)
Passenger 1: RS9 39 (Booking Status: W/L 59,GNWL)
Passenger 2: RS9 39 (Booking Status: W/L 60,GNWL)
Total Fare:  690
Chart PREPARED

Status as of: Jun 14 2016 (14:07)
Passenger 1:  (Booking Status: W/L 59,GNWL)
Passenger 2:  (Booking Status: W/L 60,GNWL)
Total Fare:  690
Chart NOT Prepared

Status as of: Jun 14 2016 (14:01)
Passenger 1: RAC 73 (Booking Status: W/L 59,GNWL)
Passenger 2: RAC 74 (Booking Status: W/L 60,GNWL)
Total Fare:  690
Chart NOT Prepared

Status as of: Jun 14 2016 (13:43)
Passenger 1: RAC 75 (Booking Status: W/L 59,GNWL)
Passenger 2: RAC 76 (Booking Status: W/L 60,GNWL)
Total Fare:  690
Chart NOT Prepared

Status as of: Jun 14 2016 (13:33)
Passenger 1: RAC 76 (Booking Status: W/L 59,GNWL)
Passenger 2: RAC 77 (Booking Status: W/L 60,GNWL)
Total Fare:  690
Chart NOT Prepared

Status as of: Jun 14 2016 (13:08)
Passenger 1: RAC 78 (Booking Status: W/L 59,GNWL)
Passenger 2: RAC 79 (Booking Status: W/L 60,GNWL)
Total Fare:  690
Chart NOT Prepared

Status as of: Jun 14 2016 (12:12)
Passenger 1: RAC 79 (Booking Status: W/L 59,GNWL)
Passenger 2: RAC 80 (Booking Status: W/L 60,GNWL)
Total Fare:  690
Chart NOT Prepared

Status as of: Jun 14 2016 (10:03)
Passenger 1: RAC 83 (Booking Status: W/L 59,GNWL)
Passenger 2: RAC 84 (Booking Status: W/L 60,GNWL)
Total Fare:  690
Chart NOT Prepared

Status as of: Jun 13 2016 (22:20)
Passenger 1: RAC 85 (Booking Status: W/L 59,GNWL)
Passenger 2: RAC 86 (Booking Status: W/L 60,GNWL)
Total Fare:  690
Chart NOT Prepared

Status as of: Jun 13 2016 (18:45)
Passenger 1: RAC 88 (Booking Status: W/L 59,GNWL)
Passenger 2: RAC 89 (Booking Status: W/L 60,GNWL)
Total Fare:  690
Chart NOT Prepared


  
4028 views
Jun 13 2016 (21:18)
Its me   779 blog posts   40605 correct pred (79% accurate)
Re# 1893310-1            Tags   Past Edits
CK - 46 Available as of now.
  
Predictions: 10
confirm: 10
rac: 0
wl: 0
Journey: Mon May 23, 2016 @ 22:10
Class: Sleeper - SL   |   Tot Seats: Avbl 218
Travel: SBC/KSR Bengaluru City Junction (Bangalore)   to   TUP/Tiruppur   |   328 km / 1513 km
11013/Mumbai LTT - Coimbatore (Kurla) Express (PT)
Entry# 1857979

Posted by: Kartheeswaran   469 blog posts   1416 correct pred (75% accurate)
PNR: 853-xxxxxxx    |   Similar PNRs
Posted Status as of: May 21 2016 (19:24)
Passenger 1: Waitlist# 3 (Booking Status: W/L 3,CK)
Total Fare:  385
Chart NOT Prepared
Please analyze this PNR, and predict the final Charting Status. Thanks.

Latest Status as of: May 23 2016 (17:55)
Passenger 1: S7,3 [UB]/Coach Position:15 (Booking Status: W/L 3,CK)
Total Fare:  385
Chart PREPARED

Full PNR Status History (3 statuses)
Status as of: May 23 2016 (17:55)
Passenger 1: S7,3 [UB]/Coach Position:15 (Booking Status: W/L 3,CK)
Total Fare:  385
Chart PREPARED

Status as of: May 23 2016 (07:47)
Passenger 1: Waitlist# 2 (Booking Status: W/L 3,CK)
Total Fare:  385
Chart NOT Prepared

Status as of: May 21 2016 (19:29)
Passenger 1: Waitlist# 3 (Booking Status: W/L 3,CK)
Total Fare:  385
Chart NOT Prepared


  
3399 views
May 23 2016 (14:49)
Its me   779 blog posts   40605 correct pred (79% accurate)
Re# 1857979-1            Tags   Past Edits
PT 21 Available.
  
General Travel
1 Followers
2360 views
May 21 2016 (21:21)  
 

Kartheeswaran   469 blog posts   1416 correct pred (75% accurate)
Entry# 1858126            Tags   Past Edits
//Do you Know why IRCTC does not allow you to choose seats? Would you believe that the technical reason behind this is PHYSICS.
Booking a seat in a train is far more different than booking a seat in a theatre.
Theatre is a hall, whereas train is a moving object. So safety concern is very high in trains.
Indian railways ticket booking
...
more...
software is designed in such a way that it will book tickets in a manner that will distribute the load evenly in a train.
Let me take an example to make things more clear : Imagine there are sleeper class coaches in a train numbered S1, S2 S3... S10, and in every coach there are 72 seats.
So when some one first books a ticket, software will assign a seat in the middle coach like S5, middle seat numbered between 30-40, and preferably lower berths (Railways first fills the lower berths than upper one so as to achieve low centre of gravity.)
And the software books seats in such a way that all coaches have uniform passenger distribution and seats are filled starting from the middle seats (36) to seats near the gates i.e 1-2 or 71-72 in order from lower berth to upper.
Railways just want to ensure a proper balance that each coach should have for equal load distribution.
That is why when you book a ticket at the last, you are always allotted an upper berth and a seat numbered around 2-3 or 70, except when you are not taking a seat of someone who has cancelled his/her seat.
What if the railways book tickets randomly ? A train is a moving object which moves around at a speed of around 100km/hr on rails.
So there are a lot of forces and mechanics acting on the train.
Just imagine if S1, S2, S3 are completely full and S5, S6 are completely empty and others are partially full. When the train takes a turn, some coaches face maximum centrifugal force and some minimum, and this creates a high chance of derailment of the train.
This is a very technical aspect, and when brakes are applied there will be different braking forces acting at each of the coaches because of the huge differences in weight of coach, so stability of train becomes an issue again.
I felt that this is a good information worth sharing, as often passengers blame the Railways citing inconvenient seats/ berths allotted to them.//
I have received this info in whatsapp...
Is this info true?

  
May 22 2016 (00:46)
Pran Pratim Ghosh   20255 blog posts   94868 correct pred (75% accurate)
Re# 1858126-1            Tags   Past Edits
totally incorrect.

  
907 views
May 22 2016 (01:05)
suyashchandra26~   829 blog posts   455 correct pred (64% accurate)
Re# 1858126-2            Tags   Past Edits
I disagree
if center of gravity is the reason then general coaches should be in the middle of train not at both the ends becoz general coaches has maximum crowd hence maximum load is present on general coach
but in real life the general coach at the both ends have maximum load & if we go according to center of gravity then there is no equal load distribution but even after that no train derails

  
1008 views
May 22 2016 (01:14)
Vinay Kumar~   15557 blog posts   361 correct pred (78% accurate)
Re# 1858126-3            Tags   Past Edits
Garib Rath/Rajdhani/Shatabdi/DRNTO: These mostly do booking Coach wise & in lean period or not so in demand version, u may find many coaches full empty & closed!!
A Coach weight by any mean isnt related with the negligible weight of passengers, even if its full till toilet!! Ur funda gets void, as in such case, Freight would never been running empty!! & many times u gonna find steel mesh freight with few fully loaded while first few or mid few or last few or zig-zag remain empty!!

3 posts are hidden.

  
888 views
May 22 2016 (06:48)
Kartheeswaran   469 blog posts   1416 correct pred (75% accurate)
Re# 1858126-7            Tags   Past Edits
Thanks to everyone who clarified about this info...

5 posts are hidden.
  
Info Update
1 Followers
5794 views
Dec 28 2015 (11:07)   22607/Ernakulam - KSR Bengaluru Weekly SF Express (PT) | AWY/Aluva (Alwaye) (3 PFs)

Kartheeswaran   469 blog posts   1416 correct pred (75% accurate)
Entry# 1693893            Tags   Past Edits
Dear Admins,
Pls update the coach position as below,
LOCO-SLR-GEN-S14-S13-S12-S11-S10-S9-S8-S7-S6-S5-S4-S3-PC-S2-S1-B1-B2-A1-GEN-SLRD
Source: traveled my self yesterday from AWY to TUP

  
5715 views
Dec 28 2015 (13:21)
krishnameledom   18 blog posts   1 correct pred (50% accurate)
Re# 1693893-1            Tags   Past Edits
There is a correction. It is Loco SLR GEN S1- S12 PC S13 S14 B1 B2 A1
I travelled yesterday from PGT to SBC.
  
General Travel
0 Followers
2581 views
Dec 28 2015 (10:23)  

contactvetri   36 blog posts
Entry# 1693855            Tags   Past Edits
Hi Experts can we do Change in Boarding Point online or it has to be done only in stations

5 posts are hidden.

  
1189 views
Dec 28 2015 (11:10)
Kartheeswaran   469 blog posts   1416 correct pred (75% accurate)
Re# 1693855-6            Tags   Past Edits
You can approach any nearest PRS counter, the boarding point can be changed minimum 24 Hrs before from originating station (not boarding station) & the boarding point change is possible only for confirmed tickets, WL and RAC cannot be changed.

2 posts are hidden.
  
Predictions: 17
confirm: 17
rac: 0
wl: 0
Journey: Sun Dec 27, 2015 @ 17:24
Class: AC 3-tier - 3A
Travel: AWY/Aluva (Alwaye)   to   TUP/Tiruppur   |   223 km / 618 km
22607/Ernakulam - KSR Bengaluru Weekly SF Express (PT)
Entry# 1673298

Posted by: Kartheeswaran   469 blog posts   1416 correct pred (75% accurate)
PNR: 411-xxxxxxx (E-Ticket)   |   Similar PNRs
Posted Status as of: Dec 07 2015 (15:42)
Passenger 1: Confirmed (Booking Status: B1,63,PQ)
Passenger 2: Waitlist# 22 (Booking Status: W/L 27,PQWL)
Passenger 3: Waitlist# 23 (Booking Status: W/L 28,PQWL)
Passenger 4: Waitlist# 24 (Booking Status: W/L 29,PQWL)
Passenger 5: Waitlist# 25 (Booking Status: W/L 30,PQWL)
Passenger 6: Waitlist# 26 (Booking Status: W/L 31,PQWL)
Chart NOT Prepared

Please analyze this PNR, and predict the final Charting Status. Thanks.

Latest Status as of: Dec 27 2015 (17:08)
Passenger 1: B1,63 [SL]/Coach Position:19 (Booking Status: B1,63,PQ)
Passenger 2: Can/Mod (Booking Status: W/L 27,PQWL)
Passenger 3: Can/Mod (Booking Status: W/L 28,PQWL)
Passenger 4: B1,12 [LB]/Coach Position:19 (Booking Status: W/L 29,PQWL)
Passenger 5: Can/Mod (Booking Status: W/L 30,PQWL)
Passenger 6: Can/Mod (Booking Status: W/L 31,PQWL)
Chart PREPARED

Full PNR Status History (7 statuses)
Status as of: Dec 27 2015 (12:54)
Passenger 1: B1,63 [SL]/Coach Position:19 (Booking Status: B1,63,PQ)
Passenger 2: Can/Mod (Booking Status: W/L 27,PQWL)
Passenger 3: Can/Mod (Booking Status: W/L 28,PQWL)
Passenger 4: B1,12 [LB]/Coach Position:19 (Booking Status: W/L 29,PQWL)
Passenger 5: Can/Mod (Booking Status: W/L 30,PQWL)
Passenger 6: Can/Mod (Booking Status: W/L 31,PQWL)
Chart PREPARED

Status as of: Dec 26 2015 (17:34)
Passenger 1: Confirmed (Booking Status: B1,63,PQ)
Passenger 2: Can/Mod (Booking Status: W/L 27,PQWL)
Passenger 3: Can/Mod (Booking Status: W/L 28,PQWL)
Passenger 4: Waitlist# 3 (Booking Status: W/L 29,PQWL)
Passenger 5: Can/Mod (Booking Status: W/L 30,PQWL)
Passenger 6: Can/Mod (Booking Status: W/L 31,PQWL)
Chart NOT Prepared

Status as of: Dec 26 2015 (15:10)
Passenger 1: Confirmed (Booking Status: B1,63,PQ)
Passenger 2: Can/Mod (Booking Status: W/L 27,PQWL)
Passenger 3: Can/Mod (Booking Status: W/L 28,PQWL)
Passenger 4: Waitlist# 4 (Booking Status: W/L 29,PQWL)
Passenger 5: Can/Mod (Booking Status: W/L 30,PQWL)
Passenger 6: Can/Mod (Booking Status: W/L 31,PQWL)
Chart NOT Prepared

Status as of: Dec 26 2015 (09:41)
Passenger 1: Confirmed (Booking Status: B1,63,PQ)
Passenger 2: Can/Mod (Booking Status: W/L 27,PQWL)
Passenger 3: Can/Mod (Booking Status: W/L 28,PQWL)
Passenger 4: Waitlist# 6 (Booking Status: W/L 29,PQWL)
Passenger 5: Can/Mod (Booking Status: W/L 30,PQWL)
Passenger 6: Can/Mod (Booking Status: W/L 31,PQWL)
Chart NOT Prepared

Status as of: Dec 24 2015 (10:03)
Passenger 1: Confirmed (Booking Status: B1,63,PQ)
Passenger 2: Can/Mod (Booking Status: W/L 27,PQWL)
Passenger 3: Can/Mod (Booking Status: W/L 28,PQWL)
Passenger 4: Waitlist# 7 (Booking Status: W/L 29,PQWL)
Passenger 5: Can/Mod (Booking Status: W/L 30,PQWL)
Passenger 6: Can/Mod (Booking Status: W/L 31,PQWL)
Chart NOT Prepared

Status as of: Dec 23 2015 (13:59)
Passenger 1: Confirmed (Booking Status: B1,63,PQ)
Passenger 2: Can/Mod (Booking Status: W/L 27,PQWL)
Passenger 3: Can/Mod (Booking Status: W/L 28,PQWL)
Passenger 4: Waitlist# 8 (Booking Status: W/L 29,PQWL)
Passenger 5: Can/Mod (Booking Status: W/L 30,PQWL)
Passenger 6: Can/Mod (Booking Status: W/L 31,PQWL)
Chart NOT Prepared

Status as of: Dec 23 2015 (01:53)
Passenger 1: Confirmed (Booking Status: B1,63,PQ)
Passenger 2: Can/Mod (Booking Status: W/L 27,PQWL)
Passenger 3: Can/Mod (Booking Status: W/L 28,PQWL)
Passenger 4: Waitlist# 9 (Booking Status: W/L 29,PQWL)
Passenger 5: Can/Mod (Booking Status: W/L 30,PQWL)
Passenger 6: Can/Mod (Booking Status: W/L 31,PQWL)
Chart NOT Prepared


  
2620 views
Dec 08 2015 (11:08)
Kartheeswaran   469 blog posts   1416 correct pred (75% accurate)
Re# 1673298-1            Tags   Past Edits
Passenger no1 - Confirmed, Passenger no 2,3, 4, 5& 6 should be WL1 to 5, but here WL is starting from 22 to 26. How is this possible? It looks strange to me!
Seniors, pls help to understand about this. thanks

  
2628 views
Dec 27 2015 (12:26)
CrUeL InTeNtIoNs*^~   4312 blog posts   44800 correct pred (92% accurate)
Re# 1673298-2            Tags   Past Edits
first passenger has been confirmed by virtue of berth multiplexing
  
Predictions: 5
confirm: 5
rac: 0
wl: 0
Journey: Sat Dec 26, 2015 @ 02:25
Class: AC 3-tier - 3A
Travel: TUP/Tiruppur   to   TLY/Thalassery   |   305 km / 660 km
16527/Yesvantpur - Kannur Express (via Salem)
Entry# 1677789

Posted by: Kartheeswaran   469 blog posts   1416 correct pred (75% accurate)
PNR: 452-xxxxxxx (E-Ticket)   |   Similar PNRs
Posted Status as of: Dec 12 2015 (11:05)
Passenger 1: Waitlist# 6 (Booking Status: W/L 6,PQWL)
Passenger 2: Waitlist# 7 (Booking Status: W/L 7,PQWL)
Passenger 3: Waitlist# 8 (Booking Status: W/L 8,PQWL)
Chart NOT Prepared

Please analyze this PNR, and predict the final Charting Status. Thanks.

Latest Status as of: Dec 26 2015 (23:02)
Passenger 1: Waitlist# 2 (Booking Status: W/L 6,PQWL)
Passenger 2: Waitlist# 3 (Booking Status: W/L 7,PQWL)
Passenger 3: Waitlist# 4 (Booking Status: W/L 8,PQWL)
Chart PREPARED

Full PNR Status History (2 statuses)
Status as of: Dec 25 2015 (15:54)
Passenger 1: Waitlist# 2 (Booking Status: W/L 6,PQWL)
Passenger 2: Waitlist# 3 (Booking Status: W/L 7,PQWL)
Passenger 3: Waitlist# 4 (Booking Status: W/L 8,PQWL)
Chart PREPARED

Status as of: Dec 23 2015 (01:53)
Passenger 1: Waitlist# 2 (Booking Status: W/L 6,PQWL)
Passenger 2: Waitlist# 3 (Booking Status: W/L 7,PQWL)
Passenger 3: Waitlist# 4 (Booking Status: W/L 8,PQWL)
Chart NOT Prepared


  
1296 views
Dec 19 2015 (15:06)
Kartheeswaran   469 blog posts   1416 correct pred (75% accurate)
Re# 1677789-1            Tags   Past Edits
Not even a single no come down after 7 days! Will this get confirmed?

  
1216 views
Dec 25 2015 (13:45)
Kartheeswaran   469 blog posts   1416 correct pred (75% accurate)
Re# 1677789-2            Tags   Past Edits
Will this get confirmed? Feeling nervous as we need to be there in the morning!!! Experts pls advise. thanks
TRIP HAS ENDED.
Blog  Time-Table

  
4687 views
Dec 14 2015 (16:03)
Kartheeswaran   469 blog posts   1416 correct pred (75% accurate)
Re# 1677793-1            Tags   Past Edits
Will this get confirmed? Expert pls advise
  
Travel Question
1 Followers
5287 views
Dec 08 2015 (20:11)   22607/Ernakulam - KSR Bengaluru Weekly SF Express (PT) | AWY/Aluva (Alwaye) (3 PFs)
 

Kartheeswaran   469 blog posts   1416 correct pred (75% accurate)
Entry# 1674573            Tags   Past Edits
I have booked a ticket,
Passenger no1 - Confirmed, Passenger no 2,3, 4, 5& 6 should be PQWL1 to 5, but here PQWL is starting from 22 to 26. How is this possible? It looks strange to me!
Seniors, pls help to understand about this. thanks

1 posts - Tue Dec 08, 2015

  
4632 views
Dec 08 2015 (20:16)
sys tem~   8202 blog posts   75434 correct pred (76% accurate)
Re# 1674573-2            Tags   Past Edits
quota is pooled between different stations so this is the case ...
.
source -> dest1 , dest 2 ( say WL quota is PQWL) ...also dest1-> dest2 is PQWL ...
.
now source to
...
more...
dest 2 is already PQWL ..say PQWL 20 . while a single seat is avbl between source -> dest1..so you get one confirmed seat while WL tkt starts from PQWL 21,22...and not 1 , 2 ..

  
4464 views
Dec 08 2015 (20:28)
Kartheeswaran   469 blog posts   1416 correct pred (75% accurate)
Re# 1674573-3            Tags   Past Edits
Non of them are senior citizens

  
4502 views
Dec 08 2015 (20:31)
Guest: 45b6b761   show all posts
Re# 1674573-4            Tags   Past Edits
Female passanger??

  
4588 views
Dec 08 2015 (20:39)
आम्ही कधीच नाही होणार म्हातारे~   2834 blog posts   1236 correct pred (71% accurate)
Re# 1674573-5            Tags   Past Edits
PQ tickets are not cleared numerically, rather they are cleared station wise.
For the passenger who is WL 22, his/her ticket will be cleared when the next passenger between alwaye-tirruppur cancels his ticket, not when WL 1-21 gets confirmed.
the waitlist is alloted numerically, but is cleared station to station.

  
4546 views
Dec 08 2015 (21:07)
Kartheeswaran   469 blog posts   1416 correct pred (75% accurate)
Re# 1674573-6            Tags   Past Edits
Thanks for the explanation. Now I can understand the scenario.
  
Predictions: 7
confirm: 7
rac: 0
wl: 0
Journey: Sun Nov 29, 2015 @ 22:10
Class: AC 3-tier - 3A   |   Tot Seats: Avbl 16
Travel: SBC/KSR Bengaluru City Junction (Bangalore)   to   TUP/Tiruppur   |   328 km / 1513 km
11013/Mumbai LTT - Coimbatore (Kurla) Express (PT)
Entry# 1659736

Posted by: Kartheeswaran   469 blog posts   1416 correct pred (75% accurate)
PNR: 864-xxxxxxx (E-Ticket)   |   Similar PNRs
Posted Status as of: Nov 24 2015 (11:20)
Passenger 1: Waitlist# 26 (Booking Status: W/L 28,RLGN)
Chart NOT Prepared

Please analyze this PNR, and predict the final Charting Status. Thanks.

Latest Status as of: Nov 29 2015 (17:37)
Passenger 1: B3,47 [SL]/Coach Position:7 (Booking Status: W/L 28,RLGN)
Chart NOT Prepared

  
1573 views
Nov 26 2015 (13:10)
Kartheeswaran   469 blog posts   1416 correct pred (75% accurate)
Re# 1659736-1            Tags   Past Edits
will this get confirmed?

  
1579 views
Nov 28 2015 (18:49)
sys tem~   8202 blog posts   75434 correct pred (76% accurate)
Re# 1659736-2            Tags   Past Edits
yes...this should be a sure shot confirm ..just wait for a while till the chart prepares from LTT and this should confirm ..
Page#    294 Blog Entries  next>>

ARP (Advanced Reservation Period) Calculator

Reservations Open Today @ 8am for:
Trains with ARP 10 Dep on: Sat Apr 8
Trains with ARP 15 Dep on: Thu Apr 13
Trains with ARP 30 Dep on: Fri Apr 28
Trains with ARP 120 Dep on: Thu Jul 27

  
  

Rail News

New Trains

Site Announcements

  • Entry# 2175399
    Feb 23 2017 (01:22PM)


    There has recently been a lot of frustration among RFs when their Station Pics, Loco Pics, Train Pics get rejected because the "number is not showing", "shed is not visible", the loco/train is at a distance, Train Board is too small, "better pic available", etc. . To address this issue, effective tomorrow, ALL...
  • Entry# 2165159
    Feb 15 2017 (09:53AM)


    A minor update, but may impact many members: Hereafter, FMs will be able to delete invalid Red Flags on Imaginary trains. Red Flags can be removed by FMs, only against specific complaints filed against the blog. This does not give all members the right to complain against EVERY single red flag they...
  • Entry# 2155798
    Feb 08 2017 (11:40AM)


    -@all members: As of recently, there has been a trend whereby minor name updates of Trains/Stations - whether such and such regional name should be there or not, whether the train should be called "Abc Express" or "Abc Superfast Express", etc. are threatening to take over the majority of Timeline entries. Also,...
  • Entry# 2147631
    Feb 01 2017 (11:05AM)


    A new experimental feature is being introduced called BotD - "Blog of the Day". The rules are: . 1. Replies are not eligible - only the Top Blog. 2. ONLY Blogs posted today (the day of the vote) are eligible. 3. Every member has ONE vote. In the course of the day, you may keep...
  • Entry# 2136570
    Jan 23 2017 (12:25AM)


    Several new features have been introduced recently to the Forum, and we are forever striving to make Member experience here more productive and satisfying. With the recent introduction and success of the new FM System, it has been observed that small groups of highly involved and enthusiastic members are far more...
  • Entry# 2134907
    Jan 21 2017 (02:46PM)


    It has been over 2 weeks since the appointment of the current batch of FMs and 750 Complaints have been handled so far. It gives me immense pleasure in congratulating them for running the team diligently, professionally, competently and above all, without a shred of controversy or bias. The FM position...
Scroll to Top
Scroll to Bottom


Go to Mobile site