STATS
| rating | goal | assists | total... | passes | key... | duels won | |
|---|---|---|---|---|---|---|---|
vs![]() | 6.7 | 0 | 0 | 1 | 33 | 0 | 4 |
15 Nov 25FT
23
08 Nov 25FT
20
09 May 25FT
20
| Club | Season | lineup... | match... | yellow... | red... | mins | goals... |
|---|---|---|---|---|---|---|---|
| 2016/2017 | 3 | 5 | 1 | 0 | 273 | 0.00 | |
| 2017/2018 | 3 | 3 | 0 | 0 | 270 | 0.00 | |
| 2023/2024 | 2 | 2 | 0 | 0 | 180 | 0.00 | |
| La Liga 2 | 15 | 16 | 1 | 0 | 1323 | 0.00 | |
| Total | 23 | 26 | 2 | 0 | 2046 | 0.00 |
OPPONENT
| Opponent | M | W | D | L | |||||
|---|---|---|---|---|---|---|---|---|---|
| 9 | 1 | 3 | 5 | 0 | 0 | 0 | 0 | 0 | |
| 9 | 1 | 3 | 5 | 0 | 0 | 0 | 0 | 0 | |
| 8 | 2 | 4 | 2 | 0 | 0 | 0 | 0 | 0 | |
| 8 | 3 | 2 | 3 | 0 | 0 | 0 | 0 | 0 | |
| 8 | 2 | 4 | 2 | 0 | 0 | 0 | 0 | 0 | |
| 8 | 3 | 2 | 3 | 0 | 0 | 0 | 0 | 0 | |
| 7 | 2 | 2 | 3 | 0 | 0 | 0 | 0 | 0 | |
| 7 | 2 | 2 | 3 | 0 | 0 | 0 | 0 | 0 | |
| 6 | 0 | 4 | 2 | 0 | 0 | 0 | 0 | 0 | |
| 6 | 2 | 3 | 1 | 0 | 0 | 0 | 0 | 0 |
- Current market value
- Highest transfer fee
- Transfer fee
Performance Overview
-
Fouls per game
0.1
Yellow cards per game
91.9%
Minutes per game
Passes
Assists0
Touches0
Big chances created-
Key passes0.00
Accurate per game0.00
Acc. own half-
Acc. opposition half-
Acc. long balls-
Acc. chipped passes-
Acc. crosses0%
Attacking
Goals0
Scoring frequency0
Goals per game0.00
Shots per game0.00
Shots on target per game0.00
Player Information
Age
31
Born: 17/05/1994
Height
191
Position
Defender
Branislav Ninaj played in 4 teams:
Lokeren, Sincan Belediyesi Ankaraspor, Sepsi, PodbrezováWhen and where played Branislav Ninaj?
Branislav Ninaj (Slovakia) currently plays for club Skalica. Branislav Ninaj is 31 years old (17/05/1994) and he is 191 tall. Branislav Ninaj jersey number is 88.
How many Salary earn Branislav Ninaj per year?
Branislav Ninaj receive a Salary per year
In this profile you will can follow the player data information, statistics, career history and performance of Branislav Ninaj in Skalica matches.
Show more ›››
vs





