2017 Specialized Fatboy Carbon vs 2019 Salsa Mukluk Carbon
The L is the Salsa Mukluk Carbon size closest to your L Specialized Fatboy Carbon. We match frame stack and reach. This is a geometry comparison, not a fit recommendation; stem, spacers, handlebars and saddle setup also affect your riding position.
What changes on the Salsa Mukluk Carbon
Compared with the Specialized Fatboy Carbon in L, the Salsa Mukluk Carbon in L places the top of the head tube 4 mm higher and 9 mm further forward, relative to the bottom bracket. Its wheelbase is 7 mm longer, which can contribute to stability at speed.
- Frame stack
- +4 mm
- Higher front end
- Frame reach
- +9 mm
- Longer frame reach
- Wheelbase
- +7 mm
- Longer: steadier at speed
- Head angle
- −1.5°
- Slacker: calmer steering
- Chainstays
- n/a
- One of the bikes has no number for this
The two frames
Only the Specialized Fatboy Carbon is drawn. The Salsa Mukluk Carbon numbers we have for size L are missing the chainstay length.
Geometry side by side
| Measurement | Specialized Fatboy Carbon L | Salsa Mukluk Carbon L | Difference |
|---|---|---|---|
| Reach | 437mm | 446.2 | +9 mm |
| Stack | 617mm | 620.7 | +4 mm |
| Head tube angle | 70.5° | 69 | −1.5° |
| Seat tube angle | 73° | 73 | ±0.0° |
| Effective top tube | 626mm | 636 | +10 mm |
| Chainstay length | 455mm | not listed | |
| Wheelbase | 1135mm | 1142.3 | +7 mm |
| BB drop | 60mm | 63 | +3 mm |
| BB height | 307mm | not listed | |
| Standover | 778.3mm | 765.3 | −13 mm |
| Seat tube length | 470mm | 508 | +38 mm |
| Fork length | 496mm | 483 | −13 mm |
| Head tube length | 110mm | 133 | +23 mm |
Differences are the Salsa Mukluk Carbon minus the Specialized Fatboy Carbon. Full charts: 2017 Specialized Fatboy Carbon, 2019 Salsa Mukluk Carbon.
Where each sits in its class
Specialized Fatboy CarbonSalsa Mukluk Carbon
Each bike is ranked against the other fat bikes on Quiver, on frame geometry alone. Not your hand position or ride feel.
Know what is on every bike.
Add your bike to Quiver. Keep its parts, setup, and service history together, then share your build.
Explore the app
