Forecast accuracy

Every hour we store forecasts for 121 Seoul areas and compare them with Seoul's actual values when that hour arrives. ‘Level match’ is the share of correct five-level predictions; ‘mean error’ is the score difference on a 0–100 scale.

Last 7 days

Method currently used for 24-hour-ahead forecasts (tomorrow/weekend scores in quiet routes): Baseline · current value carried 24 h ahead. A baseline or blend replaces the pattern forecast only when it beats it on both level match and mean error over the last 7 days (at least 3,000 comparisons).

The learned model is a formula over the current value, last week's same hour (averaged with the hours either side), the 4-week median, whether weekday↔weekend changes and whether it is night. Every hour, when the actual value arrives, it nudges the formula's weights by how wrong it was (slowly forgetting old results) and corrects each area's leftover bias. The ensemble remembers each baseline's recent error per area and leans on whichever has been right. The short-term blend removes each area's usual over/under-estimate from Seoul's official forecast and mixes it with the current value by their recent errors. The ensemble and learned model are used for tomorrow/weekend forecasts only when they beat every baseline and blend on both level match and mean error.

DateSeoul official forecast · 1 h aheadBaseline · current value carried 1 h aheadCrowdView short-term blend · 1 h ahead (current value + bias-corrected official forecast)Seoul official forecast · 3 h aheadBaseline · current value carried 3 h aheadCrowdView short-term blend · 3 h ahead (current value + bias-corrected official forecast)CrowdView pattern forecast · 24 h aheadBaseline · current value carried 24 h aheadBaseline · median of the same weekday and hour, last 4 weeksBaseline · same weekday and hour last weekCrowdView blend · current value if tomorrow is the same kind of day, last week's same hour when weekday↔weekend changesCrowdView ensemble · per area, more weight on the baselines that have been right latelyCrowdView learned model · corrects itself every hour from actual results
2026-11-0269% · 8.1pt · 2178 · ±1 94%84% · 4.2pt · 2178 · ±1 97%84% · 4.1pt · 2178 · ±1 97%70% · 7.7pt · 2178 · ±1 94%78% · 6.2pt · 2178 · ±1 94%78% · 5.7pt · 2178 · ±1 96%16% · 29.7pt · 2124 · ±1 69%71% · 9.7pt · 2178 · ±1 88%–89% · 2.4pt · 2178 · ±1 99%89% · 2.4pt · 2178 · ±1 99%83% · 4.2pt · 2178 · ±1 97%82% · 4.2pt · 2178 · ±1 98%
2026-11-0178% · 5.6pt · 2904 · ±1 97%90% · 2.6pt · 2904 · ±1 98%90% · 2.5pt · 2904 · ±1 98%76% · 6.6pt · 2904 · ±1 95%85% · 4.7pt · 2662 · ±1 95%85% · 4.3pt · 2662 · ±1 96%27% · 19.5pt · 2832 · ±1 90%75% · 8.5pt · 2904 · ±1 89%–93% · 2.1pt · 484 · ±1 98%67% · 12.5pt · 484 · ±1 83%92% · 2.6pt · 121 · ±1 97%98% · 0.5pt · 121 · ±1 99%
2026-10-3168% · 8.5pt · 2904––68% · 8.6pt · 2904––28% · 18.0pt · 283267% · 9.7pt · 2904–––––
2026-10-3064% · 9.5pt · 2904––64% · 9.5pt · 2904––29% · 18.4pt · 283280% · 4.9pt · 2904–––––
2026-10-2964% · 9.4pt · 2904––64% · 9.6pt · 2904––31% · 18.0pt · 283284% · 3.9pt · 2904–––––
2026-10-2864% · 9.3pt · 2904––65% · 9.3pt · 2904––32% · 18.7pt · 283283% · 4.4pt · 2904–––––
2026-10-2771% · 7.6pt · 2904––71% · 7.8pt · 2904––27% · 21.3pt · 283286% · 3.3pt · 2904–––––
2026-10-2665% · 9.0pt · 2904––64% · 9.7pt · 2904––17% · 30.7pt · 283272% · 8.5pt · 2904–––––
2026-10-2566% · 9.2pt · 2904––66% · 9.3pt · 2904––28% · 18.2pt · 283276% · 6.4pt · 2904–––––
2026-10-2460% · 10.7pt · 2890––61% · 10.8pt · 2892––25% · 18.9pt · 283269% · 8.6pt · 2904–––––
2026-10-2358% · 11.5pt · 2890––59% · 11.2pt · 2898––29% · 18.6pt · 283279% · 5.7pt · 2904–––––
2026-10-2262% · 10.0pt · 2876––64% · 9.9pt · 2892––29% · 18.9pt · 283279% · 5.5pt · 605–––––
2026-10-2161% · 11.0pt · 2880––61% · 10.9pt · 2898––29% · 19.9pt · 2832––––––
2026-10-2063% · 10.0pt · 2904––62% · 10.4pt · 2904––29% · 20.7pt · 2829––––––

CrowdView model vs. measured, by place (last 7 days)

Where live measurements exist (Seoul areas, theme park waits, airports), every hour we compare what the model alone would have said with the actual value, learn the gap by weekday/weekend × hour, and correct the forecast. Places of the same kind without live data get half of that correction.

PlaceError beforeError afterModel biasComparisons
愛寶樂園18.1pt14.8pt-10.0pt85
仁川機場 第一航廈19.1pt19.1pt-9.2pt163
仁川機場 第二航廈18.2pt18.2pt-11.5pt163
金浦機場 國內線15.6pt15.6pt-6.9pt77
濟州國際機場13.7pt13.7pt-4.1pt79
金海機場 國內線15.6pt15.6pt+15.1pt78
首爾世界煙火節11.5pt9.3pt+11.1pt67
韓國樂高樂園25.9pt20.2pt-12.9pt54
加勒比海灣水上樂園14.9pt11.0pt-13.2pt36
How it is calculated ›