2026 Twin Cities Marathon: Race Report

Last year, our family moved from Eagan, Minn. to Rochester, Minn., and this was my first training cycle in Rochester. It was one of my best training cycles since starting marathoning back in 2009. My mileage was solid, I had some great workouts, and I incorporated weightlifting into my schedule.

My races leading up to Twin Cities improved each time, and I clocked a solid 1:27:06 half marathon, so I felt ready for the Twin Cities Marathon.

The weather on Sunday was almost perfect. Cool, not much of a breeze, and not humid. My friends Brittany and Jared picked me up around 5:45 AM, and we drove to downtown Minneapolis. Jared was running the 10 mile, so we had plenty of time before the race started. Jared headed to the start and Brittany and I went to her in-laws', Wayne and Jen, hotel to relax indoors before the race. I had already eaten oatmeal and drank some coffee, but I snagged some coffee and a banana at the hotel as well.

We chatted about running for a while, then it was time to make our way down to the start. We walked down and met up with Michelle, who would be running the marathon with Brittany. After a photo, we went our separate ways to the start.

Since my goal was to run 3:05, I looked for the 3:05 pacer. I thought that it was going to be an old running buddy, but it turns out he had been moved to the 3:00 group, so the 3:05 pacer was someone I didn't know.

The race started, and we settled in to our goal pace. I gave the pacer a, "nice job, pacer," as we went through the first few miles in almost perfect splits.

I was feeling pretty good as we cruised along, but at around seven miles my foot started hurting a little bit. It had been flaring up here and there during training, but it never really slowed me down. I was hoping the pain would just stick right where it was at and wouldn't become a problem later in the race.

The miles ticked along. I love the Twin Cities Marathon course — lots of trees, lakes, and plenty of spectators. I saw an old friend and co-cross country coach, Jeff Webber, an old boss's son, Christian Hall, and a member of a running club I used to run with, Mike Kaiser. It's always nice to get a boost from familiar faces.

At the halfway point we came in a little fast. I was afraid that the 40ish second cushion could cause problems later, but I was feeling pretty good, so I didn't worry too much. I stuck with the pacer and for twenty miles I ran close behind him or right next to him. 

Around 20 miles I was still feeling pretty good and hadn't hit the wall, so I decided to forget about the pacer and just go by feel. If you've run Twin Cities before, you know about the notorious Summit Ave hill. I was a little nervous about the hills. I live half a mile from the Douglas Trail in Rochester. It's pancake flat, and I did the majority of my miles on it. I tried to get some hills in my training, but unfortunately from my house there's not a lot of good options that don't have a bunch of stoplights. It worked out though. I must have done enough hills, because it didn't end up being a problem. 

The entire race I was looking forward to mile 24 where my family and a couple of friends were going to be cheering for me, so I didn't think about the hills a ton as I anticipated my cheering zone. 

It was awesome getting to see my kids and wife along with some friends at mile 24. I gave some high fives, my daughter handed me my sunglasses, and from there I cruised to the finish line. I moved at a pretty good clip and passed quite a few runners at the end. I pulled through the finish line at 3:01:49. 

It was a great finish. I ran the first half of the race in 1:31:53, so I ran a negative split of over a minute, and I ran my last 2K at a 6:39 pace.

My goal for the race was a 3:05, so for the first time in seventeen years of marathoning I beat my "A" goal. I was really happy with this result. Based on my half marathon time a few weeks ago, the VDOT calculator had a marathon prediction of 3:01:45. The McMillan calculator came in at 3:03:18. As I've said before, I usually do better at shorter distances, so to almost nail the VDOT time is a big accomplishment for me.

After the race, I grabbed my post-race refreshments. I ran into Michelle (from The Runner's Plate and an old friend), chatted briefly, then headed to the beer garden. I had taken a break from alcohol for the seven weeks leading up to the marathon, which made the Summit Oktoberfest taste that much sweeter. I chatted with a couple of runners, then met up with Laura and the kids. We took some pictures, than headed to Cossetta's for lunch before driving back to Rochester. 

Thank you to Gayle and DJ for letting us stay with you for the weekend. Thanks also to Wayne and Jen for letting me hang out in the hotel room before the race.

Twin Cities Marathon weekend of 2026 was a good one!

Twin Cities Marathon: It's Goal Time

View from above my tune-up run in Winona this morning

Tomorrow morning I'll be running the Twin Cities Marathon. I'm pretty excited for the race as it will be the first time in several years that I've followed a training plan for a marathon. I wrote the training plan myself, and when I write training plans I draw from a variety of sources, but a lot of what I base my training plans on is from a book by Matt Fitzgerald and Brad Hudson called "Run Faster from the 5K to the Marathon: How to Be Your Own Best Coach." 

This training plan generally involved a speed or interval workout, a tempo run or cruise intervals, a long run, easy runs, and two weightlifting sessions. I started the plan at about 30 miles a week and built up to a peak week of 67 miles.

Since training went so well, my goal for the race is a little loftier than I would have thought when I started this plan a few months ago. I did a few 5Ks during this training plan, and three weeks ago I raced a half marathon as a tune up race. Based on my time of 1:27:06, the VDOT calculator has me predicted to run a 3:01:45, and the McMillan calculator predicts a 3:03:18.

While I'd love to run a 3:01 or a 3:03, I've always been a little faster as the distance gets shorter, so 3:03 sounds a little faster than I think I could do. 

So, here are my A, B, and C goals:

A Goal:
3:05. I think this will be tough, but doable. One cool thing about this goal is that there is a 3:05 pacer, and I know him and have run with him before.

B Goal:
3:09:43. This is the time I would have had to run this year to get into the Boston Marathon.

C Goal:
3:15. Running this time would qualify me for the Boston Marathon, but this year qualifiers needed to run over five minutes faster than their qualifying time to get in (they randomly draw for additional entrants).

I've never hit my A goal in a marathon before, but I feel like I have a good chance tomorrow. I plan on going out with the 3:05 pacer and just seeing what happens.

Thanks to everyone who's offered words of encouragement and support and thanks to all my readers. I'm looking forward to writing about how the race went soon.

Marathon Training

Twin Cities Marathon is almost here. It's been years since I've done a structured training plan for a marathon, and the first time since high school that I've incorporated weightlifting into my training.

Going into this training cycle I planned on getting to a reasonably high weekly mileage, and I was actually able to up my mileage a little more than I was planning. I managed an average of just over 44 miles a week in 14 weeks of training, and my peak week was 67 miles.

Besides running more miles than I have in years, I've also been hitting some pretty solid workouts. For a lot of my training cycle, I did some solid tempo runs between 20 and 30 minutes, and an interval workout just about every week. In 14 weeks of training, I only bailed on two workouts as my legs just weren't feeling it those days.

Besides the tempo runs and interval workouts, I also got in some good long runs. I did three long runs of 20 miles or more, and did a handful of long runs where I ran the last few miles at goal marathon pace.

My highlight long run was a two mile warmup, racing a half marathon at 6:39/mile pace, four easy miles, then two miles at goal marathon pace for a total of 21 miles.

I've really enjoyed this training block, and a big part of that was getting to train with my kiddos. Quite a few times this summer I did the first part of an easy run with my 10 year-old, and as I've mentioned before, he biked with me on several of my long runs. My six year-old daughter also joined me on her bike on a couple of my runs. On our last outing, we were going along and she said, "Three miles is my record."

I said, "How about we go four miles?"

She said, "Let's do six." And she did do six miles. It was great.

It's been a solid three-and-a-half months of training, and I'm feeling pretty good going into the Twin Cities Marathon. I'll give my goals for the race in my next post.

Healthy Human Race Half Marathon

Three weeks before the Twin Cities Marathon, I decided to do a tune-up race and run a half marathon. I'd done a few 5Ks in this training cycle, but I knew a half marathon would give me a more accurate gauge on how fast I could race a marathon.

The morning of the race I decided to ride my bike to the start to get in a little warmup and avoid having to mess with parking. With the days getting shorter, I had to dig through my bike stuff to find my headlight, and I ended up doing the first half of my half hour ride in the dark. 

The race started at 7 AM, and I got to the start with enough time to run a two mile warm up.

After the little jog, I got lined up and chatted with an old friend from a running club in the twin cities. 

The race started, and I settled into what I thought would be a good pace. After a couple miles, I checked my watch and noticed that I was running just a couple of seconds per mile slower than I had been planning.

I was able to pick up the pace a bit, and I felt like I was moving along at a challenging but somewhat comfortable pace. It was a pretty small field, and there were only a couple of people running close to me, and after around five miles I was running by myself other than one guy who was about 30 seconds behind me for most of the race.

The course was pretty flat and I enjoyed running through various parks and along the Zumbro River. The aid stations were adequately spaced, and I took water and Gatorade along with a few Pure Fuel Maple Syrup gels.

With a couple of miles left, I was feeling pretty good and was able to pick up the pace for the last couple miles. I ended up finishing in 1:27:07. My 5K of 19:06 gave me a VDOT equivalent time of 1:27:42, so I feel like my fitness has continued to improve during this training cycle.

Laura and the kids came for the finish of the race, and it was great having them cheer for me as I wrapped up the race.

Like I said, it was a small race, so the Healthy Human Race wasn't overly competitive, but I still felt good about finishing as the sixth place male and second in my age group. My 1:27 was the fastest I've run a half since running the Pensacola Beach Half Marathon in January of 2018, and almost 10 minutes faster than the last half marathon I raced, the Louisiana Half Marathon, in January of 2025.

So, I'm feeling like my training has gone well and I'm feeling optimistic about the Twin Cities Marathon in two weeks. I'll give a recap of my training for Twin Cities in my next post.

Training Update

Training for the Twin Cities Marathon has been going great! Better than I expected. I didn't think I would be in as good of shape as I'm in when I started training seriously a few months ago.

One big key to my success has been my lack of injuries. My foot has been a little sore off and on, but it hasn't hindered my running at all. I also had one day where I started a run and my knee hurt bad enough that I wasn't able to run. I was afraid that I might be derailed, but I took two days off and my knee was fine afterwards.

My weightlifting has also been going OK. I haven't been making big improvements, but I think the strength training has still helped me stay healthy and improved my speed.

I've done four 5Ks since I've started this training plan, and I've gotten faster on each one. I ran 21:32, 20:44, 19:13, and 19:06.

One thing I've really enjoyed during this training cycle is doing my long runs with my kiddo. He's biked with me for 13, 14, 18, and 19 miles. Not only has he provided good company on two hour+ runs, he also carries the water. We usually talk about camping and fishing, but occasionally touch on other topics.

Tomorrow I'll be racing the Healthy Human Race Half Marathon. I've got a goal pace in mind, so we'll see what happens.

If you're interested in my training in detail, here's a link to my training plan for this year's Twin Cities Marathon:

Twin Cities Marathon Training Plan

Washington Running

A couple weeks ago, our family took a trip out to Washington state. It was a wonderful trip for a variety of reasons, including the fact that it was about ten degrees cooler in Washington than it was in Minnesota, and I work outside.

We saw lots of beautiful scenery including Mt. Ranier, various locations at Olympic National Park, and North Cascades National Park. We saw wildlife like elk, marmot, deer, sea lions, seals, otters, and a variety of small marine animals. We got to do several scenic hikes and drives as well as see a Twins vs. Mariners game in Seattle. We also had a chance encounter with my cousin and his family and got to spend time with some friends in Seattle. 

I also had some great running on our trip. On our first morning, I got onto my Garmin Connect app and mapped out a route from our hotel in Port Angeles. I saw that there was a trail along the waterfront that was only about a mile from our hotel, so I took off and ran through town and down to the water.

As I was running along the water, I saw something near shore. I paused and took a closer look. It was otters. Not something I see when running on the Douglas Trail in Rochester. 

The next morning I took my son with me and we drove to the trail this time, and more otters showed up along with sea lions, eagles, and herons.

I also got to go on a couple runs in Leavenworth, running through the mountains. 

My last run was the Renton parkrun. The course ran along a river and was mostly shaded. It was an out-and-back and it was very flat. At the half mile mark I took my first peek at my watch and saw that I was averaging a 6:35/mile pace. This was a fair amount slower than I was expecting, and I was hoping that I wasn't in worse shape than I thought I was. 

By the turnaround I was moving at a faster clip, and I finished the race in 19:13, a 6:11/mile pace. This happened to be my fastest 5K since May of 2021, so I'm feeling pretty good about my training.

The trip to Washington was awesome, other than me getting sick at the end and missing the last couple days of fun. Running there was great and running is going well in general. In my next post I'll give an update on how my training is going.

Marathon Training

Although I've done a marathon the past few years, I haven't really trained to run a fast race for several years. This year, I set the lofty goal of breaking 3:20 in the marathon. After running 3:53 in 2025, a sub-3:20 would be a huge improvement.

While on its face a 3:20 may look like a nearly unattainable goal, I'm very optimistic.

First, I'll look at why I ran a 3:53 last year. My mileage per week for 2025 was the lowest it had been since I started running again in 2009. I also wasn't racing, didn't have a structured training plan, and weighed more than I'd weighed in years,

Now, I have reason to be optimistic for this year. First, I'll be putting in more miles in this training cycle than I have in years. Second, I've started lifted weights, which I think has been a missing piece in my training puzzle. Third, I've gotten down closer to my racing weight, and if I stay on track, I should be down to race weight by race day. And lastly, I'll be following a structured training plan for the first time in years.

As I move through my training cycle, I'll be running a few 5Ks to get a gauge on my fitness. I did one at the beginning of this training cycle, clocking in at 21:32.  With only a couple weeks of training under my belt, I was happy with this result. According to the VDOT calculator, a 21:32 in the 5K is equivalent to a 3:25:48 marathon — not a sub-3:20, but this early in the training cycle, not a bad result.

Just three weeks later, I posted a 20:44 — a big improvement in a short amount of time. This time is equivalent to a 3:18:18, which would mean I'm on track to hit my goal.

The caveat to these 5K times is that I've always skewed at being faster in the shorter distances than the longer ones. My 5K PR, 16:17, is equivalent to a 1:14:36 half marathon and a 2:36:05 marathon, and my PRs in those distances are 1:16 and 2:50 (though my marathon PR would be faster had a couple of courses been marked correctly).

I'm six weeks into my 16 week training plan. I'm fortunate to have a work schedule where I have ample time in the morning to work out. A couple days I week I have time to get in a run and then lift weights before work.

In a week I'll be racing another 5K, and I'm excited to see how my training is progressing. I've run some good workouts, and I really think I'm going to see some solid progress.