Sometimes they can be like me and get a lil premature with there ejactulation when they schedule fights, and also like me it dont make consumer of this premature ejactulation very happy.............
BoxRec a reliable source?
Collapse
-
-
Comment
-
Of course BoxRec would be a completely reliable source to the TS if Pacquiao vs. Martinez was put up without anything being signed or official.Comment
-
Comment
-
BoxRec is a site run entirely by volunteers. I very much appreciate the
job they do. We're lucky to have BoxRec.
Of course there's a mistake from time to time - I've contacted them to correct a few things in the past, such as:
http://boxrec.com/forum/viewtopic.php?f=1&t=136073
http://boxrec.com/forum/viewtopic.php?f=8&t=136574Comment
-
-
Boxrec is very dubious I jsut found out.
At least their fight stats are. Compubox did not do Froch v Dirrell. But boxrec had Froch landing some 50% more punches than Dirrell--some 150 or such. Many Brits apologized afterwards for the gift decision to Froch, saying he landed less than 30 punches for the fight.
Certainly it was Dirrell who outlanded Froch. So, at least as far as fight stats go, they are a dubious source to me. Putting out the PC thing.Comment
-
Comment
-
It's very reliable. I get all my boxing information from there and also the threads made on here.Comment
-
Post was about # of punches landed and boxrec's "version" of the same.
And as far as who won? Do a search on: British boxing fans apologize for decision given to Froch. And you will see many Brits apologized.
The fight itself was laxative. But if held in the USA, Froch would have been the one deducted points for some of his tactics, and Dirrell would have won by wide margin, maybe even so in a neutral country, if you can find one.
But it was a laxative fight with home cooking.
Bottom line as I posted yesterday, is a poll here at NSB: http://www.boxingscene.com/forums/po...s&pollid=21480
It has 220 to 73 or 69% to 23% in favor of Dirrell over Froch.
Our colleagues here at NSB have spoken clearly.
Case closed. Next.Comment

Comment