Mehmet Topal (Topal M.)

Advertisement
Advertisement
Advertisement
Advertisement
Advertisement
Advertisement
Advertisement
Advertisement
Mehmet Topal
Mehmet Topal
Midfielder
Age: 38 (March 03, 1986)
Last Matches

Career

Season
Team
Competition
A
2021/2022
6.3
7
0
0
1
0
2020/2021
6.9
25
2
2
2
1
2019/2020
7.2
25
0
1
2
0
2018/2019
7.0
28
1
0
5
0
2017/2018
7.4
29
2
3
3
0
2016/2017
7.3
29
4
2
9
1
2015/2016
7.3
33
1
2
4
0
2014/2015
33
2
0
7
0
2013/2014
27
3
-
4
0
2012/2013
26
3
-
6
0
2011/2012
20
0
-
4
0
2010/2011
23
1
-
5
1
Total
305
19
10
52
3
Season
Team
Competition
A
2020/2021
2
0
0
0
0
2020
1
0
0
0
0
2018/2019
2
1
0
0
0
2017/2018
8
1
-
1
0
2016/2017
5
0
-
1
0
2015/2016
7
0
-
2
0
2014/2015
7
2
-
0
0
2014
1
0
-
0
0
2013
1
0
-
0
0
2012/2013
7
1
-
1
0
2012
1
0
-
0
0
2011/2012
1
0
-
0
0
Total
43
5
0
5
0
Season
Team
Competition
A
2021/2022
6.4
3
0
0
0
0
2020/2021
6.5
4
1
0
1
0
2019/2020
6.7
7
0
0
3
0
2018/2019
6.8
4
1
1
0
0
2018/2019
2
0
0
0
0
2017/2018
4
0
0
0
0
2016/2017
7.2
10
0
1
0
0
2016/2017
1
0
0
0
0
2015/2016
7.0
11
2
0
4
1
2015/2016
2
0
0
0
0
2013/2014
3
0
0
0
0
2012/2013
12
0
-
3
0
2012/2013
4
0
-
0
0
2011/2012
6
2
-
0
0
2011/2012
3
0
-
0
0
2010/2011
5
0
-
0
0
2009/2010
7
1
-
1
0
2008/2009
4
0
-
1
0
2008/2009
1
0
-
0
0
2007/2008
5
0
-
1
0
2006/2007
3
0
-
0
0
Total
101
7
2
14
1
Season
Team
Competition
A
2018/2019
2
0
1
0
0
2016
7.1
3
0
1
0
0
2016
9
0
0
1
0
2012
5
0
-
0
0
2008
6.8
4
0
-
1
0
Total
69
2
2
5
0

Transfers

Date
From
Type
To
Fee
Jul 12, 21
Free agent
Free agent
Aug 26, 19
Free agent
Free agent
Jul 01, 12
Transfer
Transfer
Jul 01, 10
Transfer
Transfer
Sep 01, 06
Transfer
Transfer

Injury History

From
Until
Injury
Mar 08, 22
Aug 05, 22
Injury
Jan 08, 22
Jan 13, 22
Illness
Sep 16, 21
Oct 29, 21
Thigh Injury
Feb 01, 21
Feb 13, 21
Muscle Injury
Dec 03, 20
Dec 08, 20
Injury
Nov 30, 20
Dec 01, 20
Injury
May 12, 19
May 25, 19
Groin Injury
Mar 16, 19
Apr 06, 19
Back Injury
Mar 03, 19
Mar 14, 19
Back Injury
Oct 08, 18
Nov 10, 18
Hernia
Apr 28, 17
Apr 29, 17
Injury
NOTE: Older historical data may be incomplete, but we are in the process of updating our database.