Enter your own climb observations to compare attempts without treating personal timing as an official game statistic.
Type your climb times in seconds and the planner reports the count, total, average, best attempt, and the gap to a personal target — with strict validation, checked 2026-10-03 against the game's documented stats. Mount Lonely has no official timer, so this is the honest way to answer "am I getting faster?"
Enter your own climb observations to compare attempts. This is a personal planning aid, not an official timer or leaderboard.
Four numbers, computed exactly as shown — no hidden weighting.
The average answers "what does a normal attempt cost me?". It is deliberately sensitive to outliers: one fall-heavy 50-minute climb drags it up, which is exactly the signal you want when deciding whether a route attempt was a fluke or a habit.
The best attempt is your realistic ceiling on a clean run. Planning against the best — not the average — is what climbers do when scheduling a serious push, and the target delta below turns it into a goal gap.
Set any personal target in seconds. A negative delta means you are already under target by that many seconds; a positive one is the time you still need to find. The target never leaves your browser — it is your goal, not a game rule.
Entries are split on spaces, commas, and semicolons; anything non-numeric or negative is rejected and listed back to you. A typo like "23m40" fails loudly instead of silently corrupting your average.
A sample session, computed by hand so you can verify the tool against the same numbers.
| Input (seconds) | As clock time | What it was | Contribution |
|---|---|---|---|
| 2610 | 43:30 | First climb of the evening, two falls at the mid-section | Total and average only |
| 2340 | 39:00 | Clean run, one checkpoint break | Total and average only |
| 2220 | 37:00 | Best run — no falls, new personal best | Total, average, and best |
| (target) 2400 | 40:00 | Personal goal for the week | Delta only: 2220 − 2400 = −180s |
Count 3, total 7,170s. Total time invested in the session — useful for deciding whether a third climb is realistic tonight.
Average 2,390s (39:50). The typical attempt cost. It sits just under a 40-minute session, close to the game's measured average session of 39.6 minutes — but that stat includes hangout time, so treat the similarity as coincidence, not a benchmark.
Best 2,220s, delta −180s. The climber is already 3 minutes under the 40:00 target — the right response is a harder target (say 36:00), not more runs at this one.
What the numbers can and cannot tell you, given what the game publishes (checked 2026-10-03).
Five logged attempts telling you the second half of the climb costs you more time than the first is genuine, personal evidence — the game publishes no route statistics that could contradict it.
A time from a fresh server (no checkpoint carry-over) is not comparable to a resumed climb. Log like with like: same start rule, same day, same update — the 94% positive rating does not make anyone else's route your route.
The game updated on October 6, 2026 and changes route flow without patch notes. After every update, log a fresh set of attempts before comparing against your old numbers, and check the update watch.
It counts the climb times you enter and reports the total, the average, the best (lowest) time, and — if you set a personal target — the gap between your best and that target. Everything runs locally in your browser; nothing is uploaded.
No. Mount Lonely has no published official timer or leaderboard, so this planner only summarizes the observations you type in. It is personal arithmetic for comparing your own attempts, not a game record.
Seconds, as plain numbers — 2340 means 39 minutes. The worked example below shows a full session converted both ways.
There is no official summit time. For scale: Rolimon's measured average sessions in Mount Lonely at 39.6 minutes (checked 2026-10-03), but that figure includes hanging out at the summit and fishing, not pure climb time. Your own logged attempts are the only honest benchmark.
Checkpoints hold progress inside one climb; leaving the server or a summit-reset event puts you back at the start. The studio has run summit resets on sibling Mount games before (Mount FREYA's Season 2 reset), so treat long-standing personal records as seasonal.
The planner only computes your own observations. Use these pages for the climb systems, guidance, and update signals around that result.
