Right, how does this writing thing work? I’ve missed a few race reports; the last one I wrote was for the Town Tree Trail, back in May. Since then I’ve ran the Crewkerne 10k (abandoned draft blog post), Piddle Wood Plod, the Quantock Beast (another abandoned post), and the Pawlett Plod. As a quick summary:

• Crewkerne 10k: pretty good
• Piddle Wood Plod: meh
• Quantock Beast: good
• Pawlett Plod: felt not great, but pretty good actually

This race was the first part of my planned summer of speed, aiming to improve my 10k PB, and ideally set a sub-40 time. Unfortunately, after a good first half of my eight-week training ahead of this race, the wheels fell off somewhat, and I’ve barely done anything over the last four weeks. So, coming into this race, I didn’t really know what I’d be able to do. Sub-40 wasn’t going to be in the picture, but maybe I could still get a new 10k PB? To review, my planned targets are:

• Gold: 39:59 (sub-40)
• Silver: 41:23 (distance PB)
• Bronze: 42:05 (race PB)

Pre-race

I chose the Wessex 10k because it described itself as “a fairly flat mainly road”. I had a look at some of the Strava traces from last year, and decided that the hill looked small enough that this could still be considered a decent PB route. The date also worked out quite nicely, and I seem to recall that it was priced relatively reasonably too. (Just checked, £16.) What I failed to notice until a couple of weeks before the race was that it was a 19:00 start time on the Saturday; I had spotted it was on a Saturday, but not that it was an evening race. This threw me off a little: I have it in my head that I don’t race so well in the evening, and I was just annoyed at not having noticed.

In the end though, being in the evening worked quite well; it meant that we still had all of the day on Saturday as a family, and would have on Sunday too (though I’m sat here writing this, so go figure.) I left just after five, which gave me lots of time to get to Somerton and then bimble around for plenty of time before the start. I didn’t have to worry about registration, as the race number had been sent out through the post. Just after half six I started my warm-up; I had intended to go for a longer warm-up, as I generally find them more effective, but it ended up being just over a mile, which is about my normal.

At around five to seven, we started to gather at the start line, and I got chatting to another chap on the start line, but it quickly became apparent that I wouldn’t be using him as a pacer; he was aiming for around 38 minutes! In the inaugural race in 2018, only six runners went sub-40, so I was half aware that there might not be too many ahead of me, and so lined up in the front row.

The race

I almost managed to not go off too fast. As I wasn’t too sure what time I would be capable of, I opted to aim for 41 minutes, and see what happened. That would equate to a time of 4:06 per kilometre. After the initial rush, I settled down to 3:55 for the first kilometre, which was pretty flat, heading out of the sports club, along the main road, and then hooked right onto the back-roads. It was obvious that there were more quick runners than in 2018, but that was to be expected for the second year of an event.

Shortly after the end of the first kilometre, we started to drop down the hill; this was the same one that we would return up later. And, well, it looked worse than I had hoped. In place of the gentle slope I had been expecting, or at least hoping for, was a genuine hill. Okay, no worries, I could make time up heading down the hill, and just see how well I could hold on up the hill in the second half. Downhill-assisted, the second kilometre clocked in at 3:45, and the third, still with a modest descent, was 3:58, leaving me 40 seconds up on an even-split 41:00 time. But of course, it wouldn’t be an even-split race, and I was aware that I could lose close to that same 40 seconds on the hill alone.

Any hopes of managing to make up more time, or at least hold steady were immediately dashed, as at the 3 km marker, we started on the rough stuff. A dusty, rocky, pot-holed farm track. This wasn’t part of my plan, and brought back memories of the Bridgwater 10k way back in 2014, when I destroyed myself chasing a PB on a course with a farm-track in the middle. Thankfully, I’m a bit more experienced now, but I was still losing time against my 41 minute target. Partly, this was probably just lack of fitness due to my reduced training lately, but the terrain clearly won’t have helped. Through the fourth and fifth kilometres, I clocked 4:13 and 4:19, taking me through five kilometres in 20:11; still theoretically 19 seconds up on my target, but in reality, starting to really struggle.

I’d developed an odd pain high on my chest; either my lung or a muscular pain, I couldn’t tell which. It was annoying without being debilitating, but I was very much hoping that it didn’t get worse. Just after the halfway stage, we had the only drinks station on the course, from which I took a quick swig, and then we returned to the road. I tried to get my legs turning over a bit quicker on the better surface, but to little avail; the next three kilometres came in at 4:36, 4:30, 4:30.

Then the hill hit. It actually was not so bad as I had worried; I managed to run up the whole thing. That shouldn’t have been an achievement, but I’ve really struggled with hills this year for some reason, so I was pretty proud of it. The hill last for pretty much a whole kilometre, starting just before the 8 km marker in actual fact, and correspondingly, finished just before 9 km. It was by far my slowest kilometre of the race, a 4:54, but Strava’s grade-adjusted pace (GAP) was 4:25, which was quicker than my GAP for kilometres six and seven.

Over the top of the hill, and I knew I just had a kilometre to go. I willed my body to run faster, damn it! I managed it. Not consistently, but effectively; I oscillated between a 3:50 and 4:20 pace, and despite telling myself that I was now in energy-saving mode ahead of another race on Wednesday, I engaged in a sprint-finish when the runner behind me tried to get past. Helped by his push at the end, I ducked in just under 42 and a half minutes, officially posting a time of 42:28.

Post-race

After getting my breath back from my quick finish, I grabbed a cup of water, and then had another chat with the chap I’d been taking to before the race. After a quick analysis of each of our races, I commented that I noticed he was from 26.2 RRC (the best running club in Surbiton), made famous by Danny Norman on the With Me Now podcast. It turned out that I’d been chatting to none other than Chauffeur Ramek – what a small world it is! After some more parkrun chat, we headed off our different ways.

The medal was really nice; probably the second biggest in my collection, though I don’t really do the type of races that give big medals. (Because I’m cheap.) (Because I race so much that if I did expensive races, we would miss our mortgage payments.)

How about my time? It ranks as my fourth best 10k time; just behind my Pawlett Plod time from a few weeks ago:

• 42:06, Chard Flyer, January 2017
• 42:19, Battle of Sedgemoor 10k, August 2015
• 42:23, Pawlett Plod, July 2019
• 42:28, Wessex 10k, August 2019
• 43:18, Round the Tor 10k, May 2016

That two of my quickest ever 10k times have come this year is encouraging. That my two overall quickest times are two and four years old respectively is disappointing. It’s another eight weeks now until the Taunton 10k, and if I want to get a new PB, then I simply have to put the training in. No excuses.

• Did I enjoy this race? If I’m honest, not really. But that was no fault of the race, or the course. Sure, I’d have liked the hill to be flatter, and the rough track to be smoother. In reality though, I just wasn’t fit enough to run this race as I wanted.
• Would I do this race again? Probably not, no. I signed up hoping that it was a good PB course, and it wasn’t really. If it was a Somerset Series race, I’d do it and enjoy it well enough, I’m sure. But as a standalone race, it probably won’t be for me again. Never say never though, I guess.
• What’s next? The Haselbury Trail 10k on Wednesday.