this post was submitted on 27 Aug 2026
318 points (98.2% liked)

memes

22489 readers
2364 users here now

Community rules

1. Be civilNo trolling, bigotry or other insulting / annoying behaviour

2. No politicsThis is non-politics community. For political memes please go to !politicalmemes@lemmy.world

3. No recent repostsCheck for reposts when posting a meme, you can only repost after 1 month

4. No botsNo bots without the express approval of the mods or the admins

5. No Spam/Ads/AI SlopNo advertisements or spam. This is an instance rule and the only way to live. We also consider AI slop to be spam in this community and is subject to removal.

A collection of some classic Lemmy memes for your enjoyment

Sister communities

founded 3 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] Lupus108@sh.itjust.works 17 points 2 days ago (5 children)

Iirc for the DB a train is considered on time when it's not later than 7 min on arrival. Which is a joke if you miss your following connection.

[–] python@lemmy.world 18 points 2 days ago (1 children)

A train that doesn't arrive at all is also not considered late.

[–] baguettefish@discuss.tchncs.de 7 points 2 days ago (1 children)

they abuse this mechanic to catch up on late trains, by stopping their trains a couple stops before the end stop and turning them around to drive the other direction, now not late anymore.

[–] Zwiebel@feddit.org 4 points 2 days ago

The Pofalla-turnaround, named after a politician

[–] FooBarrington@lemmy.world 1 points 1 day ago* (last edited 1 day ago)

I'm not sure I agree. The real world is never going to run perfectly, so some slack must be included (either by adding buffer time to schedules, or using the way you mention). Of course there are examples like Japan that have done a really good job at optimizing these systems, but you won't be able to successfully apply their approach to every country. Some locations require more work to achieve this, others require less.

Generally the closer you get to an "ideal" performance, the more costly every further improvement gets. If 7 min isn't reasonable, what number would be? Say we manage to shave off two minutes, at twice the cost of the current system. Is that really worth it?

The better approach is to include reasonable slack time in people's train schedules, while increasing frequencies so missing a connection doesn't result in hour-long wait times.

[–] surewhynotlem@lemmy.world 8 points 2 days ago (1 children)

I have this same argument with my spouse. If fifteen minutes late is "on time", then change the arrival time and just be on time.

[–] FishFace@piefed.social 1 points 2 days ago

Ah, the Ryanair approach. But unreliable arrival times are annoying for passengers and a drain. Sure, build in a small amount of slack, but a functioning train system should be able to get to 90% punctuality without adding 15 minutes of slack everywhere.

[–] mr_might44@lemmy.world 7 points 2 days ago

Luckily the next train you have to take is also late, so nothing really changes. A system so broken that it works "perfectly".

[–] FishFace@piefed.social 1 points 2 days ago (1 children)

Having been on a delayed German train, my connection actually waited so that everyone on my train connecting to it could catch it...

[–] idiomaddict@lemmy.world 1 points 2 days ago (1 children)

That obviously can’t be done regularly without impacting the whole system though. Meaning either that’s why they’re always late everywhere, or that doesn’t happen very frequently

[–] FishFace@piefed.social 1 points 1 day ago (1 children)

It can happen if delays are rare, yeah

[–] idiomaddict@lemmy.world 1 points 1 day ago

Yeah, unfortunately they’re not rare with DB :(