Halo Gravitas 29" Boost CL Rear Wheel (XD) 32h Silver MFPN=11.4118.059.025 Number of Chainrings No Rings Boot Size:41.5
USD250.00
USD292.00
Pay in 4 interest-free payments of $62.50 Learn more
Shipping Estimate
USA
- USA
- CAN
- USA
- CAN
Ships within 48 hours · Estimated delivery Nov 11 - Nov 16
Court notes
Description
Halo Gravitas 29" Boost CL Rear Wheel (XD) 32h Silver MFPN=11.4118.059.025 Number of Chainrings No Rings Boot Size:41.5 Number of Chainrings No Rings No Spider IncludedDrivetrain Speeds 12Drivetrain Speeds 13Chainring BCD Direct Mount SRAM 8 BoltChainline Hub Compatibility 135 142 Road Disc Hubs < 415 mm ChainstayChainline Hub Compatibility 135 142 Road Disc Hubs > 415 mm ChainstayColor CarbonCrank Length (mm) 165Crank Intended Use RoadCrank Intended Use GravelBB Included NoPedal Spindle 9 16"Spindle Interface Type SRAM DUBDefined Color Carbon Vendor Basil Manufacture Number 18296 Model Name Miles Tarpaulin Trunk Bag XL Pro Category Bags and brass nipples Rear: MTC Supadrive rear hub uses a wedge pawl mechanism and hollow CrMo axles for maximum stiffness and efficiency 120 points of engagement (3 deg) and Center Lock brake mount
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 Halo Gravitas 29" Boost CL Rear Wheel (XD) 32h Silver MFPN=11.4118.059.025 Number of Chainrings No Rings 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.