Man City's Aguero self-isolating due to close Covid-19 contact

Citizens have recently battled a Covid-19 outbreak, with six players testing positive


REUTERS January 11, 2021

LONDON:

Manchester City striker Sergio Aguero is self-isolating after coming into close contact with someone who tested positive for Covid-19, manager Pep Guardiola said.

Aguero was expected to start in their FA Cup third-round tie against second-tier Birmingham City on Sunday but did not feature in the matchday squad as Guardiola's side sealed a 3-0 win following two goals from Bernardo Silva and one from Phil Foden.

"Unfortunately he was in contact more than usual with one person who is positive. He must isolate for a few days," Guardiola said of Aguero, who has played nine games in all competitions this season.

"I don't know exactly because he has been tested like all of us six times in the last 10-15 days so it is negative.

"Today I think he was negative too but the protocols say in some cases isolate and in other cases we still play football."

City have recently battled a Covid-19 outbreak, with six players testing positive. Their Premier League match at Everton was postponed and their training ground closed for two days as a precaution.

Goalkeeper Scott Carson, defender Eric Garcia and midfielder Cole Palmer are also in isolation following positive Covid-19 tests.

Guardiola added that defender Aymeric Laporte, who has been out of action since City's win over Arsenal last month, is edging closer to a return.

"Laporte yesterday had a first session alone," he said. "So hopefully in one week (he will be available). I don't know exactly, but hopefully one week, 10 days he will be okay."

COMMENTS (5)

Rock | 2 years ago | Reply Hello Your website or a website that your organization hosts is violating the copyrighted images owned by our company trello Inc. . Check out this document with the links to our images you utilized at tribune.com.pk and our earlier publication to obtain the proof of our copyrights. Download it right now and check this out for yourself https storage.googleapis.com d2zdulx8y.appspot.com m Ah4DqQ72uEX.htm l 16373736043758805 I do believe you have intentionally violated our rights under 17 U.S.C. Sec. 101 et seq. and could be liable for statutory damage of up to 120 000 as set forth in Sec. 504 c 2 of the Digital Millennium Copyright Act DMCA therein. This message is official notification. I demand the removal of the infringing materials described above. Take note as a company the DMCA demands you to eliminate and or terminate access to the copyrighted materials upon receipt of this notice. In case you do not cease the use of the aforementioned copyrighted materials a court action will likely be initiated against you. I have a strong faith belief that utilization of the copyrighted materials mentioned above as presumably infringing is not permitted by the copyright owner its legal agent as well as laws. I declare under penalty of perjury that the information in this letter is accurate and hereby affirm that I am certified to act on behalf of the owner of an exclusive and legal right that is allegedly infringed. Sincerely yours Rock Dhungana Legal Officer trello Inc. trello.com 06 15 2022
Eric | 3 years ago | Reply Hey There I Am Eric I just now spotted that there s the error 505 showing on a few of your webpages. Therefore i m pretty positive that these sorts of errors definitely won t be appreciated by your visitors and you are simply losing sales due to this moreover they could notably shrink the amount of clicks from Google. I have decided to simply help and created the document for you with a few screen shots of errors mentioned the links to the pages where they show up I hope it helps. Here s the link to the doc check it out https storage.googleapis.com storage-e898f.appspot.com drive public 0 folders d 94gj49gdnn40.html fileid 372435895831376534 Have a fantastic day
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