Amir Khan decides against representing Pakistan in Rio Olympics

Brit acknowledges he will not be ready to seek place in Rio via qualification tournament


Sports Desk June 16, 2016
Amir Khan has acknowledged that he will not be ready to seek place in Rio via qualification tournament. PHOTO: REUTERS

British boxer Amir Khan has decided not to pursue the chance to represent Pakistan at the upcoming Rio Olympics, The Guardian reported on Wednesday.

The 29-year-old, who previously won a silver medal at 2004 Olympics in Athens, had earlier said he would “love” the opportunity to represent Pakistan.

However, now he has acknowledged that he will not be ready to seek a place in Rio via the final qualification tournament in Venezuela next month.

Amir Khan’s boxing event packs a punch

The Brit is still recovering from the sixth round knockout he suffered at the hands of Saul Alvárez in their WBC middleweight title fight in Las Vegas in May.

Amir had earlier raised the possibility of returning to Olympics after the world governing body, AIBA, ratified the eligibility of professional boxers for the event.

Would love to compete for Pakistan in Rio, says Amir Khan

Amir, who risked a two-year ban by the World Boxing Council had he made a return to the Games, is one of the few fully professional fighters to speak out in favour of the move.

COMMENTS (8)

FAZ | 7 years ago | Reply @salman: When did anyone from "Pakistan" did ask him to represent Pakistan anywhere? His efforts for the sportsmen of Liari is well appreciated but he is a British National. Cant represent Pakistan.
laughable | 7 years ago | Reply Just because your parents were born in Pakistan doesn't give you the right to represent Pakistan in the Olympics. Amir Khan was born in the UK and the Olympic Committee would not consider him eligible to represent Pakistan unless he immigrated back to Pakistan and took citizenship (which he hasn't).
VIEW MORE COMMENTS
Replying to X

Comments are moderated and generally will be posted if they are on-topic and not abusive.

For more information, please see our Comments FAQ