About RailSetu
RailSetu is a passenger-first journey planner for Indian train travellers. When a direct ticket is waitlisted, it looks for confirmed segments on the same train and explains the changes as one simple journey.
A berth may be unavailable from point A to B even when confirmed seats exist across smaller parts of that exact route. Finding those combinations manually is slow, confusing and easy to get wrong.
RailSetu searches for a continuous chain of confirmed segments, then makes every seat or coach transition visible before the traveller chooses it.
How the engine thinks
Read availability across the train’s route, not only the requested origin and destination.
Build continuous options that keep the traveller on the same train while seats or coaches change.
Filter by mobility, luggage, family needs and comfortable interchange time before showing the clearest route.
Built around the traveller
Comfort Score, in the simplest words
Think of it as an effort meter, not a promise that a ticket will be confirmed.
A simple journey begins with a full score.
Changing seats, managing another ticket, walking to a different coach, moving at night, or getting the wrong berth makes the number smaller.
The same change matters more for an elderly traveller, a family, or someone carrying heavy luggage. Staying in one coach or matching a requested lower berth can add a few points back.
Big number = easier journey. RailSetu uses it to rank valid paths; it never replaces live availability or a booking confirmation. See the full calculation →
Cancelled-ticket refunds
For confirmed tickets, RailSetu estimates the deduction using IRCTC's time bands: a class-based charge more than 48 hours before departure, 25% from 48–12 hours, 50% from 12–4 hours, and no refund inside four hours. Minimum charges and GST may apply. The Wallet destination is a prototype convenience; official e-ticket refunds normally return to the original payment account. Read the official rules ↗
What the build makes obvious
RailSetu is designed so the problem, the intervention and the prototype's limits are visible without a pitch.
Indian train travellers whose direct option is waitlisted—especially elderly passengers, families, people with limited mobility and anyone carrying luggage who cannot treat every seat or coach change as equally easy.
Availability is usually checked as one origin-to-destination request. Confirmed berths across consecutive portions of the same train remain hidden, leaving travellers to repeat searches, compare stations and verify continuity manually.
RailSetu treats a train route as a chain of bookable segments. It joins confirmed segments on the same train, filters them against traveller constraints and explains the station, time, coach and seat involved in every change.
It turns fragmented availability into one understandable journey. Travellers can compare confirmed paths by effort—not only fare—using an explainable Comfort Score, visible transitions, a route map and saved preferences.
The end-to-end experience, segmentation logic, traveller-aware filtering, Comfort Score, saved presets, map, checkout handoff and downloadable ticket work in the prototype. Live inventory, reservation locking, payment and official ticket issuance currently use representative data or simulated integrations.
Use authorised railway APIs, revalidate every segment before payment and reserve every leg atomically—or charge nothing. Minimise and encrypt personal data, audit ranking decisions, monitor availability and keep RailSetu clearly labelled as a planner until official booking integration is approved.
Under the hood
Every language, framework, library and production tool currently used to build and run the experience.
Move your pointer over the stack to pause it.
Made with travellers
Tell us what felt useful, confusing, or missing. Short and honest is perfect.