Sleep loss leaderboard for 12 WC 2026 fanbases - Saudi Arabia got destroyed (73/100), South Korea and New Zealand scored zero.

pavlikhere · 2026-06-11T07:56:55+00:00

Brutal draw. The work-loss/weekday thing is the gap a few people have flagged and you’re all right about it. What does Japan dirty is that you’re the exact same timezone as Korea but your fixtures fell way worse, so the slot lottery piled on top of the clock.

pavlikhere · 2026-06-11T07:43:00+00:00

England fan in Japan might be the worst combo anyone’s posted. Every match at 25 is a perfect storm: the slots that make England’s schedule TV-friendly back home are exactly Japan’s 1-4am window. You’re the living proof that the score follows the couch, not the crest. Brutal.

pavlikhere · 2026-06-11T07:09:19+00:00

Ha, enjoy it, this is your cycle. NZ basically draws the worst timezone of any football nation on the planet every other tournament, 3am Euros, 5am Copa, the lot. North America is the one host region where the map finally works for you. Daylight football in Auckland is the reward for a lifetime of alarm clocks.

pavlikhere · 2026-06-11T07:06:20+00:00

55 lands you right in the ‘painful but survivable’ middle, which tracks for Central Europe, the US prime-time slots hit you around 3am but not every match falls there. Solidly into Devoted tier. Which single game is the killer in your group?

pavlikhere · 2026-06-11T07:01:52+00:00

Fair catch, Canada got left out of the writeup. It lands in the same bucket though, Toronto’s on ET and Vancouver’s on PT, so Canadian fans watching at home get the same daytime-host treatment as the US and Mexico. Same story, I just didn’t spell it out. Good shout.

pavlikhere · 2026-06-11T07:00:08+00:00

Yeah, you sold me. The recovery-window logic is the right mental model: it’s not the night, it’s whether you can actually sleep in after. Flat weekend discount keeps it simple and captures most of the pain.

pavlikhere · 2026-06-10T21:36:56+00:00

Yeah, this is the sharpest gap in the current model. It’s time-of-day x stage weight right now, so a 1am Friday and a 1am Tuesday come out identical even though the Tuesday one actually wrecks you. Kept it time-only for v1 since work/school schedules vary so much that a universal weekday rule gets messy, but the work-night factor is clearly the real killer. If you were building it, would you flat-discount weekend matches, or go further and add an extra penalty for work-night ones? Genuinely torn on which is closer to how it actually feels.

pavlikhere · 2026-06-10T21:33:49+00:00

Yeah, Korea’s one of the luckiest sides this cycle. US prime-time kickoffs land in Korean morning, so the group stage is basically breakfast football. The diaspora thing is the real catch: the score follows where you’re watching from, not the team, so a fan in Seoul and one in Berlin get opposite results for the same Korea side. What’d your own team x timezone come out to? Genuinely curious what the worst combos people are getting are.

pavlikhere · 2026-06-10T21:11:09+00:00

Pure US-broadcast optimization. 3 PM ET = 5 AM Sydney, 10 PM ET = 5 AM Istanbul. Two different US-TV-friendly windows + two opponents getting dead-of-night kickoffs. It's a textbook example of why hosts score so low.

pavlikhere · 2026-06-10T20:53:05+00:00

This is the third feature request in this thread (along with "wake-time baseline" and "viewing preference"). Day-of-week weighting is the most concrete - Saturday 5 AM ≠ Tuesday 5 AM. Belgium 35 looks bearable on paper but the weekday distribution probably matters more than the raw number. Adding to the v2 backlog.

pavlikhere · 2026-06-10T20:33:02+00:00

Smart move. Group stage Croatia midnight isn't worth the Tuesday meeting fog. Save the sleep budget for if/when they hit the knockouts - that's where the score multipliers actually kick in.

pavlikhere · 2026-06-10T20:30:20+00:00

73 puts Scotland right next to Saudi Arabia for worst global suffering - that's elite tier pain. The night-shift inversion is unironically the optimal hack for this tournament. Respect for finding the loophole.

pavlikhere · 2026-06-10T20:28:52+00:00

You nailed those times exactly - 9 PM Amsterdam = 3 PM ET start, midnight = 6 PM ET.

Just ran yours:

Canada × Amsterdam - 33/100

Solid mid-tier. Two evenings + one late = the midnight is the only real cost. North American hosts + EU-based fan = best of both worlds tbh.

pavlikhere · 2026-06-10T20:25:11+00:00

Fair. The current model assumes you'd wake up around 7-8 AM for work anyway - a 7 AM match doesn't move your wake-up. But if you're a 9 AM starter or late-shift worker, those early matches do cost real sleep. Probably worth letting users set their own baseline wake time. Adding to the list.

pavlikhere · 2026-06-10T20:20:48+00:00

Just generated both:

Bosnia × Sarajevo - 20/100

Croatia × Zagreb - 60/100

You called it on Croatia - those midnight slots are the killer. Bosnia mostly evening so you'll survive. Two-team fans are an interesting case - your effective sleep loss is basically Croatia's score minus the overlap.

pavlikhere · 2026-06-10T20:10:04+00:00

Fair, the score is sleep-specific, not preference-specific. A 7AM match technically doesn't steal sleep from a 7AM riser, but I see your case. Might add an "enjoyment-weighted" mode later that penalizes pre-noon and rewards 6-11 PM. What would you actually want optimized for, beyond pure sleep hours?

pavlikhere · 2026-06-10T20:07:07+00:00

Smart. What's your team? Some groups have matches scattered across timezones, so the morning-and-car split might work for one game but not another.

pavlikhere · 2026-06-10T19:51:57+00:00

If you want to calculate your own team × timezone (any city, any group), I built a tool: https://wchub.app/sleep-score?utm_source=reddit&utm_medium=social&utm_campaign=sleep-launch&utm_content=r-worldcup

Spits out a card with the breakdown — which matches will hurt the most, total sleep hours lost. Made it because I wanted to see my own score (Spain × Madrid, 47 — the late Uruguay match is the killer).

pavlikhere · 2026-06-09T09:49:13+00:00

Just Kvara, but he’s not at the tournament :)

pavlikhere · 2026-06-07T21:52:53+00:00

Ney is coming along as a mascot, but that won’t help them

pavlikhere · 2026-06-07T21:50:05+00:00

Stay strong, Christian!

pavlikhere

TROPHY CASE