Shimano GRX FC-RX810-1 Crankset - 175mm 11-Speed 42t 110 BCD Hollowtech II Spindle Interface BLK MFPN=BB30-OUT-1 10sp 50/56 16 Braze on Boot Size:41.5
USD140.00
USD185.00
Pay in 4 interest-free payments of $35.00 Learn more
Shipping Estimate
USA
- USA
- CAN
- USA
- CAN
Ships within 48 hours · Estimated delivery Nov 18 - Nov 23
Court notes
Description
Shimano GRX FC RX810 1 Crankset 175mm 11 Speed 42t 110 BCD Hollowtech II Spindle Interface BLK MFPN=BB30 OUT 1 10sp 50 56 16 Braze on Boot Size:41.5 10sp 50 56 16 Braze on 99g High Mount Bottom Double }Magura Shiftmix Left Handlebar Clamp for Shimano I Spec I+II Black Color Black Rings 42 Number of Chainrings Single Crank Length (mm) 175 Crank Intended Use Gravel Drivetrain Speeds 11 Weight 655 BB Included No Pedal Spindle 9 16" Spindle Interface Type Shimano Hollowtech II Chainring BCD 110 Chainline Hub Compatibility 135 142 Road Disc Hubs > 415 mm Chainstay Defined Color Black Crank Length 175Mm Chainring Size 42T The Shimano GRX FC RX810 features optimum gearing for mixed terrain and riding styles and is designed for use with GRX Di2 components
Exchange/Return Notes
- We offer a 30-day return/exchange service after receiving.
- Final sale items are not eligible for returns or exchanges.
- To process your return/exchange, please contact us at [email protected]
- Please click here for more details>>> Return & Exchange Policy
Frequently Asked Questions for Shimano GRX FC-RX810-1 Crankset - 175mm 11-Speed 42t 110 BCD Hollowtech II Spindle Interface BLK MFPN=BB30-OUT-1 10sp 50/56 16 Braze on Boot Size:41.5
What should I record if a purchase-related problem happens only sometimes?
Avoid repeatedly recreating a problem when doing so could cause damage. Keep your notes concise enough for support to review.
What should I clarify if an offer has location restrictions?
Check whether a location change affects the displayed currency or price. Use the existing order reference if a restriction appears afterward.
What should I do if my order record shows an incorrect name?
Do not assume a support reply confirms the database change is complete. Avoid repeating sensitive information in unnecessary follow-up messages.