AFCON 2025. Why did Uganda play all three of its goalkeepers in the match against Nigeria?
By FaithDecember 31, 20252 min read
[vc_row][vc_column][vc_column_text css=""]
Defeated by Nigeria on Tuesday, December 30th (1-3) and eliminated from the Africa Cup of Nations, Uganda experienced a highly improbable situation in their final group match. Paul Put's Cranes fielded all three of their goalkeepers in this game against the Super Eagles. Why?
Uganda desperately needed a win against Nigeria on Tuesday, December 30th, to qualify for the next round of the Africa Cup of Nations . Trailing after 27 minutes to a goal by Paul Onuachu, the Cranes suffered a stroke of bad luck, having to field all three of their goalkeepers in the same match. This seriously hampered their chances of victory.
The starting goalkeeper, Denis Oyango, wearing the captain's armband, quickly felt pain in his left foot. He remained on the pitch for the first half, but the Ugandan goalkeeper was eventually substituted at halftime. His backup, Salim Magoola, took over.
Salim Magoola's huge blunder
But ten minutes later, the Al Hilal Omdurman player from Sudan was sent off. Guilty of handling a shot from Victor Osimhen outside his penalty area, the 30-year-old goalkeeper received a deserved red card.From then on, the Cranes' third-choice goalkeeper, Nafian Alionzi, was called upon to enter the game at Alhassan Stadium. Reduced to ten men and with their third-choice keeper, Uganda conceded twice more to goals from Raphael Onyedika. Rogers Mato's goal to pull one back made no difference; Paul Put's men were eliminated from the Africa Cup of Nations after this 1-3 defeat . Their opponents that evening, Nigeria, continue their journey and will face the third-placed team from Group F in the round of 16: either Cameroon or Mozambique.
[/vc_column_text][/vc_column][/vc_row]
Advertisements
Cookie Consent
We use cookies to improve your experience on our site. By using our site, you consent to cookies.
Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together.
90 days
__utma
ID used to identify users and sessions
2 years after last activity
__utmt
Used to monitor number of Google Analytics server requests
10 minutes
__utmb
Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server.
30 minutes after last activity
__utmc
Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session.
End of session (browser)
__utmz
Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server
6 months after last activity
__utmv
Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server.
2 years after last activity
__utmx
Used to determine whether a user is included in an A / B or Multivariate test.
18 months
_ga
ID used to identify users
2 years
_gali
Used by Google Analytics to determine which links on a page are being clicked
30 seconds
_ga_
ID used to identify users
2 years
_gid
ID used to identify users for 24 hours after last activity
24 hours
_gat
Used to monitor number of Google Analytics server requests when using Google Tag Manager