Site Meter WWE Daily » Blog Archive » May 25th Editon of Monday Night Raw in Jeopardy

May 25th Editon of Monday Night Raw in Jeopardy

by

raw_logo_branding

World Wrestling Entertainment has issued an press release on next weeks Monday Night Raw being in jeopardy because of an “scheduling issue”.

The May 25th Monday Night Raw edition was currently scheduled to take place at the Pepsi Center in Denver, Colorado. Game Four of the NBA’s Western Conference Finals between the Denver Nuggets and the Los Angeles Lakers is also scheduled to take place from the Pepsi Center next Monday night.

The WWE and Denver Nuggets are currently at an impasse in resolving a scheduling debacle by the team and the Pepsi Center. A sell-out crowd is expected to attend the WWE show at the same time the Denver Nuggets are slated to square off against the Los Angeles Lakers for Game 4 of the NBA Western Conference Finals.

WWE has held the May 25th date with the Pepsi Center since August 15, 2008.

“Even though the Denver Nuggets had a strong team this year and were projected to make the playoffs, obviously Nuggets and Pepsi Center owner Stan Kroenke did not have enough faith in his own team to hold the May 25th date for a potential playoff game,” said WWE Chairman Vince McMahon.

Did You Enjoy this Post? Subscribe to WWE Daily. It's Free!

Leave a Reply


About WWE Daily

It’s a knockdown, dragged-out, in-your-face power bomb that will lay the smack down daily with all the freshest news and information about the fantastic world of wrestling. It’s a no-holds-barred, no disqualification hard-core match that will rock your world daily with news about wrestlers from today, yesterday and tomorrow. What’s your name? IT DOESN’T MATTER WHAT YOUR NAME IS ‘CAUSE I’M THE ONE RUNNING THE SHOW!

WWE Daily Author(s)

Blogging Flair

free tracking

Sports & Outdoors Channel Posts

Hot Off The Press


Warning: Unknown: write failed: No space left on device (28) in Unknown on line 0

Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct () in Unknown on line 0