RailTC Master Guide
This is the single reference page for how RailTC works in practice. Use it as an operating manual for daily use.
- 1) Understand what each feature does
- 2) Follow exact usage steps
- 3) Avoid common mistakes and dead ends
Quick Navigation
- PNR Prediction (Live Check)
- Paid Notify Alerts
- Current Availability Release Alert
- Pre-Booking Analysis (Single Journey)
- Pre-Booking Multi Route Compare
- Connections (Transfer Delay Risk)
- OTP, Access Link, and Credits
- History and Past Journeys
- Accuracy and Verification Pages
- Utility Tools (Track Train, Yesterday Status, Seat Info)
- Recommended Workflows
- Troubleshooting
1) PNR Prediction (Live Check)
Where: Home page (PNR checker)
What it does: Checks your current PNR status and gives a probability score with recommendation.
How it works: RailTC fetches latest PNR data and runs a multi-factor model (waitlist behavior, class/quota behavior, timing effects, and confidence scoring).
How to use
- Enter 10-digit PNR on homepage.
- Click check/predict.
- Read probability, risk label, recommendation, and detailed factors.
- If needed, use "Get Alerts" directly from result card.
Best practice
- Do not rely only on one old check. Re-check closer to chart prep.
- For critical travel, treat medium/uncertain outcomes as planning signals, not guarantees.
2) Paid Notify Alerts
Where: PNR result card via Get Alerts
What it does: Instead of manually checking, RailTC sends email updates for your selected plan.
Daily Auto-Check
We keep checking and notify daily until chart preparation.
Chart-Ready Alert
Single notification when chart is prepared.
How to use
- Open PNR result and click Get Alerts.
- Select notify plan.
- Enter email.
- Complete payment via Cashfree.
- Wait for confirmation message in modal.
3) Current Availability Release Alert
Where: Same Get Alerts modal in PNR flow
What it does: Monitors your exact train profile and alerts when current availability opens after chart-related release window.
Profile monitored: Train number, journey date, from/to station, class, quota.
How to use
- Open Get Alerts modal after PNR result.
- Select Current Availability Alert.
- Verify profile preview carefully.
- Enter email and complete payment.
- RailTC monitor activates and checks until trigger/expiry window.
Important
- If profile is incomplete or invalid, this option can remain disabled.
- Use exact stations and class matching IRCTC profile behavior.
4) Pre-Booking Analysis (Single Journey)
Where: Pre-Booking page
What it does: Helps before booking, not after booking. You get probability and recommendation for a specific train/date/station/class/quota context.
How to use
- Select Single Journey mode.
- Fill train number, date, from/to, class, quota (and WL context where needed).
- Pay or use existing credits.
- Run analysis and review detailed factors.
When to use
- You already know which train you want.
- You want one clear go/no-go recommendation.
5) Pre-Booking Multi Route Compare
Where: Pre-Booking page in Multi Route Compare mode
What it does: Compares many train/date contexts and ranks best options, useful when route/date/train is flexible.
How to use
- Select Multi Route Compare.
- Enter primary route and date.
- Add additional routes in
FROM-TO format (one per line).
- Select suitable compare plan and pay/use credits.
- Run compare and check ranked options.
- Click any row to open detailed per-ticket analysis.
What results mean
- Best options (ranked): Top picks by probability and risk profile.
- Processed vs successful: Some contexts can fail if profile rejected or unavailable.
- Row details: Full analysis card per context, similar to single journey output.
6) Connections (Transfer Delay Risk)
Where: Connections page (header: Connections)
What it does: Helps when you change trains. First it shows free transfer time (how long you have between Train A arrival and Train B departure). When enough delay history exists for that train and station, you can unlock the chance of missing the second train if the first one runs late.
How to use
- Open /connection-risk.
- Enter first train number and its journey start date.
- Enter connecting station code (for example NDLS).
- Enter second train number and its journey start date.
- Optionally set a buffer for platform change time.
- Tap check to see free transfer time.
- If enough delay days are available, pay or use credits to unlock the miss-risk report.
What results mean
- Transfer time: Scheduled minutes between arrival and departure, minus your buffer.
- Sample size: How many past days of delay data we have for that train at that station. Below 10 days, paid unlock is not offered.
- Miss chance: Historical chance the first train arrives too late to make the second, given your buffer.
Best practice
- Use each train’s journey start date (when it leaves its origin), not only the change-day date.
- Pick a second train that actually departs from the connecting station (not one that terminates there).
- Treat this as a planning signal, not a guarantee of on-time running.
7) OTP, Access Link, and Credits
Why this exists: To keep paid credits safe across devices and prevent unauthorized usage.
Access link flow
- Use "Access credits on another device".
- Enter same email used for purchase.
- Open secure link from inbox/spam.
- You will land on pre-booking with history token and available credits.
OTP flow
- Some sensitive operations require OTP verification.
- After OTP success, analysis auto-resume is supported in current flow.
8) History and Past Journeys
Where: Pre-booking history drawer and secure history links
What it does: Lets you re-open previous analyses and compare old decisions with current travel planning.
Use cases
- Re-check route options without rebuilding everything.
- Review pattern over multiple dates.
- Open old orders directly from email links.
9) Accuracy and Verification Pages
Where: Accuracy page
What it does: Shows tracked outcomes and confidence-bucket behavior so users can judge model reliability transparently.
How to use
- Check overall trend, not one isolated number.
- Read bucket-wise behavior to understand safe/risky zones.
- Use this page before deciding your risk tolerance.
A) Live Train Status (Track Train)
Where: /track-train — also linked as Track Live from PNR ticket cards.
Purpose: Check Indian Railways live running status by train number: current position, delay, next halt ETA, platforms, map, and full route timeline.
How to use: Enter the 5-digit train number and tap Track Live. After a PNR analysis, open Track Live on the ticket card to jump straight into the same train.
B) Seat and Coach Helpers
Where: Seat info and berth helpers integrated in result flows.
Purpose: Understand coach/berth position and parse status text correctly.
C) Train Route/Schedule
Where: Route button in ticket cards and schedule helper.
Purpose: Validate station sequence and planning context.
11) Recommended Workflows
Workflow A: Already booked ticket
- Run PNR prediction.
- If medium/uncertain, activate notify alert.
- Open Live Train Status closer to departure for delay and next halt ETA.
- Track confirmation outcome closer to chart preparation.
Workflow B: Not booked yet (single route)
- Go to pre-booking single mode.
- Run context analysis.
- Book only if recommendation aligns with your risk level.
Workflow C: Flexible travel decision
- Use multi route compare.
- Open top 3 rows in detail view.
- Choose by probability + confidence + practical timing.
Workflow D: Changing trains at a junction
- Open Connections and check free transfer time.
- If history is available, unlock miss-risk before booking a tight change.
- On travel day, use Live Train Status for the first train’s live delay.
12) Troubleshooting
Issue: Payment done but result not visible
- Open status/history using same email token.
- Refresh from secure link instead of re-paying.
- Check order mode: single vs route-compare endpoint behavior differs.
Issue: Multi-route row shows failure
- Usually context mismatch: station, class, quota, date profile rejected.
- Try nearby date or alternate route/class.
- Keep successful contexts; one failure does not invalidate complete run.
Issue: Release alert option disabled
- Profile extraction incomplete from current ticket context.
- Ensure valid train number and station codes in result.
Issue: Access link not received
- Check spam/promotions folder.
- Use same purchase email and retry after a short gap.
- If still blocked, use Contact with order details.
Final Notes
RailTC is designed for decision quality, not blind optimism. The strongest way to use it is:
- Use pre-booking tools before money is locked in.
- Use notify/release alerts to avoid manual repeated checking.
- Use multi-route compare when flexibility exists.
- Always keep one backup option for high-impact travel.
Open Pre-Booking Tool
