So What Happened To Bodog?

Posted by Bill @ 12:48 am

If you're new here, you may want to subscribe to my RSS feed. Thanks for visiting!

bodog-red-logoWhen Bodog lost its domains and had to convert over to NewBodog.com there was much speculation over how this would impact the company. Well, now we have some answers. To be honest, I was a little surprised.

On Sept 1st, Bodog (or NewBodog . . . depending on how you look at it) slipped to its lowest point following the yanking of its domains. On Sept 1 their peak traffic (as reported by PokerSiteScout) dropped to 1636 peak players. That was down from 2024 a week prior on Aug 25. So, the immediate impact was a massive 19% drop. But if we look at how they’ve weathered the storm since then we see that a week after the Sept 1 whacking they were back up to 1924. Still short of their 2024 number but this was a 5% drop which is within the normal variance of most week over week numbers. Perhaps a more compelling story is that on Sept 11, Bodog posted peak numbers of 2474 which put them at a 22% increase from Sept 1. Of course, these are not like comparisons because we were comparing Sat to Sat numbers and now we’re comparing Sat to Tues numbers. In fact, if we go back to Aug 21st then Bodog had posted a 2535 peak which means overall Tues numbers are down instead of up. All in all though I think it demonstrates that Bodog has shown the ability to bounce back here.

License

This work is published under a Creative Commons Attribution-NonCommercial-NoDerivs 2.5 License.

If you enjoyed this post, please consider getting our free RSS feed so you can be notified of other posts like this.


COMMENTS / ONE COMMENT

They have really been able to stick up there. Thats really good after such a dissapointment!

Poker Tips added these pithy words on Sep 15 07 at 8:21 am

SPEAK / ADD YOUR COMMENT
Comments are moderated.

XHTML: You can use these tags: <a href="" title="" rel=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <card> <code> <em> <i> <span class=""> <strike> <strong>

Return to Top