Winter plan time wrong when entered during Summer Time
In October 2025 I created a journey departing at 1500 in January 2026. Journey is calculated and displayed as 1400.
Presumably this ie because today is GMT+1 and January is GMT, but this is neither intuitive nor sensible.
Expected behaviour: when I enter xx:xx on a date after an upcoming summer/winter time change, I expect this to plan as xx:xx and not xx+1:xx.
- Where does this happen?
- ABRP version number (found at bottom of settings menu)
Log in to comment and vote
Comments7
Anne O’Neamus
Dec 30, 2025
THIS ISSUE HAS BEEN ERRONEOUSLY MARKED AS “COMPLETED”. PLEASE RE-OPEN.
Anne O’Neamus
Dec 30, 2025
This problem persists. I am planning a journey in Europe for August 2026; my computer is set to UK time. I enter 0900 for a departure time and it shows in the planner as 1000.
Can you fix this long-standing issue please?
Anne O’Neamus
Oct 22, 2025
I don’t think you can solve a bug by waiting for summer time to end! It will still be a bug next year. And for any of us who plan well in advance.
Linda ABRP
Oct 22, 2025
If you still have the issue it’s winter time from this Sunday and then it will be solved. If it’s still an issue when we change back to summer time we have to look at it again.
John Abraham
Oct 12, 2025
I had the same problem.
Anne O’Neamus
Oct 10, 2025
What time zone is your computer in? Mine is in UK summer time.
I have replicated the issue in the ABRP app on iPad.
My devices are set to UK summer time:
I have also replicated the same error in Chrome on a Mac, with no previous planning data or account open. See how the waypoint entered as 1500 is displayed as 1400 on the plan:
Linda ABRP
Oct 10, 2025
Hi
I’m not able to reproduce that. If I add 11.00 as a departure time in January I get 11.00 as a departure time.