Forum Replies Created
-
Posts
-
Hi,
Thanks for the reply! I didn’t think to note the error code, but based on the wording, I think it must have been “55 – Already Used”. The text of the error message on the screen was “Card already used”.
As for the journey history, yes I also wondered when the auto top up took place. The app didn’t say but the journey history reveals it happened on the attempted touch in:
Sunday, 21 May 2023 £14.70 daily total
21:45 – ???? Stockwell to [No touch-out] £4.20 £20.45
21:45 Touch in, Stockwell £4.20 £20.45
21:45 Auto top-up, Stockwell +£10.00 £24.65???? – 19:08 [No touch-in] to Stockwell £4.20 £14.65
16:15 – ???? Barking to [No touch-out] £4.20 £18.85
16:15 Touch in, Barking £4.20 £18.8512:34 – 13:13 Elephant & Castle [London Underground] to Barking £2.10 £23.05
13:13 Touch out, Barking +£2.10 £23.05
12:34 Touch in, Elephant & Castle [London Underground] £4.20 £20.95My best guess was that there was an open journey, even though the touch at Stockwell at 19:08 was out.
Hi Ben,
Is the second journey history entry really:
???? to WestFerry
Westferry doesn’t have barriers; normally validators can only start incomplete journeys, not end them.
If it doesn’t in fact say “Westferry to ????” (ie it’s not just a typo) then the exact expanded journey history from the web site for that entry would be useful, as this would imply something else unusual was going on.
I’ve emailed TfL to ask them to consider adding an OSI between City Thameslink and St. Paul’s on the basis that this will significantly ease connectivity from Elephant & Castle and London Bridge to the Central Line eastbound during the Northern Line closure from Kennington-Mortgate.
As it’s now shown as a dotted-line on the Tube Map, it seems likely that many people will use the link during this period; potentially being charged more than their pre-disrupted journey.
Ah of course, the NLE could then be depicted to cross the SWR line between Vauxhall and Waterloo, rather than between Queenstown Road and Vauxhall. I don’t think Geoff considered that in his video on the R&T map (I recall the suggestion to move Vauxhall down in the tube map, but the R&T map was implied to be insurmountable!).
I don’t see Nine Elms station getting much use anyway – if coming from the West, it’s quicker (and may also be cheaper) to use Vauxhall, and from the South similarly Vauxhall or Stockwell. Then again I think most people don’t care what fare they are charged, eg all the people at my work who get the train to Waterloo and then connect on the Jubilee line to London Bridge(!)
So I haven’t heard any rumours about Nine Elms to Vauxhall becoming be an OSI (which I can understand as it’s a slightly further walk, but it’s a shame as more SWR services call at Vauxhall), but Queenstown Road to BPS will be. This has the potential to be very useful to me as long as Battersea Power Station and Nine Elms are in Z1/2.
I see TfL’s recent press releases claims the stations will be in Zone 1, but per Geoff Marshall’s video of a few months ago, I don’t see how that could work map-wise. The only arrangement I can see that would work is putting them both in Z1/2:
(It would also be true to say the stations were Zone 1 stations if they were actually in 1/2, so I am remaining optimistic!).
Aha! You are absolutely right, it is exactly the one year anniversary of the card. (I think the clue should have been lack of an email, as they always send one of it’s for a journey!)
Still a bit surprising it doesn’t have an explicit name!
OK, I’ve now got a hunch as to what it may be for, as this is the only incomplete journey in my history, although I’m a little dubious as this was back in June which I’d have thought is far too long ago:
- Stratford International [HS1] to [No touch-out] £2.80
- [No touch-in] to Elephant & Castle [London Underground] £3.85
(Total cost = £6.65)
£6.65 – £5.00 = £1.65, the off-peak Z1-2 Railcard TfL-LU fare.
(Incidentally I filtered my history for journeys costing >=£5.00 as part of the search and I haven’t taken any since Jan 2020!).
My (monthly) statement is back! Email just received covering the entire month of June. Hopefully it stays that way.
I got a response back from the help desk as follows:
On escalating this to our technical team, there has been an issue identified, which there isn’t a fix for at this time, but they are working on it!
However, there is a workaround in the meantime. If you set-up your account to receive weekly statements, once you’ve received these then you can revert back to monthly. Strangely, setting statement delivery to a different timeframe can often solve the issue.
Lastly, after trying these steps, if we still don’t have any joy, unfortunately the only way to retrieve your journey history will be to manually download it until a fix can be created. This is very easy to do and only takes a few seconds.
I’ve tried setting mine to weekly so we’ll see if it sorts the issue. I did try turning it off and on to no effect some time back so I’m not that optimistic.
Me neither. I’ve been doing manual CSV exports (which is at least possible; it can be set to export the full 8 week date range in one go).
You can also buy a ticket from Enfield Lock to Cheshunt for the same price, available as an e-ticket, if you’d rather not visit a ticket office. The train does not have to call at Enfield Lock, only pass it; which in the case of GA services they all do.
Thanks for the report! Maybe fiddling with the setting in April (I turned the feature off and on) has caused the May one not to turn up. I’ll leave well alone and cross my fingers for June 🙂
Thanks for your thoughts. I know it’s a bit of an unusual idea. I didn’t imagine anyone would be looking for idiots like me, there again I did wonder if this is a well worn path for point-to-point modes due to the cable car, but the entrance and exit passageways are physically segregated there.
Two maximum fares on that line would be the same as two single journeys (I believe?) so I wouldn’t feel too disappointed there.
Once minimise travel is withdrawn I think I’ll give it a try. Although knowing my luck the timetables will be tweaked such that it is no longer possible by then! 🙂
Another option would be tapping out and then straight back in again at Clapham Junction (perhaps at the Grant Road entrance). Clapham Junction to Golders Green is Zone 2 with an OSI at Camden Road/Camden Town which might save you waiting for the OSI to time out.
The other thought that struck me is why you aren’t starting your journey at East Putney or Putney Bridge, which offer straightforward non-Zone 1 options.
I recall reading somewhere that Kennington will become a Boundary Zone 1/2 (can’t find where now; the best I can turn up is an uncited claim on the List of stations in London fare zone 2 Wikipedia page.
A Nine Elms to Vauxhall OSI is admittedly very niche; the walk means that Oval (and stations further south) will be equal or better sticking with Vauxhall LU and changing at Stockwell, and London Bridge (and stations further north) will be better with other options via Waterloo. But as someone who lives between Kennington and E&C and has tried every way conceivable of accessing SWR services from home (none of them particularly seamless), it would be a welcome addition for me 🙂
I’m not sure if you’re referring to the oyster app, or the oyster website… but on the website, when I went through this, I had to attempt to add another top up and on the last page of that the option presented itself to remove any unwanted cards (as a link under each card).
NB you can’t delete a card that’s associated with auto top up, so if you do have such a card you’ll need to go to auto top up settings and change the associated card first.
That makes sense, especially the stuff about accessing offline materials and staff being stretched across teams. I note multiple lines are often unavailable due to staff shortages especially on weekends, so FOI is a distant relation of essentialness by comparison. I guess I’d better cut some slack for a bit longer (much to the relief of the team who would otherwise receive my
frivolousnot critical requests!)TfL takes train frequency into account when deciding zonal coverage. Streatham has frequent northbound trains on Thameslink and Southern, whereas from Tooting you are stuck with the Wimbledon loop of the Thameslink line which is half hourly. This explains the different treatment. Note that Streatham to Southfields is Zone 3 only, so East Putney is the cut point.
TfL only need half an excuse to default to a Zone 1 route and in this case the Zone 1 competitor would be via Herne Hill and Victoria. You may well ask why TfL assume that a transfer at Victoria happened when no touches at the Victoria gateline took place, but there are lots of examples of TfL not distinguishing routes based on Out of Station Interchanges where they could do, especially where a pink reader exists to prove the cheaper route instead.
I also can’t speak to Google Pay, but Apple Pay is capable of authorising a transaction on public transport only even when the phone has no signal and is out of power. With Apple this is a feature called “Express Travel” and needs to be turned on; I wonder if there is something similar on Android?
In addition, even if you weren’t inspected by a revenue block, you wouldn’t escape the fact that your journeys wouldn’t be symmetrical. TfL has sophisticated reporting platforms to look for precisely the kind of anomaly you are suggesting and you would eventually find yourself being targeted. As others say there are likely to be other (legal) ways to save money if you describe your journey in more detail!
I do think TfL needs to decide what the dotted lines mean. “Walkable and has an OSI” is one definition, but equally it might be useful to someone to know a destination station is near another so they can use a more convenient route. For example, Battersea Park and Queenstown Road Battersea – there are no rational interchanges anyone would want to make but it could be useful for journey planning purposes to know of the proximity.
Interesting! Looks like the same applies for Bermondsey to Charing Cross NR, which I did a while back, but the NR1-T guess was correct there. Obviously solution would be to add a route from Southwark to Waterloo East at Z1 TfL-LU but I guess that could cause different problems.
