@first blogger:
/train/timetable/7971/401/466

@anon: Mar 18 (02:21PM)
I said from LTT to VSKP not from VSKP to LTT

@anon: Mar 18 (02:31PM)
Please refer Blog # 24685 for complete details of timings and stops. The timetable will also be added shortly for 2750 VSKP-LTT Express.

@Manish: Mar 19 (05:18PM)
2750/LTT Vishakhapatnam Express timetable is now available on the site. /train/7972

@first blogger:
you are correct
@moderator: this is shown in indianrail.gov.in:
Fare Enquiry

You Queried For
Train Number Train Name Date
(DD-MM-YYYY) Source Station Destination Station
0516 NED DD PASNGR 20-3-2010 H SAHIB NANDED DAUND JN
Train Type Distance (kms)
ORDINARY 586

Fare/Charges Class -- Sleeper
Base Fare 132
Reservation Charges 20
Superfast Charges 0
Other Charges 0
Total Amount 152
PLEASE INCLUDE SIR ! good wishes

@Murli: Mar 19 (11:47PM)
@anon:
Fixed. Thanks.

@TUX:
Pls somebody reply to my questions..

@TUX:
Thanks for the compliment - compliments are the fuel this community runs on. As for your question, I have pasted further details from the PNR page, to help our bloggers render advice. If you had posted your comment from the PNR page, the following details would automatically have appeared, and would have helped someone give you a quick reply.
Date of Journey: Sun Mar 21 Class: Sleeper
Passenger 1: Waitlist# 34 (Booking Status: W/L 138, GNWL)

@TUX: Mar 16 (02:35PM)
firstly you have 50-50 chances of getting conf wait till chart prepartion. this train does not have a pantry car you can arrange your food from your home itself or while comming to ndls station you can buy food from resturant near by station

@TUX:
Re food, even though train does not have a Pantry car, it has pantry service. The food is picked up from designated stations and served. Coffee/Tea, biscuits/ breakfast is also made available. Good wishes.

@Murli: Mar 16 (04:42PM)
Date of Journey: Sun Mar 21 Class: Sleeper
Passenger 1: Waitlist# 16 (Booking Status: W/L 138, GNWL)
Chart NOT Prepared
my heartbeat has started beating fast now...will it get confirmed..?

@TUX: Mar 18 (06:59PM)
PNR: 210-3730995
Howrah Express/2324
Date of Journey: Sun Mar 21 Class: Sleeper
Passenger 1: Waitlist# 13 (Booking Status: W/L 138, GNWL)
Chart NOT Prepared
What are the chances..? will i get a confirmed berth?

@TUX: Mar 19 (01:21PM)
RAC is assured.

@Jitesh: Mar 19 (01:22PM)
Thanks Jitesh.. i hope berth mil jaye...

@Jitesh: Mar 19 (01:22PM)
Since there is WL in tatkal quota as well..that means....all tatkal seats are booked..
and rarely people cancel their confirmed tatkal tickets...so only hope is various quota seats...if they doesn't get filled..only then there are chances of a WL ticket to get confirmed.
My present status is
Passenger 1: Waitlist# 11 (Booking Status: W/L 138, GNWL)
Chart NOT Prepared
PNR: 210-3730995/ 2324/Howrah Express.
how many RACs would be there between a confirmed berth and a WL berth?

@TUX: Mar 19 (07:55PM)
You are now 10 on the W/L. Certain for RAC. Good chances for confirmation. Just wait for a day more and check again tomorrow sometime in the afternoon. Check chart status at around 9. p.m. on Saturday 20th. It should have been prepared then since train leaves Sun morning at 0715 from NDLS. good luck and good wishes.

@Kapadia :
In continuation to this suggestion post ....
.... When the reply post is posted, the system will generate sub-entry post # No. and will appear suitably in the reply post, as illustrated above.
The moderator may kindly look into and respond.

@Kapadia : Mar 18 (11:18AM)
As always, thanks for the suggestion and the thought process that went into it. Your concept is formalized in a term called "multi-level threading" or "hierarchical threading", where replies to replies are also tracked independently. Our current model is called "flat threading". Some forums, most notably, slashdot.org uses this format. The reason we did not adopt this hierarchical threading model was the increased complexity of displaying/perusing the forum; we wished to keep this forum quick and casual. Another technical aspect is that we don't want the speed of site to go down, since already the pages are considered "heavy".
We can definitely look at a modified simpler/more customized implementation of your suggestion. We are currently working on some long-pending requests for features. If you permit, we can revisit this topic at a later point in time. Thanks for your patience in the meanwhile.

@moderator: Mar 19 (02:06AM)
You may to some extent call it multi-level-threading but the suggestion is purely in the context of generating sub-etnry post #No. under the main entry post # No. by just extending the main entry # No. with (numbers) in brackets. I shall elaborate more on this suggestion to clear mis-interpretation if any, after few weeks in view of a load of long pending requests with the website team.
However, thanks for your response and views.

@Kapadia : Mar 19 (10:17AM)
@ Moderator :
The running numbers just before the entry post Nos. are misunderstood by the bloggers as the reference number for future purposes. Plz refer post entry # 24612 for this. This aspect was apprrehended by me and poste earlier vide post entry # 20671.
This supports and substantiates my suggestion to have unique id number to be generated at the time the reply post is posted (similar to the new blog post entry post # No.) The suggestion is to extend the same entry post #No. by generating new id No. (to appear in the reply post) (more details as posted in the suggestion) . Simply putting ... Say the original post Entry # 24671. then for each reply post the new id number / sub-entry post number say Entry #24671 (1), Entry #24671(2), Entry #24671(3) would be generated. I think that this will not impact the website speed.
Although right now it may not be possible by the website team in view of pre-occupation with other long pending requests, this may be included in the WL and be considered for try out and implementation later but as early as possible.

@moderator:
As a followup to the previous post:
Anyone can make a PNR prediction - anonymous, logged-in users and admins. However, as can be expected, anonymous bloggers will not have a prediction history/accuracy score.

@moderator:
Good feature added.

@moderator:
Nothing is happenning when I click on any of the tabs for PNR prediction.

@Kapadia : Mar 19 (01:13PM)
Indeed Good feature introduced.

@moderator:
Thanks Moderator for accepting my suggestion. I am sure that it will make our site more interesting.

@Kapadia : Mar 19 (01:13PM)
Thanks. The feature was earlier suggested by Jitesh, and some other admins - so thanks to them as well.
The accuracy score and other metrics will be visible next to the name - soon to be introduced.
Before that, another link to mark/set the final status of the PNR on the day of journey. Without this, it will not be possible to validate the prediction against the final status. Only logged-in users and admins will be able to set the final status of the PNR, to prevent abuse. When the final status of any PNR is set, the predictions for that PNR will be automatically scored.

@Manish: Mar 19 (01:14PM)
Please try again. There was a glitch, which has now been fixed. Thanks.

@moderator: Mar 19 (01:21PM)
Yes, now it works.

@moderator: Mar 19 (01:20PM)
Nice feature added Sir
Regards
HE2L

@moderator: Mar 19 (01:21PM)
Dear Sir,
There is some modification are require in new feature.
I think when we predict some one PNR then our No. of Post will be not increase.
Suggestion welcome from other admins/bloggers
Regards
HE2L

@HD: Mar 19 (01:33PM)
Yes, thank you. Good point.

@moderator: Mar 19 (01:35PM)
is this feature available to registered users only?

@anon: Mar 19 (01:37PM)
The feature - that is making PNR predictions - is available to everyone, including anonymous users. However, as you can expect, anonymous users will not be able to track their prediction history/accuracy score (soon to be introduced features).
Each anonymous (by IP address) or logged in user gets only one vote on a PNR.
This is a new feature, and many modifications will be made over the coming days and weeks, as needs and concerns are identified.

@moderator: Mar 19 (01:20PM)
Some queries regarding setting the final status of PNR.
1)What happens if no logged in user sets the final status of PNR? Wil there be any mechanism by which the final status of PNR is set automatically on chart preparation.
2)What happens in case of Partially waitlisted tickets where some passengers are confirmed/RAC and others are waitlisted at time of charting? Whose prediction will be considered as correct in this case.

@moderator:
In the present feature, a new blog entry is made for each prediction.The number of blogs seem to be increasing rapidly and it is getting difficult to track blogs.
I would suggest to introduce something similar to the "Rate Comment" feature that is already available. Whenever any user select any option for prediction, the count will be automatically increased. If one wishes to see who has predicted what, he can click on any option on which a pop-up displaying the responses of various users is provided.

@Manish: Mar 19 (02:55PM)
Very valid points indeed. With immediate effect, to maintain the quality of predictions, only logged-in users may make predictions. Also, all PNR analysis entries are being moved to a new subtab, with the rest of the entries staying on the main page. Thanks.

@moderator: Mar 19 (03:05PM)
Thanks a lot for super fast implementation of suggestions.

@moderator: Mar 19 (03:05PM)
Many many complementes to the Moderator and the full website team for this feature.
Very right sir, the feature will require to be upgraded / filtered in future as and when concerns are identified.
i) One such concern is that about PNR score of any ticket which subsequently gets cancelled by the passenger. Those scores will need to be scrapped from the aggregate PNR score to the credit of admin/logged in user.
ii) Tatkal PNRs - it's entirely subjective and any type of prediction is based on conjectures and surmises. Scores aggregating of General PNR's and Tatkal PNR's may present a distorted result and not the one desirable.
However, I hold a view that it should be made amply clear to the visitors that neither any sure pattern exists nor any standard criterias exists for ticket confirmation. The score is based on the experience, judgements and expectations of the admins / logged in users and thus ... it is views only.
The bloggers are to be advised not to too much rely on the score and be prepared for any eventuality. Sort of standard disclaimer ought to appear at appropriate place.
As everybody knows, Number of factors play its role such as seasonal factor (now summer season) , particular train factor, its frequencey, tourist place important factor, commercial place importance factor . religious place importance, peak season, off peak season, announcement of spl train and many others.
The views will thus be entirely subjective, judgemental and more to the luck factor in some typical PNR's. More positive score may not necessarily result into confirmed status and more negative score may not necessarily result into non-confirmation.
Moderator may look into and respond. As always, Views of fellow admins are also welcome.

@Kapadia : Mar 19 (05:15PM)
Dear Kapadia Ji
Thanks for your valuable feedback, as you know that now anonymous predictions have been stopped, because here what matter is quality not quantity. People may just predict it by blind guessing. Suppose 6 out 10 10 responses say it will not get confirmed and due to this the blogger may cancel the tickets while it may be blind guess. So this was not the purpose of my suggestion. It was only for some exercise to make site more interesting.
So I invite views from fellow bloggers to make this feature more useful and interesting.

@Kapadia :
A very good suggestion indeed. Moderator may please look into this suggestion by Mr Kapadia.

@Kapadia :
Enhanced blog search has been a long-pending request, which was getting pushed back in favour of other features. Thanks a lot for once again bringing it to the fore.
Enhanced/fast blog search has now been implemented. Also, the search functionality itself has been made faster. Details (also available in a separate "feature announcement" blog post) are as follows:
1. The search box now says "search phrase", instead of "search word". You can type in as many words as you want. All your typed words will be matched against each blog entry + replies.
2. Results are sorted such that Blog Entries with the most recent activity will appear first.
3. Each word typed into the box is individually auto-completed, and adds to the search phrase.
Hope the enhanced search feature helps everyone in performing more focused searches through the knowledge-base/archives.

@moderator: Mar 08 (06:33PM)
Great feature. Thanks for quick implementation.

@moderator: Mar 08 (06:33PM)
Thanks a lot for implementation of a feature of great importance.

@Kapadia : Mar 08 (06:36PM)
congrts on reaching 1000.

@Kapadia : Mar 08 (06:36PM)
Thanks again. The search also takes into account train title headings in the search territory. This is meeting of long pending request. Late - better then never.

@moderator: Mar 08 (06:33PM)
In Post # 22364 there is following entry:
"Date of Journey: Wed Mar 17"
I tried searching with Mar 17 in the "Search Phrase box, but no result came up.Please look into it.

@anon: Mar 08 (06:42PM)
Thanks a lot.

@Manish: Mar 08 (06:54PM)
Thanks for notifying. Fixed.

@moderator: Mar 08 (09:09PM)
Now if I search with Mar 17, all blogs that have "Mar" and "17" are also being shown.Is there any way we can restrict the search results to show only those entries having "Mar 17".

@moderator: Mar 08 (09:09PM)
Moderator may please look into this. Similar request also raised by Jhentee Jivraj in Blog Entry #24839

@Kapadia :
Changed. Thanks.

@moderator: Feb 01 2010 (04:56PM)
hi hello

@moderator: Feb 01 2010 (04:56PM)
i m mazhar

@first blogger:
Thanks for informing. 2749 has been added to the site. 2750, official timetable not available yet - will try later.

@first blogger:
Kindly name this train as ARIHANT express.

@anon: Mar 18 (10:55AM)
Please state your reason/source for renaming this train. Thanks.

@anon: Mar 18 (10:55AM)
why is it caled Arihant express???

@first blogger:
no chance

@first blogger:
which class? Without that it is NOT possible to give a correct reply. IF it is sleeper then chances of coming into RAC and possible confirmation is there ... good wishes.
@other blogger: without knowing the class you are able to say no chance? Are you an astrologer, or you in the Railway booking counter? Good wishes.

@Murli: Mar 16 (04:38PM)
sry 4got 2 mention; yes its sleeper

@Murli: Mar 16 (04:38PM)
DEAR MURALI
Then how u r saying chances are there? U are aalso gussing no body here can tell the correct position until CHART PREPARED . So u have no right to post those kind of comments to the first blogger. He has converyed his opinion like wise U too and every body here is conveying their opinion regarding different quries accoding to their logic. So he may be having his own logic to explain for his answer like wise U too. But no no comments like who are You an ASTROLEGER?, Why to insult a fellow blogger? all those things are not goood. CAN I ASK U 1 QUESTION HOW YOU SAID THAT IT WILL COME TO RAC are you an ASTROLEGER?

@anon: Mar 16 (06:05PM)
I wished you had answered the question of the first blogger instead of responding to my comment. And do note that even now you have not answered that question raised. How can a person without knowing the class simply say no chance? The train is one of the slow ones from MAS to Mumbai, and that is why I first responded to that first and then wrote about the other blogger. Anyway you have as much right to your opinion as I ... so no issues, and I don't mind your statement at all.
@first blogger: you have a chance as I said with W/L 85 (it must have gone up now, unless you booked already... pls post your present status and some of us will try and see what chances you have. Forget the rest of the comments here. I stand by my position.
Good wishes to all on this particular blog !

@Murli: Mar 16 (07:13PM)
See Murli my point is whether he will get confirmed or not is the issue. The way U have responded to the other blogger (NITIN) U R COMMENT towards his answer to the first blogger matters.
One example is blog #23693 where IRFANB has answered NO CHANCE FOR a query and look how JITESH has responeded. Jithesh replied dont say like that always there is a chance of 50:50 and finally the passenger got CONFIRMED
In another blog #20977 IRFAN answered Yes and immediately HD answerd to IRFAN that he is kidding, how U say no, this is nonsense and this is the last warning for You etc but ultimately the passenger got CONFIRMED.
My point here is see how JItesh and HD responded to the bloggers questions. Jitesh in more civilized manner aand HD not like that and U also to NITIN the same way.
Another point here is INFRAN was wrong in his first case and right in second case regariding his answers. That is why i have told all are gussing here acording to their knowledge and experience and u have right to correct them but in a more civilized maanner and respect each other.
I think because U are ADMIN: and u can write anything or what? to other bloggers
GOOD LUCK

@anon: Mar 16 (07:44PM)
Dear Sir
Thanks for your comments on me.
I also want to say some thing on the issue. This is right that no can 100 % predict about a pnr's final status that is why I never say 100 % (or in rare cases). I stuck up to 99 %. There may be some mistakes by us.
Murli Ji & HD are reputed, old & respected blogger of the forum. I learnt many things from both of them.
Specially about Mr Murli Ji, He is such a knowledgeable person, apart from our friendship(Me, Mr Murli & HD) we both(HD & Me) are fan of Mr Murli that he is such a rail crazy person. You just ask him any thing & I know he is the person which will help you in the late night also. You can see his late night posting on the blog, He is always ready to help you. You will be amazed to know that we three(Me, Mr Murli & HD) never meet each other but still we trust each other & so we share all of our expreience with each other.
Thanks for praising me but I request you to be polite for him.
I think he is the elder most person on the forum so deserves respect.
Thanks & Regards.

@Jitesh: Mar 16 (08:03PM)
Jitesh Thanks for the comments.
One point Murli may be experienced than me and U and may be senior most person in this site and that means he can insult by asking questions like ARE U AN ASTROLOGER or RAILWAY BOOKING CLERK ? to a blogger. If he is such a nice and experienced person means he is the one who has to guide other bloggers here with good outlook. not like this way may be he may have not ment that but by going through one feels like that.
And he has asked YOU COULD HAVE BETTER ANSWERED THE QUESTION but until there is PNR # i wont answer to a bloger that is why i have not answered and in soem case if we ask for PNR they wont even respond. So i answeres to PNR queries only. Likewise each INDIVUIDAL will be haaving his own expertise here to answer questions. So one should not insult the other blogger who had answered to a query. I hope u maay have gone through the blog #20977 and see how HD has responded to IRFAN is that way?
If MURLI is a great fan or experienced person, from my point view he should not have made a comment like that. He should be the person to guide other bloggers.
Any way good luck for this beautiful site, admins, moderators, and bloogers.

@anon: Mar 16 (08:17PM)
Hello Sir,
Thanks for comment on US.
I suggest you please login 1st & afterwards post your blog(s).
Regards
HE2L

@HD: Mar 16 (10:40PM)
Posting blog comments, thinking about chances of cofirmation, etc. take time and effort, and the fact that our bloggers/admins are doing it is itself a great thing. As for prediction accuracy, we all know and realize that it is not 100%.
From a suggestion given by our admins - Jitesh, HD and Murli - (maybe as a result of this discussion), we are working on a feature whereby "PNR Predictions/Analysis" are shown on a separate tab. Also, we are going to make it easy for everyone to verify the final WL charting status on the day of the journey, for those PNRs for which a prediction was made. This feature will help us track and go back and verify the prediction, and also keep a score on prediction accuracy - maybe even individual metrics.
This feature will keep each person's prediction metrics, and will lend some objectivity. Maybe it will also be a fun exercise for those people who make the prediction, to finally know how it turned out.
Thanks a lot for the discussion. As can be seen here, all debates, even arguments, can result in some great ideas.

@first blogger:
There can not be two entries with blog post nos. # 24403. I checked up and there is only one blog post bearing entry # 24403. Plz be clarified by re-checking yourself.

@Kapadia : Mar 16 (09:39PM)
that is why i have pasted the entries which was seen in the blog - if you notice entry no.24403 is shown as 60 number and also 61 no. ( I have copy pasted only the first entry. all replies are same - this was uptil some time ago. now the Serial numbers would have changed. thanks

@anon: Mar 16 (09:49PM)
Anyway, that the problem is no more. This must be bcoz of overlapping in entries happening some times when you click on the bottom tab for next page. Certain blog entries are repeated in view of new incoming blog entries. If anything else is there, plz post it.

@Kapadia : Mar 16 (09:57PM)
Thanks for the discussion. There are no duplicate entries in the blog/forum. But, what the first blogger above saw was real and valid. What happens is this:
1. While viewing entries, when you click the "NEXT PAGE" button, the next 10 entries are brought up.
2. But what happens if in the meanwhile someone added a new blog entry? The last entry in the "current page" gets pushed as the first entry in the "next page".
3. So, now when you click the "NEXT PAGE" button, you once again see the last entry in the current page as the first entry in the new page. Looks like there is some duplication.
4. So, apologies for the confusion. It is the nature of the software, and it happens due to a peculiar sequence of circumstances. But, the main thing here is that this is only a "presentation problem". There is no underlying bug here.
Thanks for your patience, and we shall look at ways to mitigate the confusion when the above sequence of events happen.

@moderator: Mar 17 (03:37AM)
thanks for the clarification. i will look into this feature once again.