2017-18 UCI Track Cycling World Cup

Redirect to:

2017–18 UCI Track Cycling World Cup

This page is a redirect. The following categories are used to track and monitor this redirect:

From a modification: This is a redirect from a modification of the target's title or a closely related title. For example, the words may be rearranged. This redirect is a modification of: 2017–18 UCI Track Cycling World Cup.
- Please note that there are many more specific templates. Please use {{R from alternative spelling}}, {{R from alternative hyphenation}}, {{R from alternative punctuation}}, {{R from alternative spacing}} and {{R from misquotation}} where relevant; see subcategories of Category:Redirects from modifications for other options (capitals, abbreviations, diacritics, plurals, stylizations, transliteration, ligatures, different parts of speech, etc.). If you are unsure which to use, this template is fine; someone will make it more specific later if necessary.
- In cases of modification from distinctly longer or shorter names, please use {{R from long name}} or {{R from short name}}, respectively. An abbreviation should be tagged with {{R from initialism}} or, if it can be spoken like a word such as NASA and RADAR, use {{R from acronym}}.
- Use this rcat instead of {{R from other capitalisation}} and {{R from plural}} in namespaces other than mainspace for those types of modification. This may also apply to several other subcategories of modification; please check those templates' output before saving if using outside of mainspace.

When appropriate, protection levels are automatically sensed, described and categorized.

This redirect was created by a bot because 2017–18 UCI Track Cycling World Cup exists. If you delete this redirect without also deleting 2017–18 UCI Track Cycling World Cup, the bot will most likely recreate it. Thus, if you think this should be deleted, your best option is to have 2017–18 UCI Track Cycling World Cup deleted and then delete this as a G8. Please don't delete this and salt the page to prevent the bot from re-creating it; that's almost certainly not the correct solution.
If that target page no longer exists, purge this page to refresh this message.