Tijjani Reijnders – Netherlands | World Cup 2026 Player Profile
Tijjani Reijnders
Date of BirthJuly 29, 1998 (age 27)
Place of BirthZwolle, Netherlands
Height / Weight178 / 73
PositionMidfielder
Current ClubManchester City
130
Career
Appearances
27
Career
Goals
2025-26 Season
| Competition | MP | Gls | Ast |
|---|---|---|---|
| Friendlies | 3 | 1 | 0 |
| World Cup | 3 | 0 | 1 |
| FIFA Club World Cup | 3 | 0 | 0 |
| Friendlies Clubs | 3 | 0 | 0 |
| League Cup | 3 | 1 | 1 |
| FA Cup | 5 | 0 | 2 |
| Premier League | 28 | 5 | 2 |
| UEFA Champions League | 10 | 0 | 3 |
| Serie A | 37 | 10 | 4 |
| UEFA Champions League | 10 | 3 | 0 |
| Coppa Italia | 5 | 2 | 0 |
| Euro Championship | 6 | 0 | 0 |
| UEFA Nations League | 7 | 3 | 1 |
| World Cup - Qualification Europe | 7 | 2 | 1 |
| All Competitions | 130 | 27 | 15 |
32
Int'l
Caps
6
Int'l
Goals
Netherlands International
VeloBet
Get a $20 World Cup Free Bet — No Deposit Required
Accepts:· 18+ · PLAY RESPONSIBLY
₿
Ξ
₮
Ł
World Cup 2026 — tournament summary
| MP | Starts | Min | Gls | Ast | G+A | CrdY | CrdR | Avg Rating |
|---|---|---|---|---|---|---|---|---|
| 3 | 3 | 201 | 0 | 1 | 1 | 0 | 0 | 6.63 |
Competition performance
| Competition | Team | MP | Starts | Min | Gls | Ast | Rating |
|---|---|---|---|---|---|---|---|
| World Cup | Netherlands | 3 | 3 | 201 | 0 | 1 | 6.63 |
Shooting stats — World Cup 2026
| Gls | Sh | SoT | SoT% | Sh/90 | G/Sh | G/SoT | xG |
|---|---|---|---|---|---|---|---|
| 0 | 4 | 2 | 50% | 1.79 | 0% | 0% | — |
Passing & creativity — World Cup 2026
| Key Passes | Crosses | Pass Accuracy | Chances Created | Ast | xA |
|---|---|---|---|---|---|
| 6 | — | 82% | 6 | 1 | — |
Discipline — World Cup 2026
| CrdY | CrdR | Fls | Fld | Off | Int |
|---|---|---|---|---|---|
| 0 | 0 | 0 | 3 | 0 | 2 |
CrdY = Yellow cards · CrdR = Red cards · Fls = Fouls committed · Fld = Fouls drawn · Off = Offsides · Int = Interceptions
Mbappé
Haaland
Vinícius Jr
Kane
Messi
Ronaldo
YamalData is sourced from API-Football and updated regularly. If you notice incorrect information, it will be corrected in the next data refresh.