JR Launching 3-Part WrestleMania Series on FOX Sports, Did the Vince/Forbes Article Cause a Big WWE Stock Hit?

Nick Paglino

JR Launching 3-Part WrestleMania Series on FOX Sports

wwe stockThe following press release has been issued. As we noted earlier today, Part 1 of the series has already launched:


Three-Part Series Launches on FOXSports.com

As the 30th WrestleMania approaches, WWE Hall of Fame Announcer and FOXSports.com Contributor Jim Ross kicked off a three-part series on the history of wrestling's greatest showcase.

To read Part 1, click here: http://msn.foxsports.com/buzzer/wrestlemania-part-1

Starting with WrestleMania I, which debuted in 1985, Ross takes fans through the early years and the iconic body slam that launched the legend.

Ross talked to longtime WWE creative member Bruce Prichard, mega-villain Rowdy Roddy Piper, Million Dollar Man Ted DiBiase, Bubba Ray Dudley, Rob Van Dam and Roy Farris, aka the Honky Tonk Man.

Part 2 debuts on Tuesday, April 1 followed by Part 3 on Thursday, April 3.

Did the Vince/Forbes Article Cause a Big WWE Stock Hit?

The Forbes article profiling the WWE Network, which also contains quotes from Vince McMahon regarding the future of WWE, might have caused a big hit in the WWE stock at around 1pm EST today, as the stock was down about 7.3%.

The Forbes articles noted the recent surge in WWE's stock, but was quick to point out that while the stock has tripled in the past six months, profits have been stagnant and revenues "have barely budged in the past few years."

On the targeted 1 million Network subscribers WWE hopes to accumulate, the Forbes article notes the following:

Not everyone is sanguine about those [WWE Network] prospects, however. Intrepid Capital Management was WWE's largest outside shareholder until January 2014, when it sold its 10% stake in the public float at a 100% profit. Intrepid portfolio manager Jayme Wiggins believes the WWE Network will be a tougher sell.

Have a news tip? Attended an event and want to send a live report? Submit it now!
monitoring_string = "851cc24eadecaa7a82287c82808f23d0"