Michal Ordoš

Michal Ordoš (born 27 January 1983) is a Czech football player who plays for FK Blansko.

Michal Ordoš
Personal information
Date of birth (1983-01-27) 27 January 1983
Place of birth Znojmo, Czechoslovakia
Height 1.90 m (6 ft 3 in)
Playing position(s) Forward
Club information
Current team
Blansko
Youth career
1990–1993 Sokol Troskotovice
1993–1996 SK Mikulov
1996–1999 Zeman Brno
1999–2003 Slovácko
Senior career*
Years Team Apps (Gls)
2003–2006 Slovácko 27 (5)
2006–2007 Mladá Boleslav 20 (2)
2007–2008 Bohemians 1905 24 (3)
2008–2011 Sigma Olomouc 76 (23)
2011 Kapfenberg 14 (4)
2012–2016 Sigma Olomouc 28 (16)
2016–2017 Karmiotissa 32 (4)
2017 SC Retz 13 (4)
2018 SC Wieselburg
2018–2019 Znojmo 11 (1)
2019– Blansko
National team
2012–2013 Czech Republic 2 (0)
* Senior club appearances and goals counted for the domestic league only and correct as of 00:55, 20 May 2019 (UTC)
‡ National team caps and goals correct as of 8 February 2013

Club career

Ordoš is a prolific goalscorer. In the 2008–09 season, he scored nine goals. In the 2009-2010 season Ordoš scored 12 goals, becoming the Gambrinus liga top-scorer.[1]

In July 2017, Ordoš signed with Austrian club SC Retz.[2] He left the club at the end of the year, to join another Austrian club, SC Wieselburg.[3]

Ordoš joined 1. SC Znojmo for the 2017/18 season in the summer 2018.[4] He played there until February 2019, where he joined FK Blansko.[5]

International career

He made his debut for Czech national team on 14 November 2012 in a friendly match against Slovakia at the age of 29.

gollark: It says "EdDSA-like digital signatures", which implies that it may not actually be something available outside of CC.
gollark: It would be neat if they were cryptographically signed too, but it turns out I have no idea what actual algorithm the potatOS ECC library is implementing, oops.
gollark: So, progress on the potatoupdates™ system, I now have a script generating manifest files which are deterministically generated from the exact contents of a PotatOS version™.
gollark: > multiprocessing.pool objects have internal resources that need to be properly managed (like any other resource) by using the pool as a context manager or by calling close() and terminate() manually. Failure to do this can lead to the process hanging on finalization.> Note that is not correct to rely on the garbage colletor to destroy the pool as CPython does not assure that the finalizer of the pool will be called (see object.__del__() for more information).Great abstraction there, Python. Really great.
gollark: No, I mean I was reading from underneath the line it highlighted, which was the POST documentation.

References

This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.