Royal Never Give Up
This article needs additional citations for verification. (May 2016) |
File:Royal Never Give Up logo.png | |
Sport | League of Legends |
---|---|
Colors | Gold and black |
Royal Never Give Up (RNG) is a Chinese League of Legends team that is competing in the League of Legends Pro League. It was the winner of the 2016 and 2018 LPL Spring Split[1][2][3][4], as well as the champion of 2018 Mid-Season Invitational.[5] It is the sister team of Star Horn Royal Club.
Roster
Current[6]
Yan "LetMe" Jun-Ze (严君泽) (toplane)
Liu "Zz1tai" Zhi-Hao (刘志豪) (substitute toplane)
Liu "mlxg" Shi-yu (刘世宇) (jungle)
Hong "Karsa" Hao-Xuan (洪浩轩) (substitute jungle)
Li "Xiaohu" Yuan-Hao (李元浩) (midlane)
Jian "Uzi" Zi-Hao (简自豪) (carry)
Dai "Able" Zhi-Chun (戴志春) (substitute carry)
Shi "Ming" Sen-Ming (史森明) (support)
Tournament results
- 1st — 2018 LPL Summer Playoffs
- 1st — 2018 Mid-Season Invitational
- 1st — 2018 LPL Spring Playoffs
- 1st — 2016 spring LPL
- 3-4th 2017 World Championship
- 3-4th — 2016 Mid-Season Invitational
- 2nd — 2016 summer LPL
- 5—8th 2016 world championship
References
- ^ Volk, Pete (6 May 2016). "First MSI playoff spot clinched". Retrieved 11 December 2016.
- ^ Volk, Pete (29 April 2016). "MSI preview: Royal Never Give Up". Retrieved 11 December 2016.
- ^ Sport1.de. "League of Legends MSI 2016: Royal Never Give Up im Portrait". Retrieved 11 December 2016.
{{cite web}}
: CS1 maint: numeric names: authors list (link) - ^ Machiavelli, Hamza (30 April 2018). "Uzi Wins the LPL Spring 2018 Finals – RNG Going to MSI this Year". eSportsRanks.
- ^ "KZ vs RNG: RNG beat KZ to win Mid-Season Invitational 2018". finalkill.com.
- ^ "2018春季赛RNG大名单". Weibo (in Chinese). 2017-12-21. Archived from the original on 2017-12-27. Retrieved 2017-12-27.
{{cite web}}
: Unknown parameter|dead-url=
ignored (|url-status=
suggested) (help)
As of this edit, this article uses content from "Royal_Never_Give_Up", which is licensed in a way that permits reuse under the Creative Commons Attribution-ShareAlike 3.0 Unported License, but not under the GFDL. All relevant terms must be followed.