Click to Read an Important Member Update Regarding Our Comment System
We recently upgraded our comment system to improve reliability, performance, and long-term control, and we’re currently running both systems during the transition. This shift moves us away from an external service to a system we run and control directly—meaning we own the content and can continue improving it over time. We’ve also reduced the comment refresh delay from about 30 seconds to 10 seconds, making it much closer to real-time.
We understand there have been frustrations and increased feedback, and we’re actively working to improve things. What we ask is simple: use the system and give it a fair shot. If you run into issues, please submit them through the support form so we can track and fix them properly. Repeated complaints without details don’t help us solve problems—we appreciate your patience as we continue refining the experience.
If you’d like a full side-by-side comparison of the platforms and the reasons behind this decision, please refer to the chart below. This change is being made with the long-term benefit of the entire community in mind.
Built by Nationals Fans. Powered by the Conversation.
The Washington Nationals had a lot to smile about yesterday. To go three innings with no baserunners to score 15-runs over the next five innings was the high octane offense the Nats had been waiting for in the past week. While the final score showed they only needed three runs to win, it was nice to see a laugher by the end in a 15-2 obliteration of the Twins pitching staff.
The Nationals scored zero runs over the first three innings of tonight’s game against Minnesota, and in their remaining five offensive frames, scored 15. For those who don’t want to do that math, the Nats’ offense averaged three runs an inning over innings 4-8. Such an offensive outburst was accompanied by a stellar pitching performance, with Miles Mikolas picking up his first win as a Nat, Mitchell Parker retiring all eight batters he faced, and Zak Kent tossing an (almost) perfect ninth inning in his team debut. All of this came together to give the good guys a 15-2 victory to even the series with Minnesota at one apiece.
The Washington Nationals had Cade Cavalli on the mound last night for the first game in the series. Cavalli just didn’t have his swing-and-miss pitch, and the game as well as his defense just got away. Cavalli’s own fielding error led to three unearned runs. Those unearned runs made it 30 through the Nats’ 36th game. That is 0.83 free runs per game on average. The Nats lead baseball in the most unearned runs and lead MLB with 33 errors. The next closest team has 25 errors.
The Washington Nationals open up a 3-game series in inter-league play against the Minnesota Twins at Nationals Park. Cade Cavalli starts this series on an extra day of rest, courtesy of a scheduled day-off on the calendar yesterday.
Since we don’t have any baseball to enjoy today (at least from our organization), I wanted to take this opportunity to do a deep dive at every position and just take a look at what the Nationals have at every spot and every level, from the Washington Nationals on down to the Fredericksburg Nationals. I’ll warn everyone right off the bat, if you’re not a numbers person, this may not be the article for you. Stats junkies, on the other hand, welcome to paradise, my friends! I am going to do as much as I can to keep my opinions out and let the numbers speak for themselves, but as closely as I’m attempting to cover the minor leagues in tandem with the big league squad this season, I think it’s important to do this a couple of times throughout the year to give you all a better idea of who these guys might be. Last note, the positions I assign each player to are my best estimate or projection. Most guys are versatile and could be at a completely new spot any given week, so don’t worry too much over that. I hope you guys enjoy!
The early weeks of the 2026 season haven’t answered many long-term questions for the Washington Nationals — yet. That was never really the expectation. What they’ve done, though, is offer a clearer sense of direction. You can start to see where things might be heading, even if the picture isn’t fully formed yet.
You must be a TalkNats Subscriber to access this content. Subscribers have access to exclusive content on the TalkNats website and can engage in discussions with other Nats fans. Click here to become a subscriber.
First two weeks are free and then you will be billed $3.99/month. Cancel anytime. Secure payments using Stripe.
If you are already a subscriber, simply log in using the form below.
The Washington Nationals didn’t get a whole lot of production from the offense this afternoon, but they sure didn’t need more than three runs. The young coaching staff had quite the strategy cooked up this afternoon from a pitching standpoint, and a combination of PJ Poulin, Zack Littell, Mitchell Parker, Gus Varland, and Richard Lovelady executed it to perfection, leading the Nats to the 3-2 victory in today’s salvage game.
The Washington Nationals struggles at their home field continued on Saturday. The team dropped to a 3-11 record at Nationals Park.
Yesterday, the Nats got 6.0 innings of zeroes in the earned run category from starter Foster Griffin. Unfortunately the Nats once again fell due to mistakes. Three runs scored due to an error, and the Nats lost 4-1. This has become a theme for a team that leads MLB in errors (32) and unearned runs (27). The Nats have 28 percent more errors than the next closest team. These are just some of the mistakes we wrote about earlier in the week.
A big moment in the 2026 season as Foster Griffin stays in the game; Photo by Sol Tucker/TalkNats
The Washington Nationals haven’t had many big moments in Nationals Park this year. But Foster Griffin has shown he is good at his home stadium also. The Nats are a disappointing 3-11 in Nationals Park this year. That has to change. This is Griffin’s third start at home.
We recently upgraded our comment system to improve reliability, performance, and long-term control, and we’re currently running both systems during the transition. This shift moves us away from an external service to a system we run and control directly—meaning we own the content and can continue improving it over time. We’ve also reduced the comment refresh delay from about 30 seconds to 10 seconds, making it much closer to real-time.
We understand there have been frustrations and increased feedback, and we’re actively working to improve things. What we ask is simple: use the system and give it a fair shot. If you run into issues, please submit them through the support form so we can track and fix them properly. Repeated complaints without details don’t help us solve problems—we appreciate your patience as we continue refining the experience.
If you’d like a full side-by-side comparison of the platforms and the reasons behind this decision, please refer to the chart below. This change is being made with the long-term benefit of the entire community in mind.