The trust page

How we reach a verdict

Every verdict on this site answers one question: will the view be worth the money and the day? Not whether the weather is "nice". Not whether it's safe to travel. Whether standing on that platform, today, is worth the fare and the queue. This page is the public version of our decision engine's specification — the actual thresholds, not a summary of them. If a verdict ever looks wrong, this is what to check it against.

What each verdict means

The forecast supports a worthwhile scenic visit. Check the date and confidence.

Workable, but time it — check the best window below.

Save your money for a better day.

Scores shown are illustrative, not fixed examples.

What the forecast can tell us

Cloud base does not tell us cloud top

Cloud cover alone cannot tell you whether a particular viewpoint has a useful panorama. The cloud's altitude and depth matter too. Our input includes a forecast base, but no measured cloud top. A base below the summit can leave the summit inside cloud or above it.

Example: top 2,400 mExample: top 3,600 mSame summit: 3,000 mSame base: 2,000 m
Invented examples: identical summit and base heights, different cloud tops. Neither illustrated top is supplied by our forecast feed.

We give no extra points simply because a summit is farther above the cloud base. When substantial low or mid-level cloud leaves its position unresolved, we keep the verdict at MAYBE or below and cap confidence. A base comfortably above the viewpoint provides limited support for views beneath cloud, but cannot establish that distant peaks are visible.

Clearer forecasts can still earn PEAK. Modelled horizontal visibility, rain, snow, wind, forecast age and transport availability also affect the result. The score is a provisional decision aid, not a probability of sunshine or an observed view.

Stage by stage

What goes into a verdict

The score behind every verdict starts from whether there's a view at all, then subtracts for everything that would spoil the day. View quality dominates, because the view is what you're actually buying.

View quality comes first

We combine low and mid-level cloud cover with the forecast base altitude. With substantial cloud and no basis for placing it above the viewpoint, the cloud score stays near 50 before other penalties; height above its base adds no reward. Small changes in cloud cover blend gradually into this uncertainty treatment. Horizontal visibility subtracts further, from no penalty at 20 km or more to a strong penalty below 2 km. It comes from a secondary model and cannot establish a cloud top. Strong visibility therefore does not cancel an uncertain cloud position.

Then precipitation

Rain and snow subtract from there. Any meaningful rain — 0.5 mm/h or more — costs real points; 2.0 mm/h or more is a heavy penalty, because rain ruins both the view and the visit. Snowfall of 1 cm/h or more gets its own penalty on top: it's beautiful, and it still hides the panorama you paid for.

And wind — counted twice, for two different reasons

Wind appears in the score twice, deliberately, because it means two different things and collapsing them into one number would be wrong in both directions.

The first is operational risk: how much wind it takes to stop the machinery. An aerial system stops for wind long before a ground-based one does, so we track gusts against different thresholds by transport type:

Wind gust thresholds by transport type
TransportModerate riskHigh risk
Cable car, gondola, aerial tramway≥ 60 km/h≥ 80 km/h
Cog railway, funicular, sightseeing train≥ 90 km/h≥ 110 km/h

High operational risk caps the verdict at MAYBE — never SKIP on wind risk alone, because we don't actually know the operator has stopped running, only that they might. Claiming a closure we haven't verified would be exactly the kind of guess this site exists to avoid.

The second is comfort, and it's deliberately mild: people accept being cold and blown around at altitude — they're there for the view. Gusts of 60 km/h or more, or an apparent temperature at or below −15 °C, cost a few points. Not a verdict, just an honest nudge to dress for it.

The gate nothing else overrides

Operations are a hard gate

None of the above matters if the mountain is closed. A closed cable car, cog railway or funicular can never produce a PEAK — however good the sky looks, if you can't get up there, there's no view to have.

Here's the part we'd rather not have to admit, but it's the honest state of things: we currently know an operator's published schedule, not whether they're actually running right now. Outside opening hours, we can say "closed" with confidence. Inside opening hours, our best honest answer is "unconfirmed" — and that deliberately lowers our confidence rating, rather than letting the page quietly assume the lift is running. Live operator status is on our roadmap. Scraping operator websites to fake it in the meantime is not something we're willing to do.

Not just "today"

How we pick the best window

A verdict is for a specific window, not a vague "today". We only ever consider hours a visitor could actually be up there: the attraction's own published service hours for that date, narrowed further to between sunrise and sunset. A beautiful forecast at 3 a.m. is not a reason to go anywhere.

Those hours are the operator's, not a rule of ours, so they differ by mountain and by season — Harder Kulm's funicular runs into the evening in high summer, and a winter timetable closes earlier than the same mountain's summer one. We used to apply one fixed 08:00–17:00 band to every attraction, which both hid genuinely good evening hours and recommended hours that were already shut. That band now only applies to an attraction whose schedule we don't hold.

Within those hours, we look for the best contiguous 3-hour block — shorter only when a continuous run of usable forecast hours is shorter. We compare the verdict first, then the average score: a clear PEAK window wins over a higher-scoring window capped at MAYBE by uncertain cloud or wind. We score the day on the chosen window's average, not the day's average. If the morning is glorious and the afternoon clouds over, averaging the two would call the day mediocre, when the honest advice is: go in the morning. We'd rather tell you exactly when to go than hand you a number that blurs a great window into a forgettable one.

No black box

The thresholds, in the open

The final score, 0 to 100, becomes a verdict by two lines:

  • score ≥ 75 → PEAK
  • score ≥ 45 → MAYBE
  • otherwise → SKIP

PEAK is set deliberately high. A PEAK is a promise — go, spend the money, spend the day — and a PEAK that disappoints costs us far more trust than a cautious MAYBE ever earns. We'd rather undersell a good day than oversell a mediocre one.

Two hard rules override the number entirely, and both are described above: operations closed or scheduled-closed forces SKIP, score 0, regardless of the weather; high wind operational risk caps the verdict at MAYBE, whatever the score says.

How much to trust the number

Confidence

Every verdict also carries a confidence rating — high, medium or low — separate from the score itself. It starts at high and only ever gets downgraded, never upgraded, by the single worst thing that applies:

  • A forecast lead time of 2–3 days out, or 4 or more days out for a bigger downgrade — forecasts get less reliable the further out they are.
  • Weather data older than 90 minutes, or older than 3 hours for a bigger downgrade.
  • An operating status we can't confirm live — see "Operations" above.
  • Substantial low or mid cloud whose position we cannot resolve from the forecast base alone — we will not guess a cloud top.
  • Visibility doing most of the work in a low score — it's our weakest input, and leaning on it should be visible.
  • A score sitting within 4 points of a verdict boundary. A 74 and a 76 are the same forecast, and pretending a line at exactly 75 is more precise than that would be false confidence.

Feature, not apology

What we don't know yet

This is v1, and the thresholds above are informed judgement, not yet empirically calibrated — we've set them where the physics and the stakes argue they should sit, not where a dataset told us to. Being honest about that means being honest about a few specific gaps:

  • We know an operator's published schedule, not live running status. Real-time confirmation is on the roadmap.
  • We don't yet check any webcam against our own call. If and when we do, frames will only ever come from cameras we have explicit permission to use — never scraped or re-hosted without it.
  • We run one weather model. When we add a second, disagreement between them becomes a confidence signal in its own right — right now we have no way to know when our one source is simply wrong.

We record every forecast we see and every verdict we issue, on a fixed schedule, starting from launch. That's not for later marketing — it's so that, in time, we can compare what we predicted against what actually happened and publish the result: how often a PEAK was actually worth it. As far as we know, nobody else in this space publishes their reasoning, and nobody publishes their accuracy either. We intend to, once there's enough data to say something honest.

Who the number answers to

Independence

The part of this system that decides PEAK, MAYBE or SKIP cannot see affiliate data. It has no import path to partner IDs, pricing or booking links — that's not a policy, it's enforced by an automated test that fails the build if it's ever violated. Offers are attached to the page only after the verdict already exists, by a separate part of the codebase, and they never reorder or influence which mountain we recommend.

That matters because a SKIP verdict costs us money — nobody books a ticket off a page that just told them to save their francs and try another day — and we publish it anyway. If we were optimising for revenue, every day would be a MAYBE.