VS
The record covers 8 completed meetings between Panetolikos and AOK Kerkyra from 17 September 2011 to 25 February 2018. Panetolikos won 4, AOK Kerkyra won 2 and 2 matches ended level; the aggregate was 11–6. The fixture dated 2018-02-25 was Panetolikos 1–0 AOK Kerkyra in Super League 1. Another listed fixture dated 2017-10-21 was AOK Kerkyra 1–0 Panetolikos in Super League 1. This summary reflects the listed completed fixtures only.
Past matches, Panetolikos vs AOK Kerkyra
Match center
Starting eleven
Starting XI Panetolikos
-
82
-
88
-
21
-
66
-
17
-
16
-
11
-
22
-
7
-
73
-
94
AOK Kerkyra Starting XI
-
31
-
2
-
3
-
17
-
55
-
23
-
7
-
4
-
6
-
18
-
14
Substitutes Panetolikos
-
33
-
6
-
5
-
10
-
23
-
77
-
12
AOK Kerkyra Substitutes
-
16
-
10
-
77
-
21
-
70
-
13
-
88
Match events
-
10'S. Vasiloudis Marcos Paulo
-
45' +1⚽Willyan Normal Goal (Asst: E. Mihaj)
-
70'E. Mensah G. Pamlidis
-
73'P. Zorbas F. Georgiou
-
79'K. Georgakopoulos M. Rolle
-
80'F. Bravo Willyan
-
88'K. Itabel F. Mazurek
Matchup Panetolikos VS AOK Kerkyra
Record and recent results
The available record contains 8 completed meetings from 17 September 2011 to 25 February 2018. Panetolikos won 4, AOK Kerkyra won 2, and 2 matches ended level; the aggregate score is 11–6 in Panetolikos’s favour. The fixture dated 2018-02-25 was Panetolikos 1–0 AOK Kerkyra in Super League 1. Another listed fixture dated 2017-10-21 was AOK Kerkyra 1–0 Panetolikos in Super League 1. The other listed fixture was 2017-02-25, AOK Kerkyra 0–0 Panetolikos in Super League 1. The balance remains a description of the listed sample.
Home context and coverage
Home results: Panetolikos won 2 of 4 matches, while AOK Kerkyra won 1 of 4. The most represented competition is Super League 1 with 8 recorded meetings. The record includes 0 matches decided after extra time and 0 matches decided on penalties. Home listings add context but do not establish a permanent venue-based trend. The summary uses only completed FT, AET or PEN fixtures linked to this H2H. The sample remains historical and should be read as context, not a forecast.