Time and Distance is built on one equation that you already know:
Everything else — trains, boats, cyclists, cars — is a rearrangement or extension of this. The reason this topic appears in nearly every RRB NTPC paper is that it can be disguised in dozens of forms: two vehicles approaching each other, a boat fighting a current, a train swallowing a platform. The core relationship never changes.
Here is the analogy that makes this click. Think of speed as your earning rate (₹ per hour), time as the hours worked, and distance as the total pay. If you earn faster (higher speed), you accumulate distance faster. If you work longer (more time), you cover more ground. The formula is the same arithmetic as salary calculations — just with different labels.
Unit conversion you must internalize:
These two conversions appear in at least one question every time trains are tested. If you hesitate here, you waste precious seconds.
What RRB NTPC actually tests under this chapter:
The chapter is not mathematically hard — it is trap-heavy. The mistakes happen not because the concept is unclear but because you pick the wrong formula for the wrong scenario. This page will fix that.
When a person travels the same distance at two different speeds, the average speed is not the arithmetic mean. It is the harmonic mean.
This formula applies only when the two distances are equal. If the times are equal (same duration at two speeds), then the arithmetic mean applies. NTPC loves to set up the "same distance" case and hope you pick the arithmetic mean.
Worked example: Travel 60 km at 30 km/hr, return at 60 km/hr.
Two scenarios:
| Direction | Relative Speed | |-----------|---------------| | Opposite directions | | | Same direction | |
This is the engine behind every "two trains" and "two cars" problem. When they move toward each other, they close the gap at the sum of their speeds. When they move in the same direction, the faster one gains on the slower one at the difference of their speeds.
Time to meet:
The key insight: when a train crosses something, the distance covered equals the train's own length plus the length of the object being crossed.
| Object crossed | Distance | |----------------|----------| | A pole / person (zero length) | Length of train | | A platform / bridge | Train length + Platform length | | Another train (same or opposite direction) | Sum of both train lengths |
For two trains crossing each other:
The pole trick: If a train crosses a pole in seconds and a platform of length in seconds, then:
Let = speed of boat in still water, = speed of river current.
Reversing these:
The exact same structure applies to a cyclist riding with or against the wind — just replace "current" with "wind." This is why the PYQ about the cyclist uses the identical formula.
When speed changes by a fraction or fixed amount, the time changes inversely (since distance is constant).
If speed decreases from to , extra time . Compute both times and subtract — do not try to shortcut this one unless the numbers are clean.
When a person walks north km then east km, the straight-line distance is . For RRB NTPC, the numbers are almost always a Pythagorean triple: (3,4,5), (5,12,13), (8,15,17). Recognizing these triples saves you from doing the arithmetic under exam pressure.
When the same distance is covered at two speeds S₁ and S₂, compute average speed as 2S₁S₂/(S₁+S₂). To apply it fast: multiply the two speeds, double it, divide by their sum. For S₁ = 40, S₂ = 60: numerator = 2×40×60 = 4800, denominator = 100, answer = 48 km/hr. Standard method (find each time, add, divide total distance) takes 5 steps and 40 seconds. This formula takes 2 steps and under 10 seconds.
Multiply km/hr by 5/18 to get m/s. For clean numbers, memorize: 18 km/hr = 5 m/s, 36 = 10, 54 = 15, 72 = 20, 90 = 25, 108 = 30. Train questions almost always use multiples of 18. When you see 108 km/hr in a train crossing question, stamp it immediately as 30 m/s — no multiplication needed. Standard conversion with long multiplication: 6 steps. Stamp recognition: 0 steps.
If a train crosses a pole in t₁ seconds and a platform of length P in t₂ seconds, train length L = P × t₁ / (t₂ - t₁). Derivation: speed = L/t₁ = (L+P)/t₂, so L·t₂ = (L+P)·t₁, giving L(t₂-t₁) = P·t₁. In the PYQ with P=200 m, t₁=15 s, t₂=30 s: L = 200×15/(30-15) = 3000/15 = 200 m. Direct substitution: 3 steps. Standard algebra: 5+ steps.
Still water speed = (downstream speed + upstream speed) / 2. Current speed = (downstream - upstream) / 2. These are the only two formulas you need for boats. When a question gives you two travel times over the same distance, first convert to speeds (Distance/Time), then average them. This handles cyclist-vs-wind questions identically. Recognition time from question to formula: under 3 seconds once this pairing is locked in.
Before computing √(a²+b²), check if (a,b) fits a known triple scaled up. Core triples: (3,4,5), (5,12,13), (8,15,17), (7,24,25). A question with 4 km north + 3 km east = 5 km answer, no calculation. A question with 12 km north + 5 km east = 13 km answer, no calculation. Standard method (square, add, root): 4 steps, 20 seconds. Triple recognition: 1 step, 2 seconds.
When you see a Time and Distance question, run this decision tree in under 5 seconds:
Step 1 — What type?
Step 2 — Units consistent?
Step 3 — What is unknown?
Step 4 — Check for traps.
Why this question: Tests whether you recognize the cyclist-vs-wind problem as identical to the boats-and-streams structure.
Solving path: Speed against wind = 30/2 = 15 km/hr. Speed with wind = 30/1.5 = 20 km/hr. Still-air speed = (15 + 20)/2 = 35/2 = 17.5 km/hr. The "still air speed = average of two observed speeds" pattern is identical to "still water = average of upstream and downstream." Once you see this, the question is a 10-second read.
Why this question: Classic average-speed trap — two legs of a journey with different speeds. Tests if you use the harmonic mean or mistakenly average the speeds.
Solving path: Let distance = . Time equation: . LCM of 60 and 40 is 120. So , giving , hence km. Do not try the harmonic-mean formula here — the question gives total time, not equal distances for each leg. Set up the time equation directly.
Why this question: Pure relative speed. Tests whether you add or subtract the speeds.
Solving path: Opposite directions → relative speed = 50 + 60 = 110 km/hr. Time = 330/110 = 3 hours. No conversion needed since everything is in km and hours. If the question had asked for the time in minutes, multiply by 60 at the end — do not convert speed first.
Why this question: Train crossing with unit conversion. The most common NTPC train question format.
Solving path: Opposite directions → relative speed = 45 + 63 = 108 km/hr. Stamp: 108 km/hr = 30 m/s (known multiple of 18). Distance (sum of lengths) = 30 × 12 = 360 m. The only danger here is forgetting to convert units. Always convert when time is in seconds.
Why this question: Train crossing a platform — the length-extraction problem.
Solving path: Let train length = . Speed = m/s. Same train crosses platform: . Multiply both sides by : . So m. Using the shortcut formula: m — same answer, one fewer algebraic step.
Using arithmetic mean for average speed with equal distances. If the two distances are equal, you must use . The arithmetic mean gives a number that looks plausible and is always an option — it is the distractor.
Forgetting to convert km/hr to m/s in train problems. The question gives speeds in km/hr and time in seconds. Using them together without conversion gives a nonsensical answer. Always check units before writing the distance formula.
Adding current to upstream speed instead of subtracting. Upstream means the boat fights the current — speed decreases. Downstream means it is aided — speed increases. Mixing these up reverses your answer entirely.
Counting only one train's length when two trains cross each other. The distance covered during a crossing is always the sum of both train lengths. Even when the question asks for the length of one train, the crossing distance includes both.
Applying relative speed addition to same-direction trains. Two trains in the same direction use the difference of speeds, not the sum. The sum applies only when they move in opposite directions. Drawing a quick arrow sketch — two arrows pointing the same way vs. opposing — removes this confusion in 2 seconds.
Confusing "still water speed" with "downstream speed." Still water speed is the average of upstream and downstream speeds. Downstream speed is always higher than still water speed by exactly the current speed. If your computed still-water speed is higher than the downstream speed, you have made an error.