Ivica Ivušić – Croatia | World Cup 2026 Player Profile
Ivica Ivušić
Date of BirthFebruary 1, 1995 (age 31)
Place of BirthRijeka, Croatia
Height / Weight195 / 77
PositionGoalkeeper
Current ClubHNK Hajduk Split
110
Career
Appearances
0
Career
Goals
2025-26 Season
| Competition | MP | Gls | Ast |
|---|---|---|---|
| HNL | 15 | 0 | 0 |
| UEFA Europa Conference League | 15 | 0 | 0 |
| 1. Division | 27 | 0 | 0 |
| 1. Division | 27 | 0 | 0 |
| Cup | 5 | 0 | 0 |
| UEFA Europa Conference League | 10 | 0 | 0 |
| UEFA Europa League | 10 | 0 | 0 |
| Friendlies | 1 | 0 | 0 |
| All Competitions | 110 | 0 | 0 |
36
Int'l
Caps
0
Int'l
Goals
Croatia 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 |
|---|---|---|---|---|---|---|---|---|
| No World Cup 2026 player stats have been published for this player yet. | ||||||||
Competition performance
| Competition | Team | MP | Starts | Min | Gls | Ast | Rating |
|---|---|---|---|---|---|---|---|
| No World Cup 2026 player stats have been published for this player yet. | |||||||
Shooting stats — World Cup 2026
| Gls | Sh | SoT | SoT% | Sh/90 | G/Sh | G/SoT | xG |
|---|---|---|---|---|---|---|---|
| No World Cup 2026 player stats have been published for this player yet. | |||||||
Passing & creativity — World Cup 2026
| Key Passes | Crosses | Pass Accuracy | Chances Created | Ast | xA |
|---|---|---|---|---|---|
| No World Cup 2026 player stats have been published for this player yet. | |||||
Discipline — World Cup 2026
| CrdY | CrdR | Fls | Fld | Off | Int |
|---|---|---|---|---|---|
| No World Cup 2026 player stats have been published for this player yet. | |||||
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.