Šeško vs Gelhardt

FPL Comparison · GW1 · Who to buy?

Quick answer: Buy Gelhardt over Šeško this week. Gelhardt scores higher across the engine's combined signals.

Buy Gelhardt over Šeško this week.

Gelhardt scores higher across the engine's combined signals.

Šeško
Man Utd
FWD£7.0m3.2% owned
11
Goals
2
Assists
111
Points
Engine verdict:AVOID
Next: @ HUL · D2/5 · 1.7 xP
Shin injury - 75% chance of playing
Full profile →
✓ Recommended pick
MID£5.0m0.1% owned
0
Goals
0
Assists
0
Points
Engine verdict:AVOID
Next: @ NFO · D3/5 · 1.5 xP
Full profile →

Head-to-Head Stats

Šeško (A) vs Gelhardt (B) — ✓ marks the better value
AStatB
£7.0mPrice£5.0m
3.2%Ownership0.1%
111Total points0
11Goals0
2Assists0
19Bonus points0
0.0Form (last 30 days)0.0
0.0Avg pts last 5 GWs0.0
1.7Next fixture xP1.5
10.26-GW projected xP8.7
9.2xG this season0.0
0.3xA this season0.0

Recent Form — Last 5 Gameweeks

Šeško
No history
Gelhardt
No history

Upcoming Fixture Difficulty

Šeško
HUL
IPS
EVE
MCI
FUL
TOT
Gelhardt
NFO
BRE
BHA
NEW
CRY
ARS
Easy (D1–2) Medium (D3) Hard (D4) Very hard (D5)

Šeško vs Gelhardt — Common Questions

Should I buy Šeško or Gelhardt in FPL?

Buy Gelhardt over Šeško this week. Gelhardt scores higher across the engine's combined signals. Šeško costs £7.0m and Gelhardt costs £5.0m — the price gap is £2.0m.

Šeško or Gelhardt — who should I captain GW1?

Onside recommends Gelhardt as the captain pick for GW1 (AVOID). Gelhardt scores higher across the engine's combined signals.

How do Šeško and Gelhardt compare statistically?

This season: Šeško has 11 goals + 2 assists (111 pts, £7.0m). Gelhardt has 0 goals + 0 assists (0 pts, £5.0m). Šeško lead on goal involvements.

Who has the better fixture — Šeško or Gelhardt?

GW1: Šeško plays @ HUL (D2) and Gelhardt plays @ NFO (D3). Šeško has the easier fixture.

Do Šeško or Gelhardt take set pieces?

Neither Šeško nor Gelhardt are listed as primary set-piece takers in Onside's current data.

Explore More

Compare Šeško against:

Comparison data sourced from Fantasy Premier League API. Verdicts computed by the Onside engine. Data refreshes continuously.