J. Bellingham – England | World Cup 2026 Player Profile
J. Bellingham
Jude Victor William Bellingham
Date of BirthJune 29, 2003 (age 22)
Place of BirthStourbridge, England
Height / Weight186 / 75
PositionMidfielder
Current ClubEngland
80
Career
Appearances
19
Career
Goals
2025-26 Season
| Competition | MP | Gls | Ast |
|---|---|---|---|
| Friendlies | 1 | 0 | 0 |
| La Liga | 31 | 9 | 8 |
| Copa del Rey | 4 | 1 | 0 |
| Super Cup | 2 | 1 | 0 |
| FIFA Intercontinental Cup | 6 | 1 | 1 |
| UEFA Champions League | 13 | 3 | 3 |
| UEFA Super Cup | 1 | 0 | 0 |
| Euro Championship | 7 | 2 | 1 |
| UEFA Nations League | 4 | 1 | 2 |
| World Cup - Qualification Europe | 5 | 0 | 1 |
| FIFA Club World Cup | 6 | 1 | 1 |
| All Competitions | 80 | 19 | 17 |
23
Int'l
Caps
4
Int'l
Goals
England International
World Cup 2026
Group L →
England
Croatia
Ghana
Panama2026 tournament outlook
J. Bellingham will represent England at the 2026 FIFA World Cup. England have been drawn in Group L alongside Croatia, Ghana, Panama. Their campaign begins on 2026-06-17 against Croatia at AT&T Stadium, Arlington. As a midfielder, Bellingham will be looking to make an impact on the biggest stage in world football. England is a 1-time World Cup champion and will be looking to add to their legacy.
England at the 2026 World Cup
J. Bellingham is part of the England squad for the 2026 World Cup, managed by Thomas Tuchel, alongside D. Henderson, D. Burn, E. Anderson, and B. Saka among the key players.
View full England team profile →Related players
England Teammates
| Player | Position |
|---|---|
| D. Henderson | Goalkeeper |
| D. Burn | Defender |
| E. Anderson | Midfielder |
| B. Saka | Attacker |
Similar Players to Watch
| Player | Country | Why |
|---|---|---|
| D. García |  Mexico | Box-to-box energy |
| J. Adams |  South Africa | Creative playmaker |
| Mohamed Al Manai |  Qatar | Defensive anchor |
Mbappé
Haaland
Vinícius Jr
Messi
Ronaldo
YamalFrequently asked questions
Data is sourced from API-Football and updated regularly. If you notice incorrect information, it will be corrected in the next data refresh.