Ritchey WCS Link Seatpost - 20mm Offset, Black CheckoutTitle=Maxxis Holy Roller Tire - 26 x 2.4 Examples include Avid BB7 Avid Boot Size:41.5
USD119.95
USD154.95
Pay in 4 interest-free payments of $29.99 Learn more
Shipping Estimate
USA
- USA
- CAN
- USA
- CAN
Ships within 48 hours · Estimated delivery Nov 14 - Nov 19
Court notes
Description
Ritchey WCS Link Seatpost 20mm Offset, Black CheckoutTitle=Maxxis Holy Roller Tire 26 x 2.4 Examples include Avid BB7 Avid Boot Size:41.5 Examples include Avid BB7 Avid Juicy Hayes HFX and Hayes MX1 Rotor Size (mm) 220 Pad Compatibility All Pad Compounds Rotor Type Two Piece Weight 209 Hub Disc Compatibility 6 Bolt Size 220Mm Compatibility Type 6 Bolt 700c x 41mm tires on M–XL frame sizes (700c x 38mm with fenders) Rear Axle QR x 138mm Brake Type Disc TT (Effective) 630 Fork Type Rigid Fork Material Steel Frame Material Steel Frame Type Rigid Front Axle QR x 100mm Color Black Mfg Size X Large Platform Preamble Wheel Size 700c Defined Color Black Size X Large Link posts come with standard 2 bolt clamps: Vector Evo clamp (ST4170) is available separately Blatte Diameter 27
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 Ritchey WCS Link Seatpost - 20mm Offset, Black CheckoutTitle=Maxxis Holy Roller Tire - 26 x 2.4 Examples include Avid BB7 Avid 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.