The third outfield spot is where a Team of the Season gets interesting. You might have a regular outfielder with a good year, a stronger hitter who split time between two positions, and a player who was excellent in a short spell. Their names can sit next to each other on a leaderboard. To put one of them in the lineup, you need to know what they did, how often they did it, and where they actually played.
That’s the question we wanted the 2026 Statbase Team of the Season to answer. How strong a squad can we build from the performances we can substantiate across a whole season?
What PFI tells us
The Player Form Index, or PFI, starts with a game. We use the recorded contributions at the plate, on the mound and in the field to assess a player’s performance in the context of that game and competition. The score sits alongside the game log, so you can see the appearance it came from and how it fits into the player’s season.
There are three ways to read that record. Latest Game shows the most recent appearance. Recent Form gives more weight to the games a player has played lately. That matters if you’re preparing for next weekend and want to see how an opponent is performing now. Season PFI gives you the longer view. April stays in the picture even when September is the part everyone remembers.
France D1 is a good example of what that means in practice. We worked from 119 played games and 2,902 scored player-game performances across 182 players, from opening weekend through the playoffs. The Season view in the Performance Hub shows the same PFI scores we used to build the squad. The difference between a leaderboard place and a roster place comes down to eligibility and how the players fit together.
How the metrics work together
The same game records support several kinds of analysis in Statbase. PFI follows performance from game to game. PVI, our Player Value Index, uses a broader body of evidence to assess a player’s value in the context of their league and role. That assessment also informs OVR, which brings together the different parts of a player’s profile, such as batting, pitching and defense.
At club level, the Team Power Metric helps us look at strength across a roster. That changes the question. A club can have several outstanding players and still have a thin pitching staff. In matchup work, StatPredict brings player value, recent form and team strength together with the information we have about the teams involved. When a scout is looking across borders, our league-strength and translation work helps frame what a performance might mean in a different competition.
For Team of the Season, we use Season PFI to rank eligible performances. Playing time and recorded positions establish which jobs a player can be considered for. That separation lets the same player record support a season award, a scouting conversation and a forecast without asking one score to answer all three questions.
Show me why that player made the team
When a platform puts “we have THAT FANCY METRIC” (you name it) in its pitch, I want to see what happens after the number appears. Pick two players competing for the same spot. Show me their games, the work they did at that position, and how the evidence leads to a decision. I’d rather see the hardest selection you made than the highest score on your dashboard.
In France D1, two candidates for an outfield spot had the same number of verified games in the outfield. One faced a higher eligibility bar because his club played deeper into the playoffs. We went back to the box scores, revised the rule so every club faced the same positional standard, and reran the selections across every league we covered. The performances stayed exactly as recorded. The stronger full-season candidate earned the spot.
That’s the difference I want people to see in Statbase. Open an award card and you’ll find the same Season PFI you see on the leaderboard. Follow it to the player’s profile and you can see the games behind it. The selection adds the baseball questions that a ranking leaves open. Did the player actually play the position? Was there enough work over the season to make the case? How does that player fit alongside the other nineteen?
The same season record can support a different decision the next day. A scout can read a player’s form alongside PVI and league context. A coach preparing for a series can bring that evidence into StatPredict alongside team strength and the players available. The work carries forward because the player, the games and the context stay connected. That’s what makes the award worth building and what makes the platform useful after the reveal.
Building the twenty
We start with a lineup you could put on a field. That means a starting pitcher, every defensive position, three outfielders and a designated hitter. We look for the strongest complete lineup among players with enough verified playing time and evidence at the positions they’re being considered for.
One detail we revised this year was the position requirement. Two players in the same league with the same verified outfield workload should clear the same bar, even if one club played deeper into the playoffs. We now anchor that requirement to the league’s regular-season schedule. Playoff performances still count toward both the player’s score and their record at the position.
Then we build a five-pitcher staff with room for additional starters, relief specialists and flexibility. We look at the work those pitchers actually did. For the five dugout hitters, we go back to the season rankings and take the strongest remaining eligible bats across distinct primary positions. A two-way player can be considered for either job and earns one place in the squad.
When a selection is close, we can go back to the games, check the role and see who else could have filled it. I want us to be able to have that conversation with a player who missed out.
Why we’re building this
I want a season played in France, Belgium or anywhere else in European baseball to leave a record that stays useful after the final out. A player should be able to carry that record into a conversation with a new club. A coach should be able to follow a development priority from one season to the next. A federation should be able to see where players are getting opportunities and how those pathways are changing.
That’s what we’re building Statbase for. The awards give people a reason to look. The profiles, game logs and analysis give them somewhere to go when they want to understand what they saw.
If you have a question about a selection, a scorebook detail we should look at, or a better way to handle a particular role, I’d really like to hear it. Bring a game or a player record and we can talk through it together. Email us at playball@statbase.eu
