SFBayDuck
Footballguy
10K Race Report
I've only run one 10K, a turkey trot back in 2015. I ran a 52:04, but I was at least in decent shape at the time having run 4 ultras that year, including a 50M in October. So I really had no idea what to put down as my estimated time for this. Because I've been on the roads I've been running a lot more miles in the 10s than I usually do on the trails, but I still rarely have a mile quicker than 9:30 or so, and that's not easy. So I, somewhat jokingly, just estimated 1 second less than @BassNBrew for each of the distances.
But I haven't really been "training", just trying to run a few times a week for stress relief and to not lose all fitness. My diet has been crap (I'm a bit of a stress eater with a default for comfort foods), so I'm 25+ pounds over where I was for States a few years back. I did actually look up some 5K workouts last month, and had my watch programmed for some intervals when I hurt myself getting dressed for that run.
That led to taking 13 days completely off last month, and only running 5 of the last 11 days of the month as I eased back into it. And I obviously missed the 5K. But the last couple of weeks I've been a little more consistent, although I never did an actual workout - just a few strides here and there.
This morning I was feeling ok, I hadn't run yesterday, so after a shorter walk with the pup I decided to give the 10K a go. It had started to rain at the end of our walk, so it was probably as cool as it was going to get over the next 5 days. I figured I'd just start out at a pace I thought I might be able to hold, and see how it went - if I screwed up I'd just pull the plug and try again Saturday. I obviously don't have any examples of pace, and as I started I realized my Fenix HR monitor wasn't working - it was showing in the 120s when I knew I was at least in the high 150s. So I just went by my breathing - from the few tempo runs I've run over the years I know there's a hard breathing pattern I can maintain for awhile, and if I go above that I start to almost gasp a bit with each breath. So the plan was just to try and stay as close to that line as possible.
First mile - 9:05. Felt ok, nothing hurt, effort level seemed manageable. Let's pick it up a bit.
Second mile - 8:45. Still alright, but now it's hard. Had my first thought of pulling the plug. Nah, let's at least get to 5K and see where we're at
Third mile - 8:29. Ok, this kind of sucks now. Where's that hill I can power hike? Is there an aid station coming? Can a bear get in my way so I can stop?
Fourth mile - 8:19. A slight downhill here so the pace picks up, but about the 3 1/2 mile mark I started having serious doubts about holding the pace. But I also started thinking that it's going to suck just as much if I try this on Saturday, and I don't want to do this again. So #EmbraceTheSuck
Fifth mile - 8:26. Slipping into that gasping breathing pattern a couple of times, so had to ease back just a bit. Listening to a podcast and realize I haven't heard anything that's been said for about 15 minutes.
Sixth mile - 8:20. "It never always gets worse" is one of my favorite mantras in ultras. This mantra does not apply to 10Ks.
Final .22 - 1:44 for a 7:47 pace. I really had no idea when to break into the "finishing kick", if you can call a 7:47 pace that. But as I hit 6.22 and hit stop on the watch I doubled over gasping, so I think I did it right. Then again I didn't puke, so maybe not.
53:12 for an 8:33 overall pace.
It's pretty embarrassing how hard that was for me, when for almost everyone else in here you're running your easy runs faster than that. But I feel good about the effort I put out there today.
Thanks all for including me, and letting my slow, ultra ### muck up this thread of you real runners every once in awhile.
I've only run one 10K, a turkey trot back in 2015. I ran a 52:04, but I was at least in decent shape at the time having run 4 ultras that year, including a 50M in October. So I really had no idea what to put down as my estimated time for this. Because I've been on the roads I've been running a lot more miles in the 10s than I usually do on the trails, but I still rarely have a mile quicker than 9:30 or so, and that's not easy. So I, somewhat jokingly, just estimated 1 second less than @BassNBrew for each of the distances.
But I haven't really been "training", just trying to run a few times a week for stress relief and to not lose all fitness. My diet has been crap (I'm a bit of a stress eater with a default for comfort foods), so I'm 25+ pounds over where I was for States a few years back. I did actually look up some 5K workouts last month, and had my watch programmed for some intervals when I hurt myself getting dressed for that run.
That led to taking 13 days completely off last month, and only running 5 of the last 11 days of the month as I eased back into it. And I obviously missed the 5K. But the last couple of weeks I've been a little more consistent, although I never did an actual workout - just a few strides here and there. This morning I was feeling ok, I hadn't run yesterday, so after a shorter walk with the pup I decided to give the 10K a go. It had started to rain at the end of our walk, so it was probably as cool as it was going to get over the next 5 days. I figured I'd just start out at a pace I thought I might be able to hold, and see how it went - if I screwed up I'd just pull the plug and try again Saturday. I obviously don't have any examples of pace, and as I started I realized my Fenix HR monitor wasn't working - it was showing in the 120s when I knew I was at least in the high 150s. So I just went by my breathing - from the few tempo runs I've run over the years I know there's a hard breathing pattern I can maintain for awhile, and if I go above that I start to almost gasp a bit with each breath. So the plan was just to try and stay as close to that line as possible.
First mile - 9:05. Felt ok, nothing hurt, effort level seemed manageable. Let's pick it up a bit.
Second mile - 8:45. Still alright, but now it's hard. Had my first thought of pulling the plug. Nah, let's at least get to 5K and see where we're at
Third mile - 8:29. Ok, this kind of sucks now. Where's that hill I can power hike? Is there an aid station coming? Can a bear get in my way so I can stop?
Fourth mile - 8:19. A slight downhill here so the pace picks up, but about the 3 1/2 mile mark I started having serious doubts about holding the pace. But I also started thinking that it's going to suck just as much if I try this on Saturday, and I don't want to do this again. So #EmbraceTheSuck
Fifth mile - 8:26. Slipping into that gasping breathing pattern a couple of times, so had to ease back just a bit. Listening to a podcast and realize I haven't heard anything that's been said for about 15 minutes.
Sixth mile - 8:20. "It never always gets worse" is one of my favorite mantras in ultras. This mantra does not apply to 10Ks.
Final .22 - 1:44 for a 7:47 pace. I really had no idea when to break into the "finishing kick", if you can call a 7:47 pace that. But as I hit 6.22 and hit stop on the watch I doubled over gasping, so I think I did it right. Then again I didn't puke, so maybe not.
53:12 for an 8:33 overall pace.
It's pretty embarrassing how hard that was for me, when for almost everyone else in here you're running your easy runs faster than that. But I feel good about the effort I put out there today.
Thanks all for including me, and letting my slow, ultra ### muck up this thread of you real runners every once in awhile.
Last edited by a moderator:
. Kinda like running on the Hudson near the W Village in the 80s early 90s.
Like I said, I'm pretty sure he slowed down as a precaution (if he did, I'm just going by the sound of the engine that I heard as a was leaving the road, I didn't hear any brakes or anything) - like when you see one deer and you assume others are coming.