Time, Speed and Distance (TSD) is the backbone of roughly 4–6 questions in every CDS Mathematics paper. The core relationship is deceptively simple:
But the exam never tests this formula directly. It tests your ability to manipulate it under constraints — stoppages, relative motion, partial journeys, fractions of usual speed. That is where aspirants lose marks.
Think of it this way: distance is a fixed corridor. If you walk slower, it takes longer. If you sprint, you finish early. Speed and time are always pulling against each other while distance stays constant. This inverse relationship between speed and time (when distance is fixed) is the single most exploited idea in CDS TSD questions.
A useful real-world anchor: imagine two soldiers starting from opposite ends of a 800 km supply route. The moment they move toward each other, they are consuming the gap at the sum of their speeds — that is relative speed in the "toward" direction. If they move in the same direction, the faster one is only gaining on the slower one at the difference of their speeds.
Unit conversions are where you bleed time in the exam hall. Burn these into muscle memory:
The fraction converts km/hr to m/s. Its reciprocal does the reverse. You will use these in virtually every train problem.
There are four question archetypes in CDS TSD:
Master these four and you have covered the entire chapter.
When distance is constant, speed and time are inversely proportional:
If speed becomes of usual, time becomes of usual. The extra time compared to normal is:
This is the direct route to "speed-fraction" problems. If you're given the extra time (), solve for immediately:
Do not set up a distance equation with variables for speed and distance. That approach takes 90 seconds. The ratio approach takes 15.
Every train problem hides an invisible variable: the length of the train (or trains). The train "passes" an object only when its entire body has cleared that object.
The formula that ties overtaking to walking persons:
where is in seconds and speeds are in km/hr.
Relative speed is just the speed of one object as seen from the reference frame of the other.
Meeting/overtaking problems collapse into simple TSD problems once you frame them in terms of relative speed and the "gap" to be covered.
Gap to be covered: If A starts hours before B, the head start distance is . B then covers this gap at a relative speed of (assuming , same direction).
Time for B to catch A:
Meeting point distance from B's starting station:
A train runs at speed but stops for minutes every hour. Its effective speed is:
Given , find :
Or equivalently: stoppage time per hour = minutes.
For CDS, the shortcut is even cleaner — the loss in speed directly gives you the loss in distance per hour, and at the running speed, that translates to stoppage time. No algebra needed.
When a train overtakes two persons walking in the same direction, you get two equations for two unknowns (train speed and train length). Write both length equations, set them equal, solve for speed, then back-calculate length. This is one of CDS's favourite question types — the structure repeats across years.
The cancels from both sides, simplifying the algebra considerably.
When speed changes to p/q of usual and distance is fixed, new time = q/p of usual. The delay or saving = |q/p − 1| × usual time. Micro-example: speed = 3/5 usual → time = 5/3 usual → delay = 2/3 × T. If delay = 20 min, T = 30 min instantly. Standard algebraic setup (two equations with S and D): 75 seconds. Ratio flip: 12 seconds — 4 lines of arithmetic versus 1.
Loss in speed per hour = (Running speed − Effective speed). Stoppage minutes per hour = (Loss ÷ Running speed) × 60. For CDS 2026 pattern: 60 − 48 = 12 km/hr loss. 12/60 × 60 = 12 minutes. You do not write a single equation. Standard distance-based equation method: 3 equations, ~60 seconds. One-liner: under 10 seconds.
Head start gap = (slower speed) × (time difference). Meeting point distance from chasing train's start = (chasing speed) × (gap ÷ relative speed). Commit to computing these two products in sequence and you will never lose track of which train's distance you're computing. Applying this to the Delhi-Hyderabad problem: gap = 80 × 5/6 = 200/3 km → catch time = (200/3)/20 = 10/3 hr → distance = 100 × 10/3 = 1000/3 km. Total working time: ~30 seconds. Setting up distance equations with a common variable t: ~90 seconds.
When two trains start at different times and travel toward each other, compute how far the first train has already gone before the second starts. Remaining gap = Total − covered. Then combine their speeds for closing rate. This 3-step sequence (covered, remaining, closing rate) handles every "trains from opposite stations" problem without any algebraic variable for meeting point. Step count: 3 multiplications, 1 division. Full variable setup: 5–6 steps.
In L = (v − u₁) × t₁ × 5/18 = (v − u₂) × t₂ × 5/18, the 5/18 cancels before you solve for v. You work purely with the speed differences in km/hr and time in seconds, which are the exact numbers given. This avoids the conversion step entirely during the equation-solving phase — apply conversion only once at the end when computing L. Standard approach (converting all units first): 4 conversion steps + algebra. This approach: 1 conversion step at the end only. Saves ~30 seconds on a 9-second/75/8-second problem.
Read the question and classify it in the first 10 seconds:
Is speed given as a fraction of usual? → Use the Speed-Fraction Flip. Time is the reciprocal fraction of usual. Delay or saving = fractional difference × usual time. Solve directly.
Is a train crossing something? → Identify what it is crossing. Set: Distance = train length + (platform/other train length if applicable). Relative speed = sum (opposite) or difference (same direction).
Two trains starting at different times? → Compute head-start distance. Divide by relative speed to get catch time. Multiply by the chasing train's speed for meeting distance.
Stoppages? → Loss in speed per hour is directly proportional to stoppage time. Stoppage minutes = (speed loss / running speed) × 60.
Train overtakes two walking persons? → Write two length equations, set equal, solve for train speed, then find length. Cancel the 5/18 factor before solving.
If none of the above applies clearly, fall back to: identify knowns, identify the one unknown, write D = S × T, solve. Don't reach for quadratics or simultaneous equations unless you have two genuine unknowns.
Why this question: The CDS 2023 train-overtaking question is a perfect two-equation TSD setup. It tests unit conversion awareness and the cancellation shortcut simultaneously.
Solving path: Let train speed = km/hr. Write two length expressions using relative speed × time × 5/18. Note that 5/18 appears in both — cancel it before solving. You get: . Cross-multiply: → → → km/hr. Then m.
Why this question: The stoppages question (CDS 2026) is a one-liner if you know the shortcut — but aspirants who set up distance equations waste nearly a minute here.
Solving path: Speed without stoppages = 60 km/hr. Speed with stoppages = 48 km/hr. The train "loses" 12 km every hour due to stops. At 60 km/hr running speed, 12 km takes minutes. That is the stoppage duration per hour.
Why this question: The speed-fraction problem (CDS 2025) is the canonical test of the inverse relationship. If you don't know the ratio trick, you will set up two distance equations and burn 60+ seconds.
Solving path: Speed = 3/5 usual → time = 5/3 usual. Extra time = min. Therefore minutes. Two lines of working. Done.
Why this question: The Delhi-Hyderabad overtaking problem (CDS 2024) appears twice in the spec with minor wording differences — CDS regularly recycles this structure. It tests head-start gap computation and meeting-point distance.
Solving path: Train A leaves at 7:00 a.m., Train B at 7:50 a.m. — a 50-minute = 5/6 hour gap. Head-start distance = km. Relative speed (same direction) = km/hr. Time for B to catch A = hr. Meeting distance from Delhi = km.
Why this question: The P-Q opposite-direction problem (CDS 2024) pairs a meeting-time question with a meeting-distance question — both solvable from one setup. Learn the setup once, answer two questions.
Solving path: Train A starts at 7:00 p.m., Train B at 4:00 a.m. — a 9-hour gap. A covers km before B starts. Remaining gap = km. Closing speed = km/hr. Time after B starts = hr = minutes = 1 hr 44 min. Meeting time = 4:00 a.m. + 1:44 = 5:44 a.m.
Forgetting the train's own length. When a train "passes" a platform or person, the total distance is the train length plus the platform length — or just the train length for a stationary point object. Aspirants routinely use only the platform length or only the train length. Write "D = L_train + L_obstacle" before plugging in any numbers.
Using the wrong relative speed direction. Same direction = difference of speeds. Opposite direction = sum of speeds. A common error is adding speeds when trains move in the same direction. Quick check: if they move together, the relative speed should be small; if they head toward each other, it should be large. Sanity-check your answer.
Applying the 5/18 conversion at the wrong stage. Either convert all speeds to m/s at the beginning, or keep them in km/hr and convert only the final length at the end. Mixing km/hr for one train and m/s for another inside the same equation produces wrong answers every time.
Confusing "distance from Q" with "distance from P." In opposite-direction meeting problems, always state clearly which station you're computing distance from. In the P-Q problem, B travels 156 km from Q — not 644 km, not 504 km. Label your answer before computing it.
Speed-fraction problems with percentage framing. "20% faster" means speed = 1.2S, so new time = T/1.2 = 5T/6. Time saving = T/6. Many aspirants treat 20% faster as 4/5 of usual time — that is wrong. The fraction you invert is the ratio of new speed to original, not the percentage directly.
Ignoring head-start in stoppage problems. Stoppages questions occasionally embed a head-start (e.g., the train already covered some distance before stoppages began). Read the problem for "without stoppages" vs. "with stoppages" phrasing carefully — the question is about per-hour stoppage, not total journey stoppage.