15627 Coimbatore Jn - Silchar Express Time Table
- Departs
- 22:00
- Coimbatore Jn CBE
- Arrives
- 16:45 day 4
- Silchar SCL
- Journey
- 66h 45m
- 3496 km · 46 stops
15627 Coimbatore Jn - Silchar Express leaves Coimbatore Jn (CBE) at 22:00 and reaches Silchar (SCL) at 16:45 on day 4 of the run. The booked run is 3496 km in 66h 45m, with 46 stops including both ends. It is the only train this timetable version books from Coimbatore Jn (CBE) through to Silchar (SCL). Runs Sun. That is a stop every 78 km on average.
15627 at a glance
| Runs on | Sun |
|---|---|
| Calendar row for this train | to — beyond 2026-09-30, so not a date we stand behind |
| Timetable version covers | to |
| Average speed | 52.4 km/h including halts — ours (how) |
| Type | Express · Express |
| Reservation | Reserved (PRS) train. 15627 is a 1-, 2- or 8-series number: those are reserved. (how we decide) |
Time table and route
| Station | Arrives | Departs | Halt | Km |
|---|---|---|---|---|
| CBE Coimbatore Jn | start | 22:00 | — | 0 |
| TUP Tiruppur | 22:40 | 22:42 | 2m | 51 |
| ED Erode Jn | 23:20 | 23:25 | 5m | 101 |
| SA Salem Jn | 00:17 +1 | 00:20 +1 | 3m | 160 |
| JTJ Jolarpettai Jn | 02:03 +1 | 02:05 +1 | 2m | 284 |
| KPD Katpadi Jn | 03:10 +1 | 03:25 +1 | 15m | 367 |
| AJJ Arakkonam Jn | 04:13 +1 | 04:15 +1 | 2m | 428 |
| PER Perambur | 05:05 +1 | 05:10 +1 | 5m | 491 |
| OGL Ongole | 10:18 +1 | 10:20 +1 | 2m | 782 |
| BZA Vijayawada Jn | 12:50 +1 | 13:00 +1 | 10m | 921 |
| RJY Rajamundry | 15:28 +1 | 15:30 +1 | 2m | 1070 |
| VSKP Visakhapatnam | 19:05 +1 | 19:25 +1 | 20m | 1271 |
| VZM Vizianagram Jn | 20:15 +1 | 20:20 +1 | 5m | 1332 |
| CHE Srikakulam Road | 21:08 +1 | 21:10 +1 | 2m | 1401 |
| PSA Palasa | 22:18 +1 | 22:20 +1 | 2m | 1474 |
| BAM Brahmapur | 23:15 +1 | 23:20 +1 | 5m | 1548 |
| BALU Balugan | 00:13 +2 | 00:15 +2 | 2m | 1624 |
| KUR Khurda Road Jn | 01:15 +2 | 01:25 +2 | 10m | 1695 |
| BBS Bhubaneswar | 01:50 +2 | 01:55 +2 | 5m | 1714 |
| CTC Cuttack | 02:25 +2 | 02:30 +2 | 5m | 1741 |
| JJKR Jajpur K Road | 03:18 +2 | 03:20 +2 | 2m | 1813 |
| BHC Bhadrakh | 04:18 +2 | 04:20 +2 | 2m | 1856 |
| BLS Balasore | 05:07 +2 | 05:09 +2 | 2m | 1915 |
| KGP Kharagpur Jn | 06:40 +2 | 06:48 +2 | 8m | 2036 |
| DKAE Dankuni | 09:32 +2 | 09:37 +2 | 5m | 2158 |
| BHP Bolpur S Niktn | 11:38 +2 | 11:43 +2 | 5m | 2289 |
| RPH Rampur Hat | 12:49 +2 | 12:51 +2 | 2m | 2350 |
| NFK New Farakka Jn | 14:53 +2 | 14:55 +2 | 2m | 2437 |
| MLDT Malda Town | 15:55 +2 | 16:05 +2 | 10m | 2472 |
| KNE Kishanganj | 18:08 +2 | 18:10 +2 | 2m | 2617 |
| NJP New Jalpaiguri | 19:35 +2 | 19:45 +2 | 10m | 2705 |
| DQG Dhupguri | 21:08 +2 | 21:10 +2 | 2m | 2770 |
| NCB New Cooch Behar | 22:08 +2 | 22:13 +2 | 5m | 2831 |
| NOQ New Alipurduar | 22:30 +2 | 22:32 +2 | 2m | 2849 |
| KOJ Kokrajhar | 23:35 +2 | 23:37 +2 | 2m | 2928 |
| NBQ New Bongaigaon | 00:20 +3 | 00:30 +3 | 10m | 2959 |
| BPRD Barpeta Road | 01:15 +3 | 01:17 +3 | 2m | 3003 |
| RNY Rangiya Jn | 02:20 +3 | 02:25 +3 | 5m | 3068 |
| KYQ Kamakhya | 04:10 +3 | 04:12 +3 | 2m | 3109 |
| GHY Guwahati | 04:25 +3 | 04:40 +3 | 15m | 3116 |
| HJI Hojai | 06:50 +3 | 06:52 +3 | 2m | 3252 |
| LMG Lumding Jn | 08:00 +3 | 08:10 +3 | 10m | 3296 |
| MBG Maibang | 09:35 +3 | 09:37 +3 | 2m | 3361 |
| NHLG New Haflong | 10:50 +3 | 10:55 +3 | 5m | 3395 |
| BPB Badarpur Jn | 14:00 +3 | 14:15 +3 | 15m | 3466 |
| SCL Silchar | 16:45 +3 | end | — | 3496 |
What 15627’s schedule looks like
Its longest run without a stop is 291 km and 5h 08m from Perambur (PER) to Ongole (OGL). The next longest is 201 km and 3h 35m from Rajamundry (RJY) to Visakhapatnam (VSKP).
At 22:00 on day 2 of the run it is between Srikakulam Road (CHE) and Palasa (PSA), and at 06:00 on day 2 of the run it is between Perambur (PER) and Ongole (OGL).
22 of its 44 intermediate stops are booked for five minutes or more, the longest of them 20 minutes at Visakhapatnam (VSKP), 15 minutes at Katpadi Jn (KPD), 15 minutes at Guwahati (GHY), 15 minutes at Badarpur Jn (BPB), 10 minutes at Vijayawada Jn (BZA). The briefest stop is 2 minutes at Tiruppur (TUP).
The run crosses midnight before Salem Jn (SA); every later time carries a day marker.
It passes its own halfway mark of 1748 km at Jajpur K Road (JJKR), stop number 21 of 46, and is booked to stand at its stops for 233 minutes in all, 6% of the 66h 45m journey.
Its quickest booked leg is Cuttack (CTC) to Jajpur K Road (JJKR), 72 km at an average of 90 km/h.
After Coimbatore Jn it calls first at Tiruppur (TUP), Erode Jn (ED), Salem Jn (SA), Jolarpettai Jn (JTJ) and Katpadi Jn (KPD).
Its last stops before Silchar are Hojai (HJI), Lumding Jn (LMG), Maibang (MBG), New Haflong (NHLG) and Badarpur Jn (BPB).
Its stops are not evenly spread: 19 of the 44 fall in the first half of the distance and 25 in the second.
The busiest stations on its route are Vijayawada Jn (BZA), where 480 trains call, Perambur (PER), where 346 trains call, Kharagpur Jn (KGP), where 337 trains call.
At BZA it is booked in at 12:50 and away again at 13:00, 921 km into the run.
Other trains that share 15627’s route
From 15627’s halt rows, not its name. Trains without a page here are left out.
- 15607 Thiruvananthapuram Central - Silchar Aronai Express — TVC to SCL, 45 stations in common with 15627
- 12509 SMVT Bengaluru - Guwahati Express — SMVB to GHY, 36 stations in common with 15627
- 15645 Charlapalli - Silchar Express — CHZ to SCL, 32 stations in common with 15627
- 22503 Kanniyakumari - Dibrugarh Vivek Express — CAPE to DBRG, 31 stations in common with 15627
Reservation chart and seat availability
15627 is booked out of Coimbatore Jn at 22:00, which puts it under rule RB-16.12.2025-B: its first reservation chart is expected at about 12:00 on the day of the journey. How we work this out.
It assumes 15627 is charted at Coimbatore 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 15627 — Coimbatore Jn to Silchar, 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 12:00 above comes from a published railway order, worked out, never observed.