2005 UCI Africa Tour
The 2005 UCI Africa Tour was the first season of the UCI Africa Tour. The season began on 16 February 2005 with the Tour d'Egypte and ended on 2 October 2005 with the Tour du Sénégal. Tiaan Kannemeyer of South Africa was crowned as the 2005 UCI Africa Tour champion.
First edition of the UCI Africa Tour | |
Details | |
---|---|
Dates | 16 February 2005 –2 October 2006 |
Location | Africa |
Rounds | 4 |
Champions | |
Individual champion | |
Teams' champion | Barloworld |
Nations' champion | |
Throughout the season, points are awarded to the top finishers of stages within stage races and the final general classification standings of each of the stages races and one-day events. The quality and complexity of a race also determines how many points are awarded to the top finishers, the higher the UCI rating of a race, the more points are awarded. The UCI ratings from highest to lowest are as follows:
- Multi-day events: 2.HC, 2.1 and 2.2
- One-day events: 1.HC, 1.1 and 1.2
Events
Date | Race Name | Location | UCI Rating | Winner | Team |
---|---|---|---|---|---|
16–24 February | Tour d'Egypte | 2.2 | |||
26 February–12 March | Tour du Cameroun | 2.2 | |||
9–13 March | Giro del Capo | 2.2 | |||
22 March–2 April | Tour du Sénégal | 2.2 |
Final standings
Individual classification
Rank | Name | Points |
---|---|---|
1. | 163 | |
2. | 151 | |
3. | 100 | |
4. | 90 | |
5. | 72.66 | |
6. | 72 | |
7. | 58 | |
8. | 45.66 | |
9. | 43.66 | |
10. | 42 |
Team classification
Rank | Team | Points |
---|---|---|
1. | Barloworld | 327 |
2. | Team Nippo | 130 |
3. | Team Konica Minolta | 101 |
4. | Dukla Trenčín | 37 |
5. | Team Exel | 32.32 |
6. | Team Wiesenhof | 28 |
7. | Team Lamonta | 27 |
8. | Intel-Action | 18 |
9. | Recycling.co.uk | 13 |
Nation classification
Rank | Nation | Points |
---|---|---|
1. | 1049.32 | |
2. | 329 | |
3. | 40 | |
4. | 22 | |
5. | 11.3 | |
6. | 6 | |
7. | 5 | |
8. | 5 | |
9. | 4 |
gollark: But AUR.
gollark: I was looking at recompiling my nginx with LibreSSL, as OpenSSL bad.
gollark: In that case, I understand, you are being REASONABLE™.
gollark: Oh, LibreSSL, neat.
gollark: You should always program as if key features of the language/libraries/runtime may fail at any time.
External links
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.