STATS
| rating | goal | assists | total... | passes | key... | duels won | |
|---|---|---|---|---|---|---|---|
vs![]() | 6.8 | 0 | 0 | 1 | 11 | 0 | 3 |
vs![]() | 6.8 | 0 | 0 | 0 | 4 | 0 | 2 |
vs![]() | 6.7 | 0 | 0 | 2 | 4 | 0 | 1 |
28 Dec 25FT
23
23 Mar 25NS
19 Nov 24NS
22 Jan 24FT
22
| Club | Season | lineup... | match... | yellow... | red... | mins | goals... |
|---|---|---|---|---|---|---|---|
| 2022/2023 | 9 | 23 | 0 | 0 | 944 | 0.13 | |
| 2023 | 4 | 9 | 1 | 0 | 353 | 0.11 | |
| 2025 | 3 | 6 | 0 | 0 | 315 | 0.00 | |
| 2026 | 3 | 6 | 0 | 0 | 234 | 0.00 | |
| Total | 19 | 44 | 1 | 0 | 1846 | 0.09 |
OPPONENT
| Opponent | M | W | D | L | |||||
|---|---|---|---|---|---|---|---|---|---|
| 4 | 2 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | |
| 4 | 0 | 1 | 3 | 0 | 0 | 0 | 0 | 0 | |
| 4 | 1 | 0 | 3 | 0 | 0 | 0 | 0 | 0 | |
| 4 | 2 | 2 | 0 | 0 | 0 | 0 | 0 | 0 | |
| 4 | 2 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | |
| 4 | 2 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | |
| 3 | 3 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | |
| 3 | 0 | 0 | 3 | 0 | 0 | 0 | 0 | 0 | |
| 3 | 2 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | |
| 3 | 1 | 2 | 0 | 0 | 0 | 0 | 0 | 0 |
- Current market value
- Highest transfer fee
- Transfer fee
Performance Overview
-
Goals per game average
-
Shots per goals average
-%
Minutes per game
Defending
Clean sheets-
Interceptions per game-
Tackles per game-
Possession won-
Dribbled past per game-
Clearances per game-
Error led to shot-
Error led to goal-
Penalty committed
Player Information
Age
30
Born: 31/01/1995
Height
171 cm
Position
F
Attacker
Gildo Lourenço played in 3 teams:
Mozambique, Sporting Covilhã, Al-Tadamon SourWhen and where played Gildo Lourenço?
Gildo Lourenço (Mozambique) currently plays for Liga 3 club Sporting Covilhã. Gildo Lourenço is 30 years old (31/01/1995) and he is 171 cm tall. Gildo Lourenço jersey number is 16.
How many Salary earn Gildo Lourenço per year?
Gildo Lourenço receive a Salary per year
In this profile you will can follow the player data information, statistics, career history and performance of Gildo Lourenço in Sporting Covilhã matches.
Show more ›››
vs





