Shimano FC-MT210-2 Crankset - 170mm 9-Speed 46/30t 48.8mm Chainline Riveted BLK Model=Lyrik Ultimate Charger 3 RC2 Suspension Fork 7 Bearing Type Cartridge Crown
USD48.99
USD87.99
Pay in 4 interest-free payments of $12.25 Learn more
Shipping Estimate
USA
- USA
- CAN
- USA
- CAN
Ships within 48 hours · Estimated delivery Nov 14 - Nov 19
Court notes
Description
Shimano FC MT210 2 Crankset 170mm 9 Speed 46 30t 48.8mm Chainline Riveted BLK Model=Lyrik Ultimate Charger 3 RC2 Suspension Fork 7 Bearing Type Cartridge Crown 7 Bearing Type Cartridge Crown Race 30 Weight 98 Defined Color Black Upper Stack Height 17 Length 370 Color Black Weight 503 Travel (mm) 100 Actuation Cable Remote Remote Position Left Remote Position Right Diameter 31 Color Black Rings 46 30 Number of Chainrings Double Crank Length (mm) 170 Crank Intended Use Mountain Drivetrain Speeds 9 BB Included No Pedal Spindle 9 16" Spindle Interface Type Shimano Hollowtech II Chainring BCD Riveted Chainline Hub Compatibility 135 142 MTB Hubs Defined Color Black }tr:nth child(even){background color:#f2f2f2}th{background color:#eb212e
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 FC-MT210-2 Crankset - 170mm 9-Speed 46/30t 48.8mm Chainline Riveted BLK Model=Lyrik Ultimate Charger 3 RC2 Suspension Fork 7 Bearing Type Cartridge Crown
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.