20889 Howrah Jn - Tirupati Humsafr Express Time Table
- Arrives
- 13:55 day 2
- Tirupati TPTY
- Journey
- 25h 25m
- 1617 km · 12 stops
20889 Howrah Jn - Tirupati Humsafr Express leaves Howrah Jn (HWH) at 12:30 and reaches Tirupati (TPTY) at 13:55 on day 2 of the run. The booked run is 1617 km in 25h 25m, with 12 stops including both ends. It is the only train this timetable version books from Howrah Jn (HWH) through to Tirupati (TPTY). Runs Sat.
20889 at a glance
| Runs on | Sat |
|---|---|
| Calendar row for this train | to — beyond 2026-09-30, so not a date we stand behind |
| Timetable version covers | to |
| Average speed | 63.6 km/h including halts — ours (how) |
| Type | Express · Express |
| Reservation | Reserved (PRS) train. 20889 is a 1-, 2- or 8-series number: those are reserved. (how we decide) |
Time table and route
| Station | Arrives | Departs | Halt | Km |
|---|---|---|---|---|
| HWH Howrah Jn | start | 12:30 | — | 0 |
| KGP Kharagpur Jn | 14:10 | 14:15 | 5m | 116 |
| CTC Cuttack | 18:23 | 18:25 | 2m | 411 |
| BBS Bhubaneswar | 18:50 | 19:00 | 10m | 438 |
| VZM Vizianagram Jn | 00:33 +1 | 00:35 +1 | 2m | 820 |
| VSKP Visakhapatnam | 01:30 +1 | 01:50 +1 | 20m | 881 |
| RJY Rajamundry | 04:48 +1 | 04:50 +1 | 2m | 1082 |
| BZA Vijayawada Jn | 07:15 +1 | 07:25 +1 | 10m | 1231 |
| OGL Ongole | 09:23 +1 | 09:25 +1 | 2m | 1370 |
| NLR Nellore | 10:53 +1 | 10:55 +1 | 2m | 1486 |
| RU Renigunta Jn | 13:08 +1 | 13:10 +1 | 2m | 1607 |
| TPTY Tirupati | 13:55 +1 | end | — | 1617 |
What 20889’s schedule looks like
Its longest run without a stop is 382 km and 5h 33m from Bhubaneswar (BBS) to Vizianagram Jn (VZM). The next longest is 295 km and 4h 08m from Kharagpur Jn (KGP) to Cuttack (CTC).
At 22:00 it is between Bhubaneswar (BBS) and Vizianagram Jn (VZM), and at 06:00 on day 2 of the run it is between Rajamundry (RJY) and Vijayawada Jn (BZA).
4 of its 10 intermediate stops are booked for five minutes or more, the longest of them 20 minutes at Visakhapatnam (VSKP), 10 minutes at Bhubaneswar (BBS), 10 minutes at Vijayawada Jn (BZA), 5 minutes at Kharagpur Jn (KGP). The briefest stop is 2 minutes at Cuttack (CTC).
The run crosses midnight before Vizianagram Jn (VZM); every later time carries a day marker.
It passes its own halfway mark of 808 km at Vizianagram Jn (VZM), stop number 5 of 12, and is booked to stand at its stops for 57 minutes in all, 4% of the 25h 25m journey.
Its quickest booked leg is Ongole (OGL) to Nellore (NLR), 116 km at an average of 79 km/h.
After Howrah Jn it calls first at Kharagpur Jn (KGP), Cuttack (CTC), Bhubaneswar (BBS), Vizianagram Jn (VZM) and Visakhapatnam (VSKP).
Its last stops before Tirupati are Rajamundry (RJY), Vijayawada Jn (BZA), Ongole (OGL), Nellore (NLR) and Renigunta Jn (RU).
Its stops are not evenly spread: 3 of the 10 fall in the first half of the distance and 7 in the second.
The busiest stations on its route are Howrah Jn (HWH), where 704 trains call, Vijayawada Jn (BZA), where 480 trains call, Kharagpur Jn (KGP), where 337 trains call.
Other trains that share 20889’s route
From 20889’s halt rows, not its name. Trains without a page here are left out.
- 12864 SMVT Bengaluru Howrah Express — SMVB to HWH, 12 stations in common with 20889
- 12659 Nagercoil Junction - Shalimar Gurudev Superfast Express — NCJ to SHM, 11 stations in common with 20889
- 22851 Santragachi Jn - Mangalore Central Vivek Superfast Express — SRC to MAQ, 11 stations in common with 20889
- 12253 SMVT Bengaluru - Bhagalpur Anga Express — SMVB to BGP, 10 stations in common with 20889
Reservation chart and seat availability
20889 is booked out of Howrah Jn at 12:30, which puts it under rule RB-16.12.2025-A: its first reservation chart is expected at about 20:00 on the day before the journey. How we work this out.
It assumes 20889 is charted at Howrah Jn. The rule is press-reported: no circular number has been located, and the first report covered one zone. Preparation can be later. The circulars, the second chart and what is still unsettled.
Check live seat availability for 20889 — Howrah Jn to Tirupati, fetched when you ask and never stored here (how).
Where this came from
Every time and distance above is read from timetable version , and from nothing else. Where the timetable data comes from.
The 20:00 above comes from a published railway order, worked out, never observed.