Announcement

Collapse
No announcement yet.

RIGONDEAUX vs LOMACHENKO - 12 POINT HEAD TO HEAD

Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • RIGONDEAUX vs LOMACHENKO - 12 POINT HEAD TO HEAD

    Judged on the following 12 Boxing Criteria to represent the 12 RD's of Boxing.

    RD 1. POWER: RIGONDEAUX
    RD 2. ACCURACY: RIGONDEAUX
    RD 3. RING CONTROL: LOMACHENKO
    RD 4. OFFENCE: LOMACHENKO
    RD 5. DEFENCE: RIGONDEAUX
    RD 6. HAND SPEED: LOMACHENKO
    RD 7. FOOT SPEED: LOMACHENKO
    RD 8. RING SMARTS: RIGONDEAUX
    RD 9. SIZE: LOMACHENKO
    RD 10. REACH: RIGONDEAUX
    RD 11. CHIN: LOMACHENKO
    RD 12. HEART: RIGONDEAUX

    RIGONDEAUX: 6 LOMACHENKO: 6

    PREDICTION: This Fight will be a DRAW.

    Feel free to Copy and Paste your own Results with RIGO or LOMO.

    RD 1. POWER:
    RD 2. ACCURACY:
    RD 3. RING CONTROL:
    RD 4. OFFENCE:
    RD 5. DEFENCE:
    RD 6. HAND SPEED:
    RD 7. FOOT SPEED:
    RD 8. RING SMARTS:
    RD 9. SIZE:
    RD 10. REACH:
    RD 11. CHIN:
    RD 12. HEART:
    Last edited by Boxnation fan; 12-09-2017, 11:56 AM.

  • #2
    nice breakdown, hard to disagree with. i agree with the point about power - rigo has dynamite in both hands, v good solid technique, whereas lomachenko can tend to be a bit flashy. i would also be tempted to give rigo 'footspeed' or at least, 'effective footspeed' or something for similar reasons - loma uses his fast feet to be flashy sometimes i feel, and ends up being imprecise with his punches

    size makes a big difference but strange that Rigo is being seen as such an underdog. odds are longer than 3/1 for Rigo to win, that is v good value!! i see this as a Rigo KO win in the late rounds

    Comment

    Working...
    X
    ERROR: The request could not be satisfied

    403 ERROR

    The request could not be satisfied.


    Request blocked. We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.
    If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.

    Generated by cloudfront (CloudFront)
    Request ID: 8Fm4Zfoqo8rtd9vJsxmGKreD-RsnkweX8m3ZRnXkOW43_YbLltvslw==
    
    TOP
    ERROR: The request could not be satisfied

    403 ERROR

    The request could not be satisfied.


    Request blocked. We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.
    If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.

    Generated by cloudfront (CloudFront)
    Request ID: dHZ5rbQDjrZ8kOwMaEx4Oygb5NdXwYxDyFMJfqZK6Csa-9p-C3goWw==