Comparing Serie A players side by side only works if the metrics, minutes, and roles line up — otherwise you're just staring at colourful shapes. This guide walks through building a fair serie a player stats comparison in FBPlot, from picking the right chart type to catching the mistakes that make a radar or pizza chart misleading.
- Match position and minutes before charting — a serie a player stats comparison across mismatched roles produces noise, not insight.
- Radar and pizza charts work best for 2-4 players on percentile metrics within one role.
- Serie A sits in FBPlot's free Top 5 leagues tier in 2026, so no Pro plan is needed for single-league comparisons.
- Cross-competition comparisons (Serie A vs Premier League) need the same eligibility rules applied on both sides or the chart misleads.
Why this matters
A chart that compares Nicolò Barella's progressive passes to a wing-back's is comparing apples to a different sport. Role, minutes played, and sample size decide whether a comparison holds up under scrutiny — not the visual polish of the chart.
Build the comparison in FBPlot once the population and metrics are locked, and the chart becomes something you can actually publish or send to a scouting desk without someone poking a hole in it during the first ten seconds.
Most bad Serie A comparisons in 2026 fail for the same three reasons: mixed positions on one radar, raw totals instead of per-90 rates, and no stated cutoff for minutes played. Fix those three and the rest is mechanical.
What you'll need
- A defined question: who are you comparing, and why (scouting, punditry, fan content)
- A position or role filter — centre-backs against centre-backs, not centre-backs against strikers
- A minutes-played cutoff for the 2025/26 Serie A season (900 minutes is a common floor for outfield players)
- Per-90 or percentile-normalised metrics relevant to the role (progressive passes, xG per 90, tackles won per 90)
- 2 to 6 players to plot — more than six on one radar becomes unreadable
- FBPlot's chart builder, which covers Serie A under its free Top 5 leagues tier
The steps
1. Pick the comparison type
Radar and pizza charts suit 2-4 players on 6-10 percentile metrics within one role. Bar charts suit ranking a single metric across a longer list — say, every Serie A midfielder above 900 minutes on progressive carries. Scatter or swarm plots suit two metrics plotted against a wider population, useful for spotting outliers like a low-minutes forward with an unusually high xG per 90.
Common mistake: forcing 8 players onto one pizza chart. The slices overlap and the chart stops being readable past four names.
2. Define the population
Decide the season (2025/26), the competition (Serie A only, or Serie A plus other Top 5 leagues), and the minutes-played floor. Write this down before you touch the chart tool — it's the single fact that determines whether your comparison is defensible.
A 900-minute cutoff filters out small-sample noise from players who've featured in six matches. A 450-minute cutoff includes more rotation players but widens the variance on rate stats.
Common mistake: comparing a player with 1,800 minutes to one with 400 minutes on the same per-90 chart without flagging the gap.
3. Choose role-relevant metrics
A centre-back comparison wants aerial duels won, progressive passes, and interceptions per 90 — not shots on target. A winger comparison wants progressive carries, successful take-ons, and xA per 90. Pick 6-10 metrics maximum for a radar; more than that and the shape becomes unreadable.
Common mistake: using the same generic metric set (goals, assists, minutes) for every position because it's easier than tailoring the list.
4. Select your Serie A players
Name them explicitly — Khvicha Kvaratskhelia, Teun Koopmeiners, whoever fits the role and minutes floor you set in step 2. Keep the list to players who actually satisfy your cutoff; swapping in a name that falls short of 900 minutes undermines the whole comparison the moment someone checks.
5. Build the chart in FBPlot
Load the players into FBPlot's radar, pizza, bar, or scatter builder, apply the per-90 or percentile toggle, and set the competition filter to Serie A. Serie A is included in the free tier alongside the other Top 5 leagues, so a single-league comparison doesn't need the Pro plan.
Adjust colour and layout so overlapping players stay distinguishable — two similarly-shaded radar lines on top of each other is a common export problem.
Common mistake: leaving default axis scaling on when one metric (say, minutes played) dwarfs the rest and flattens every other slice.
6. Add context to the caption
State the season, the minutes cutoff, the population (e.g. "Serie A midfielders, 900+ minutes, 2025/26"), and the data date. A chart without this caption invites the first comment to be "compared to who, exactly?"
7. Export and share
Export at a resolution that holds up on social platforms, and keep the branding consistent if you're publishing under your own name or outlet. A chart that looks sharp at full size but pixelates when shared loses credibility before anyone reads the data.
Build your Serie A comparison now
Free tier covers Serie A and the rest of the Top 5 leagues.
Troubleshooting
The radar shape looks distorted or lopsided. One metric is probably on a raw-total scale while the rest are percentiles — normalise everything to the same scale before plotting.
Percentiles look wrong for a player you know well. Check the population filter; a percentile calculated against all Serie A players instead of just his position will misrepresent a specialist role.
Two players' lines overlap and you can't tell them apart. Increase colour contrast or switch from radar to a grouped bar chart, which separates players more clearly at 5+ metrics.
A low-minutes player is skewing the comparison. Raise the minutes-played floor — a player with 300 minutes can post an inflated per-90 rate that collapses over a full season.
You want Serie A against another league and the numbers don't line up. Apply identical eligibility rules — same minutes cutoff, same season window, same per-90 normalisation — on both competitions before charting them together.
The export looks fine on desktop but crops oddly on mobile. Check the chart's aspect ratio before exporting; radar and pizza charts with long legends are the most common casualties.
Tools and resources
- FBPlot's chart builder for radar, pizza, bar, and scatter/swarm charts across 107+ leagues, with Serie A included in the free Top 5 leagues tier
- A written eligibility rule (minutes cutoff, season, position filter) kept alongside every chart you publish
- If you're running the same comparison method across multiple competitions, the Premier League player stats comparison guide walks through the same steps applied to a different league — useful for checking your method holds up outside Serie A
What to do next
Once a single-league comparison works, the next test is running the same method on a different competition and seeing if the population rules still hold. That's exactly what the Premier League comparison guide linked above covers, and it's the fastest way to catch a rule that only worked by accident for Serie A.
FAQ
What's the best way to compare Serie A player stats side by side?
Use a radar or pizza chart for 2-4 players on percentile metrics within one role, with a stated minutes-played cutoff for the 2025/26 season. Bar charts work better for ranking a longer list on a single metric.
Is a radar chart better than a bar chart for Serie A comparisons?
Radar charts suit small groups (2-4 players) across 6-10 metrics in one role. Bar charts suit ranking more players on one metric, like every Serie A striker's xG per 90 above a minutes floor.
How many minutes played should I require before comparing players?
A 900-minute floor is a common cutoff for outfield players in a single Serie A season, filtering out small-sample noise. Lower floors like 450 minutes include more rotation players but widen variance on rate stats.
Can I compare Serie A players to Premier League players in the same chart?
Yes, as long as identical eligibility rules apply on both sides — same season window, same minutes cutoff, same per-90 or percentile normalisation. Mismatched rules produce a chart that looks fair but isn't.
How much does Serie A stats comparison cost on FBPlot?
Serie A is covered under FBPlot's free tier alongside the rest of the Top 5 leagues as of 2026. The Pro plan is only needed for competitions outside the Top 5.
Why do percentile stats look different depending on the population I pick?
A percentile is only meaningful relative to a defined group — all Serie A players versus just his position gives very different numbers. Always filter by role before reading a percentile as a ranking.
What metrics matter most for comparing Serie A midfielders?
Progressive passes per 90, progressive carries, tackles won per 90, and xA per 90 cover most midfield roles. Pick metrics tied to the specific role rather than generic totals like goals and assists.
How many players should go on one radar chart?
Keep radar and pizza charts to 2-4 players; beyond that the slices overlap and the chart becomes unreadable. Use a bar chart instead for comparing a longer list.
One last thing
The comparison that gets challenged fastest isn't the one with the wrong colours — it's the one where a reader asks "minutes played?" and there's no answer in the caption. State the cutoff every time, even when it feels obvious, because in 2026 anyone can screenshot a chart and strip the context from it in seconds.