2023–2025: running beyond the track season

Updated 10 Oct 2026

Running notebook · Running record · Personal bests · Race history

2015–2019 · 2020 · 2021 · 2022 · 2023–2025 · 2026

The years after the 2022 track season were uneven. Running continued: long outings in 2023, interval work in early 2024, the Orange County Marathon that May and more long runs in the autumn. The large recorded gap is 2025. This history is part of what I bring to the 2026 return, even though it was not one continuous middle-distance programme.

2023: longer outings and mixed work

Three recorded outings in May and June were around half-marathon distance:

Their titles are ordinary “Night Run” entries, with no race description. The distances and times describe those recordings; they are not official half-marathon results. The moving paces use exported distance rather than an assumed 21.0975 km. The table also gives exported elevation-gain estimates; the blank descriptions do not specify where the climbing occurred.

On 10 September, an entry titled “40 minutes in Hell” records 5×1000 m, 120 pull-ups, 120 push-ups and 60 dips. Its summary is 41:00 and 5 km. The description preserves a combined session, without giving the order of all the exercises, recoveries or individual run splits. The title’s forty minutes is not an independently timed 5 km result.

Shorter runs continued through November.

Early 2024: intervals were still there

I was still doing intervals in early 2024. These are the written sessions. The paces are for the work repetitions over their stated distances, excluding recoveries; a whole-recording moving pace would describe something different:

These manually entered workouts do not have route recordings that establish a local date. The table retains their UTC dates; the local day could be the preceding one. The 600 m workout explicitly includes jogging recoveries. Recovery for the other five formats is not supplied in their descriptions.

The two 3×1600 entries are an earlier reference for a distance now returning to the programme. Their unknown recoveries and effort prevent a direct comparison with the current LT progression. Likewise, the final 2:38.82 in a progressively faster six-by-eight-hundred set is one repetition, not a completed 2:40-average gate under today’s protocol.

April–May: longer night runs and Orange County

April’s route recordings show outings growing from roughly seven kilometres to twenty-five. The longer ones include 20.12 km in 1:30:09 on 19 April, about 4:29/km, 22.50 km in 1:50:35 on 23 April, about 4:55/km, and 24.64 km in 1:53:55 on 24 April, about 4:37/km. Those times and paces are moving summaries, with exported elevation-gain estimates around 58–72 m. These are local start dates, established from the recordings; the last appears as 25 April in the UTC export.

They give the marathon surrounding context. They do not recover a complete marathon plan or prove how much unrecorded training I did.

24 April — half-marathon training best

The 24 April night run also contains my fastest reported half-marathon effort: 1:36:57, about 4:36/km, worth 165 World Athletics points. The supplied split shows 1 m of elevation. This is a training split within the longer run; the full recording has 24.64 km, 1:53:55 moving time, 1:54:02 elapsed time and about 72 m recorded ascent. The split’s elevation display and the whole run’s ascent describe different portions of the activity.

The reported split replaces the earlier 1:37:39 same-pace comparison calculated from the whole recording. It belongs in the personal-best table, alongside its training context. The exported GPX preserves the route and timestamps, but does not retain the platform’s best-effort boundaries; the split time comes from the subsequently supplied activity detail.

5 May — Orange County Marathon

3:27:23 chip time, over the full 42.195 km, an average race pace of about 4:55/km, aged 20.

The official result records 3:31:23 gun time, bib 865, 313th overall, 281st among men and 38th in M20–24.

My activity records 42.78 GPS km, 3:27:36 moving time and 3:28:17 elapsed time. Those are recording summaries; the official chip time remains the race result. I do not correct the official distance from the GPS track or substitute the device’s time for the finish time.

Autumn 2024: more long running

The marathon was not the last long outing in the archive. Two autumn recordings are again around marathon distance, among a larger set of long runs:

The table’s elevation gains are device/export estimates, rather than surveyed ascent or a grade-adjusted pace.

Their routes establish these local Pacific dates. Several start on the evening before the export’s UTC date. Each is titled “Evening Run” or “Night Run,” with no description identifying an event or goal. I retain them as recorded long outings. A distance around 42 km does not supply a race name, an official result or a training purpose.

2025: the recorded gap

The archive contains one running upload in 2025: 2.22 km on 20 December. That is the limit of the recorded year, rather than proof that I never ran without uploading it. It agrees with my recollection that 2025 was the big gap.

The next chapter begins with occasional April 2026 efforts, then the more deliberate September return to track training.