TFL Oyster Fare I don't understand

[pjanvil]

Yesturday I did a journey from Vauxhall [National Rail] at 19:13 to Feltham [National Rail] 19:49 with my TFL Oyster with railcard discount. I did not use the underground before it was a simple point to point direct journey. The correct fare between these two stations with railcard discount is £2.40 as show in the Single Fare finder however I was infact charged £2.45. I know this is only 5p difference and its not worth calling TFL for a 5p refund but I thought it raised it here as I can't think of any logical reasons as to why this would happen. I did the same journey on 2nd December and was charged £2.40 So this just baffles me why the difference. Anyone have any theories?

Potentially related but I notice brfares.com lists it as £2.45 but TFL Single Fare Finder lists it as £2.40 though it would still be strange it would have changed within the last 10 days.

 

[danm14]

Perhaps TFL have finally implemented the reduction in Railcard discount from 34% to 33.4% that was introduced in September?

 

[pjanvil]

I didn't know it had changed, is that on all rail fares? Yet single fare finder still says £2.40. Surely this would be picked up

Its a good theory since 3.7*.66 = 2.442 whereas 3.7*.666 = 2.4642 rounded down to the nearest 5p. Although I would still have thought they would have made such a change with the regular fare changes over just randomly changing one week to the other with no warning

 

[Joe Paxton]

Perhaps TFL have finally implemented the reduction in Railcard discount from 34% to 33.4% that was introduced in September?

I didn't know it had changed, is that on all rail fares? Yet single fare finder still says £2.40. Surely this would be picked up

It will be result of TfL's delayed implementation of the change in the Railcard discount.

See @MikeWh's latest news post on his Oyster Fares Central website...

The Rail Delivery Group made a change to the way discounted fares are calculated earlier this year. See https://www.bbc.co.uk/news/articles/cpw8j4d1v2do for more details. As a result of this some railcard single fares on Oyster now cost slightly more (5p, or possibly 10p) than they did at the last fares change in March.

The somewhat disturbing side effect of the recent cyber security incident is that the database that drives our fare finder, as well as TfL’s own single fare finder, has not yet been updated. TfL make a big thing of checking what your fare will be, so it’s disappointing to know that the official source is out of step with the live database.

So essentially TfL's own Single fare finder is now showing inaccurate fares for those with Railcard discounts loaded on Oyster, though the actual live system is correctly charging the updated fares. Rather less than ideal, to say the least.

 

[Wethebest838]

I have noticed the exact same. I have a railcard applied to my oyster and all my fares have gone up 5p.

 

[pjanvil]

Really bad it's just been suddenly implemented without any communication from TFL as to when it would be implemented and Single Fares not being updated to reflect it. It just leads to confusion for customers as no fare change by TFL was published or emailed. Obviously if nothing changed in September then people wouldn't expect it in middle of December.

 

[Tetchytyke]

I suspect it's another change that got delayed by TfL's spot of computer trouble. Bad that the single fare finder hasn't been updated though.

 

[talldave]

I suspect it's another change that got delayed by TfL's spot of computer trouble. Bad that the single fare finder hasn't been updated though.

Shortly after the embarrassment of TfLGo not being updated with Overground changes. It's ludicrous that a few experienced forumites from here could knock spots off the highly paid TfL staff who stagger from one shambles to another.