STATS
| rating | goal | assists | total... | passes | key... | duels won | |
|---|---|---|---|---|---|---|---|
vs![]() | 6.2 | 0 | 0 | 0 | 23 | 0 | 1 |
vs![]() | 7.4 | 0 | 0 | 0 | 44 | 0 | 1 |
vs![]() | 7.1 | 0 | 0 | 0 | 29 | 0 | 0 |
vs![]() | 8.3 | 0 | 0 | 0 | 44 | 0 | 2 |
30 Nov 25FT
20
14 Oct 25FT
03
04 Oct 25FT
10
| Club | Season | lineup... | match... | yellow... | red... | mins | goals... |
|---|---|---|---|---|---|---|---|
| 2022 | 14 | 15 | 0 | 0 | 1280 | 0.00 | |
| 2023 | 32 | 32 | 3 | 0 | 2880 | 0.00 | |
| 2023/2024 | 2 | 2 | 0 | 0 | 180 | 0.00 | |
| 2024 | 30 | 30 | 3 | 0 | 2682 | 0.00 | |
| 2025 | 20 | 20 | 2 | 0 | 1799 | 0.00 | |
| Total | 98 | 99 | 8 | 0 | 8821 | 0.00 |
OPPONENT
| Opponent | M | W | D | L | |||||
|---|---|---|---|---|---|---|---|---|---|
| 5 | 0 | 5 | 0 | 0 | 0 | 0 | 0 | 0 | |
| 5 | 2 | 3 | 0 | 0 | 0 | 0 | 0 | 0 | |
| 5 | 2 | 1 | 2 | 0 | 0 | 0 | 0 | 0 | |
| 5 | 3 | 2 | 0 | 0 | 0 | 0 | 0 | 0 | |
| 5 | 1 | 3 | 1 | 0 | 0 | 0 | 0 | 0 | |
| 5 | 2 | 3 | 0 | 0 | 0 | 0 | 0 | 0 | |
| 5 | 0 | 5 | 0 | 0 | 0 | 0 | 0 | 0 | |
| 4 | 2 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | |
| 4 | 2 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | |
| 4 | 1 | 3 | 0 | 0 | 0 | 0 | 0 | 0 |
- Current market value
- Highest transfer fee
- Transfer fee
Performance Overview
-
Clean sheets
2.9
Save per game
99.9%
Minutes per game
Passes
Assists0
Touches679
Big chances created-
Key passes0.05
Accurate per game3.75
Acc. own half-
Acc. opposition half-
Acc. long balls-
Acc. chipped passes-
Acc. crosses0%
Player Information
Age
27
Born: 31/08/1998
Height
196
Position
Goalkeeper
Elias Hadaya played in 3 teams:
Bryne, Utsikten, SandefjordWhen and where played Elias Hadaya?
Elias Hadaya (Sweden) currently plays for club Sandefjord. Elias Hadaya is 27 years old (31/08/1998) and he is 196 tall. Elias Hadaya jersey number is 30.
How many Salary earn Elias Hadaya per year?
Elias Hadaya receive a Salary per year
In this profile you will can follow the player data information, statistics, career history and performance of Elias Hadaya in Sandefjord matches.
Show more ›››
vs








