Write an Article

WWE Rumour: Finn Balor not returning at Royal Rumble?

f

The Demon King's return is probably going to take longer than expected.


Finn Balor was expected to return at Royal Rumble as a surprise entrant.

Finn Balor’s run in the main roster was off to a magical start after he was crowned the inaugural WWE Universal Champion, at Summerslam. However, it came to a sudden halt, as Balor was forced to vacate the title the very next day due to injury.

According to cagesideseats.com, it seems like he won’t make it for the Royal Rumble as expected. Apparently, the plan was to bring Balor back as a surprise entrant in the Royal Rumble match. 

Balor suffered the injury during the match against Seth Rollins, at Summerslam, after he was power bombed into the barricade, which resulted in major torn labrum and several minor injuries as well. Below is a clip of the incident:

 

Here is what Balor commented about his injury on “The Ross Report”:

"The original diagnosis was 4 to 6 months, but when they found the extra problems in there, they said it was going to be a hard fix now. You know, I can try to shave some extra time off but I’m not going to. If I am ready before 6 months, I’m going to make sure that when the time comes I am going to be better than ever."

Balor has been working hard in the WWE Performance Centre and Dr Jeffrey Dugas from Birmingham, Alabama, as a part of his rehabilitation program and also addressed the WWE Universe. You can watch the video right here:

With this year’s Royal Rumble taking place at Alamodome, Texas. WWE are sure promoting this as a huge event, with rumoured returns of several legends, such as Shawn Micheals, Stone Cold Steve Austin and The Undertaker. WWE would have loved a Finn Balor return as well, however, under current circumstances, it seems highly unlikely.


For latest WWE News, live coverage and rumours visit our Sportskeeda WWE section. Also if you are attending a WWE Live event or have a news tip for us drop us an email at fightclub (at) sportskeeda (dot) com.



Fetching more content...