 |
|
Timeline of all Site Edits
Filters:
Page# 1 Timeline Updates
Entry# 5216806 Blog Entry# 5447839
by: SAPTARSHI^~ 26387 Conf TLs 5 Void TLs
Train Name: Sealdah - Canning Local
Departure Days: Daily
Classes: II
Type: Klkt
First Departure:
Last Departure:
SDAH 09:10; PQS 09:12 09:13; BLN 09:17 09:18; DHK 09:19 09:20; JDP 09:22 09:23; BGJT 09:24 09:25; NGRI 09:27 09:28; GIA 09:29 09:30; NRPR 09:31 09:32; SPR 09:39 09:40; BDYP 09:45 09:46; KLKR 09:48 09:49; CHT 09:52 09:53; PLF 09:55 09:56; GQD 09:57 09:58; GOF 10:01 10:02; BTPG 10:05 10:06; TLX 10:10 10:11; MATL 10:13 10:14; CG 10:26 ;
TT Source: Manual Update/Copy-Paste
Departure Days: Daily
Classes: II
Type: Klkt
First Departure:
Last Departure:
SDAH 09:10; PQS 09:12 09:13; BLN 09:17 09:18; DHK 09:19 09:20; JDP 09:22 09:23; BGJT 09:24 09:25; NGRI 09:27 09:28; GIA 09:29 09:30; NRPR 09:31 09:32; SPR 09:39 09:40; BDYP 09:45 09:46; KLKR 09:48 09:49; CHT 09:52 09:53; PLF 09:55 09:56; GQD 09:57 09:58; GOF 10:01 10:02; BTPG 10:05 10:06; TLX 10:10 10:11; MATL 10:13 10:14; CG 10:26 ;
TT Source: Manual Update/Copy-Paste
Train Name: Sealdah - Canning Local
Departure Days: Daily
Classes: II
Type: Klkt
First Departure:
Last Departure:
SDAH 09:10; PQS09:13 09:14; BLN 09:19 09:20; DHK 09:21 09:22; JDP 09:23 09:24; BGJT 09:25 09:26; NGRI 09:28 09:29; GIA 09:30 09:31; NRPR 09:32 09:33; SPR 09:40 09:41; BDYP 09:45 09:46; KLKR 09:48 09:49; CHT 09:52 09:53; PLF 09:55 09:56; GQD 09:57 09:58; GOF 10:01 10:02; BTPG 10:05 10:06; TLX 10:10 10:11; CG 10:25 ;
TT Source: Manual Update/Copy-Paste
Departure Days: Daily
Classes: II
Type: Klkt
First Departure:
Last Departure:
SDAH 09:10; PQS
TT Source: Manual Update/Copy-Paste
7 Posts
Sure, also FM should have noted the time when they're taking action, last run was over and revised TT was already in force.
When u updated , last run was not over n even when I attended , new TT was not operational. New timing from 15/8/2022
Moreover attended after verifying NTES TT.
So in what sense FMs needs to note the time? Handling was followed proper way n in time. 15/8/2022 is yet to start.
Moreover attended after verifying NTES TT.
So in what sense FMs needs to note the time? Handling was followed proper way n in time. 15/8/2022 is yet to start.
10:25 IST: Last run was over
16:21 IST: fixit given citing correction needed.
17:56 IST: FM re-confirms without any corrections made
Respectfully, I expect FMs should prefer asking for a proof or notice before...
more...
16:21 IST: fixit given citing correction needed.
17:56 IST: FM re-confirms without any corrections made
Respectfully, I expect FMs should prefer asking for a proof or notice before...
more...
1 -- Last run is over but still mentioned date is 15/8/2022 for new timings which can not be denied being valid date as per the notification.
2 -- Fixit issued after verifying from NTES which is normally followed for locals/ unreserved trains n that was correct action as both the TT didn't match.
3 -- After image in Bengali language posted by you regarding the same , it was asked about the content therein with date specifically.
Then...
more...
2 -- Fixit issued after verifying from NTES which is normally followed for locals/ unreserved trains n that was correct action as both the TT didn't match.
3 -- After image in Bengali language posted by you regarding the same , it was asked about the content therein with date specifically.
Then...
more...
From next time you will be asked for update details in case reporting happens.
Yes, simple asking doesn't harm n avoid further confusion/misunderstanding.
Yes, simple asking doesn't harm n avoid further confusion/misunderstanding.
Page# 1 Timeline Updates
Scroll to Top