NCJ-KTYM EXP (16366) Historical Delay Report
The NCJ-KTYM EXP (16366) is highly reliable. Based on 7-day historical logs, it maintains an excellent punctuality record, typically arriving at KOTTAYAM just 0 minutes late. The only notable slowdown usually occurs near KAZHAKUTTAM.
7-Day Average Delay Statistics
| Station | Sch. Arrival | Avg. Actual Arrival | Avg. Delay |
|---|---|---|---|
| Station NAGERCOIL JUNCTIONNCJ | Sch. Arrival- | Actual ArrivalSource | Avg. DelayOn Time |
| Station NAGER COIL TOWNNJT | Sch. Arrival13:07 | Actual Arrival13:15 | Avg. DelayOn Time / +8m |
| Station ERANIELERL | Sch. Arrival13:19 | Actual Arrival13:37 | Avg. Delay+18m Late |
| Station KULITTHURAIKZT | Sch. Arrival13:35 | Actual Arrival14:08 | Avg. Delay+33m Late |
| Station PARASSALAPASA | Sch. Arrival13:46 | Actual Arrival14:22 | Avg. Delay+36m Late |
| Station DHANU VACHA PURAM HADAVM | Sch. Arrival13:52 | Actual Arrival13:52 | Avg. DelayOn Time |
| Station NEYYATTINKARANYY | Sch. Arrival13:59 | Actual Arrival14:39 | Avg. Delay+40m Late |
| Station THIRUVANANTHAPURAM CENTRALTVC | Sch. Arrival14:30 | Actual Arrival15:05 | Avg. Delay+35m Late |
| Station THIRUVANANTHAPURAM PETTAHTVP | Sch. Arrival14:40 | Actual Arrival14:40 | Avg. DelayOn Time |
| Station THIRUVANANTHAPURAM NORTHTVCN | Sch. Arrival14:48 | Actual Arrival15:30 | Avg. Delay+42m Late |
| Station KAZHAKUTTAMKZK | Sch. Arrival14:57 | Actual Arrival15:40 | Avg. Delay+43m Late |
| Station KANIYAPURAMKXP | Sch. Arrival15:02 | Actual Arrival15:02 | Avg. DelayOn Time |
| Station MURUKKAMPUZHAMQU | Sch. Arrival15:14 | Actual Arrival15:51 | Avg. Delay+37m Late |
| Station CHIRAYINKEEZHCRY | Sch. Arrival15:21 | Actual Arrival15:21 | Avg. DelayOn Time |
| Station KADAKAVURKVU | Sch. Arrival15:26 | Actual Arrival16:06 | Avg. Delay+40m Late |
| Station VARKALAVAK | Sch. Arrival15:49 | Actual Arrival16:19 | Avg. Delay+30m Late |
| Station EDAVAIEVA | Sch. Arrival15:55 | Actual Arrival15:55 | Avg. DelayOn Time |
| Station KAPPILKFI | Sch. Arrival16:00 | Actual Arrival16:00 | Avg. DelayOn Time |
| Station PARAVURPVU | Sch. Arrival16:14 | Actual Arrival16:42 | Avg. Delay+28m Late |
| Station MAYYANADMYY | Sch. Arrival16:21 | Actual Arrival16:21 | Avg. DelayOn Time |
| Station IRAVIPURAMIRP | Sch. Arrival16:27 | Actual Arrival16:27 | Avg. DelayOn Time |
| Station KOLLAM JNQLN | Sch. Arrival17:20 | Actual Arrival17:20 | Avg. DelayOn Time |
| Station PERINADPRND | Sch. Arrival17:35 | Actual Arrival17:41 | Avg. DelayOn Time / +6m |
| Station MUNROTURUTTUMQO | Sch. Arrival17:41 | Actual Arrival17:41 | Avg. DelayOn Time |
| Station SASTHANKOTTASTKT | Sch. Arrival17:47 | Actual Arrival17:56 | Avg. DelayOn Time / +9m |
| Station KARUNAGAPPALLIKPY | Sch. Arrival17:57 | Actual Arrival18:08 | Avg. DelayOn Time / +11m |
| Station OCHIRAOCR | Sch. Arrival18:07 | Actual Arrival18:18 | Avg. DelayOn Time / +11m |
| Station KAYANKULAM JNKYJ | Sch. Arrival18:16 | Actual Arrival18:27 | Avg. DelayOn Time / +11m |
| Station MAVELIKARAMVLK | Sch. Arrival18:26 | Actual Arrival18:40 | Avg. DelayOn Time / +14m |
| Station CHERIYANADCYN | Sch. Arrival18:32 | Actual Arrival18:32 | Avg. DelayOn Time |
| Station CHENGANNURCNGR | Sch. Arrival18:39 | Actual Arrival18:56 | Avg. Delay+17m Late |
| Station TIRUVALLATRVL | Sch. Arrival18:49 | Actual Arrival19:07 | Avg. Delay+18m Late |
| Station CHANGANASSERICGY | Sch. Arrival18:58 | Actual Arrival19:16 | Avg. Delay+18m Late |
| Station KOTTAYAMKTYM | Sch. Arrival19:45 | Actual Arrival19:45 | Avg. DelayOn Time |
Frequently Asked Questions
Q: Is the NCJ-KTYM EXP (16366) usually on time?
A: Based on recent performance data, the NCJ-KTYM EXP maintains a Excellent punctuality record, arriving at its destination an average of 0 minutes late.
Q: Where is train 16366 delayed the most?
A: Historical running data indicates that the NCJ-KTYM EXP faces its highest average delays at KAZHAKUTTAM.
Q: How can I check the past running status of the NCJ-KTYM EXP?
A: You can review the complete 7-day historical delay statistics, including average arrival and departure delays for all 34 stations, using the Train History tool above.