(1) Thnku each n every1 of u who supported me n wished me luck V tried our best to b at ur expectations but unfortnately it cudnt happened
— Wahab Riaz (@WahabViki) March 21, 2015
Thnku every1 for ur love n support . Keep me in ur prayers n keep supporting me n my team. Love u all.
— Wahab Riaz (@WahabViki) March 21, 2015
Riaz, disappointed with the defeat, thanked his supporters in a tweet and said that the Pakistani team tried their best to land on everyone’s expectations.
Earlier in the day, he offered a public apology to the people, some of whom staged mock funerals for Pakistani cricket and reportedly destroyed their television sets.
“I am sad and I apologise to the people for the defeat because they had so many expectations from us,” the left arm pacer said on Geo News.
“I think more than ever we need the support of our fans now. I am sad because we could have won the match,” he said.
When asked about Rahat Ali dropping Watson’s catch, Riaz said, “I have no complaints because these things happen in a high-pressure match.”
ICC fines Riaz, Watson
On Saturday, Riaz was fined 50 per cent of his match fee by the ICC for violating the Code of Conduct during a heated war of words with Australia's Shane Watson.
Riaz was found to have breached article 2.1.4 of ICC's code for "using language or a gesture that is obscene, offensive or insulting during an International Match.” He was subsequently docked 50 per cent of his match fee.
Watson, who was found to have violated Article 2.1.8 (a) of the code for "conduct contrary to the spirit of the game", was slapped with fine equivalent to 15 per cent of his match fee.
Explaining his decision, Mr Madugalle said: “It was an enthralling contest between Shane and Wahab, but in the closing stages of the match both players crossed that fine line between intense competition and unacceptable behaviour, and this resulted in the sanctions.”
This article originally appeared in India Today.
COMMENTS (5)
Comments are moderated and generally will be posted if they are on-topic and not abusive.
For more information, please see our Comments FAQ