Originally posted by dragg:why cant the system do an auto refund on the cards of those they overcharged(the next time they travel)?
they can charge automatically but cant refund automatically one...
and they claim that the number of people affected is small? Sv161 got how many pax per day travelling between Woodlands and Hougang everyday? let say 5000pax daily x 21 days ?
does they mean that only the pax boarding Sv 161 at Innova JC and alighting at Blk 190C Punggol rd will be affected? What abt those boarding at Woodlands Interchange and alighting at Sengkang? they are still affected by the extra distance covered mah...
Originally posted by dragg:13 errors in fare system spottedLTA says errors rectified; refunds can be claimed
How to claim refunds- Visit www.transitlink.com.sg
- Call the Transitlink hotline (8am to 6pm, except public holidays) at: 1800-225-5663
- Go to Transitlink ticket offices
- Commuters must provide their name, IC number, contact number and ez-link or Nets Flashpay card number. They also must give the dates and times of the affected trips as well as the bus service numbers and boarding and alighting points
Commuters must give dates and times of affected tripes? if i take Sv161 twice daily , i must go submit my details 42 times to make the claims?
What are the 13 Svcs affected?
...
161
170
...
Originally posted by lemon1974:Commuters must give dates and times of affected tripes? if i take Sv161 twice daily , i must go submit my details 42 times to make the claims?
how do they tell if you are eligible for a refund?
they read your ez link card right? if that is the case i am sure they can do an auto refund.
LTA should make them do it this way. why inconvenience people for their mistake?
Originally posted by dragg:how do they tell if you are eligible for a refund?
they read your ez link card right? if that is the case i am sure they can do an auto refund.
LTA should make them do it this way. why inconvenience people for their mistake?
that the problem... they should set up some refund machines or use the top up machine (add in refund function) at the MRT station/interchange... then passengers just go tap and they can auotmatically refund if there is any error in deduction (they can program in those trips affecting by the overcharging)... but then this is LTA.....
Originally posted by brotherchen1982:What are the 13 Svcs affected?
...
161
170
...
56 67 88 105 153 161 170 173 176 178 961 963 963E 963R
Sv 145 also kena. 2x in fact.
Originally posted by lemon1974:that the problem... they should set up some refund machines or use the top up machine (add in refund function) at the MRT station/interchange... then passengers just go tap and they can auotmatically refund if there is any error in deduction (they can program in those trips affecting by the overcharging)... but then this is LTA.....
the best way is to auto refund during your next travel. you tap your card and the system refund you.
no hassle.
Originally posted by sbst275:Sv 145 also kena. 2x in fact.
TODAY published 6 only.. any idea wat's the rest?
Originally posted by dragg:the best way is to auto refund during your next travel. you tap your card and the system refund you.
no hassle.
they will give you all sort of excuses lah esp when you travel, they say that the computer/sensor cant handle or what lah and if want to auto refund will have to take some time for the card reader to check and respond or whatever excuses....... alternative is that they refund during auto top up or manual top up of the ezylink card..
Actually, I think they discovered and corrected the errors long ago. The distance from trellis towers to TPY mrt has always been tabulated as 0.6km as far as I know even though the fare boards state 0.9km. The fare calculator used 0.6 km too.
Originally posted by lemon1974:they will give you all sort of excuses lah esp when you travel, they say that the computer/sensor cant handle or what lah and if want to auto refund will have to take some time for the card reader to check and respond or whatever excuses....... alternative is that they refund during auto top up or manual top up of the ezylink card..
i believe many will not go for a refund as the time and trouble will be more than the amount itself. its only a small amount after all (sounds familiar?)
just wondering... how does 170 goes to Larkin nowadays? via the Stulang that side or the old way?
Originally posted by service_238:
TODAY published 6 only.. any idea wat's the rest?
I've no idea cos some e online calculator side might not be updated as yet.
For Sv 145 it's 2 consecutive bus stop. Opp Bras Basah Cplx > City Hall MRT > High Court.
in any case, lots of mini LTA/ PTC/ PTO joint notice at up at e bus stops.
today's ST has the full detail.
In any case I believe there's really more to come.
e.g. Sv 79, 246, 249 from Jln Boon Lay (Opp CIS) to BNL Int is 2.0km! Even Sv 30, 154 from Boon Lay Way > BNL Int is 1.1km nia.
Then Sv 170X from Woodlands Rd (Opp Chartered Semiconductor Ind) to WDL CIQ is 1.2km, yet from Woodlands Centre Rd (Opp Blk 1A) to WDL CIQ is 1.1km!
Back is 1.3km and 1.1km respectively.
Error spotted for some NEL connection
wrong post
Someone correct/confirm with me on this:
i was on SBS9494A sv196 yesterday evening, i noticed that the reader was not locked and the BC was manually updated the "distance" manually.
As the bus still has the old farecard machine, when the BC up a farestage, ie from 23 - 24, the distance jumped accordingly on the EZ reader.
So am i right to say that the behind the DRF,
it is still the farestage mechanism that is doing the calculation?!
The EZ reader has been "updated" to not show the fare stage but distance travelled?!
So what the minister said about only 1/3 paying higher fares would not be correct as the fare increase has been factored into the fare stage calculation
ACx
Originally posted by Acx1688:Someone correct/confirm with me on this:
i was on SBS9494A sv196 yesterday evening, i noticed that the reader was not locked and the BC was manually updated the "distance" manually.
As the bus still has the old farecard machine, when the BC up a farestage, ie from 23 - 24, the distance jumped accordingly on the EZ reader.
So am i right to say that the behind the DRF,
it is still the farestage mechanism that is doing the calculation?!
The EZ reader has been "updated" to not show the fare stage but distance travelled?!
So what the minister said about only 1/3 paying higher fares would not be correct as the fare increase has been factored into the fare stage calculation
ACx
cos the old validator can't display e new km based markings.
Tat's why for now, BCs are given e slider charts.
Originally posted by sbst275:
cos the old validator can't display e new km based markings.Tat's why for now, BCs are given e slider charts.
correct! but my point is the distance fare "technology" derived from the fare stage as its support technology?!
Ur fare increase or decrease after distance based fare?
Originally posted by Acx1688:correct! but my point is the distance fare "technology" derived from the fare stage as its support technology?!
actually isn't fare stage came from distance i.e. 1 fare stage ~ 0.8km less cases like Sv 155.
For Sv 155, I guess SBS took it as if 155 proceeds straight along Aljunied Rd.
Originally posted by -StarDust-:Ur fare increase or decrease after distance based fare?
My fare has increased lah...
I used to be able to take sv10 tfr to sv196 reach my place $0.88
Now its $1.09
Originally posted by sbst275:
actually isn't fare stage came from distance i.e. 1 fare stage ~ 0.8km less cases like Sv 155.For Sv 155, I guess SBS took it as if 155 proceeds straight along Aljunied Rd.
True but distance travelled is not correctly reflected...