RAM® Fishfinder Deck Kit with Dual Humminbird Helix 8-10 & XPLORE Mount
Part#:RAM-FF1-D-202-25-202-2 UPC:793442027352
Ball Icon D SIZE
Arm Icon MED ARM
9 819 kr
logo icon

Powered by

Notify Me!
  • Supports up two fishfinders for maximum data intake ideal for bow or rear-mounted fishfinder setups
  • Compatible with Humminbird Helix 8-10 & XPLORE
  • Includes AMPS and tri-hole patterns for RAM® D size bases
  • Marine-grade aluminum construction with powder-coated finish
  • Back by a Lifetime Warranty
The RAM® Fishfinder Deck Kit with Dual Humminbird Helix 8-10 & XPLORE Mount (RAM-FF1-D-202-25-202-2) is a robust, powder-coated aluminum bracket configured with two D size fishfinder mounts that allows you to mount two Humminbird fishfinders side-by-side. Whether you're trolling deep waters or scanning shallow coves, this heavy-duty mount helps you take in more data for smarter navigation and better results. Built for versatility, the Deck Mount features a wide array of pre-drilled hole patterns, including three sets of 4-hole AMPS patterns and three sets of tri-hole patterns for seamless integration with RAM® Mounts D size bases. This solution comes with the RAM® Foot Stabilizer for added support and stability in rough waters. Crafted from marine-grade aluminum, this fishfinder mounting bracket is corrosion-resistant and engineered to withstand harsh marine environments—lasting longer than your boat and standing up to the roughest conditions. In fact, we guarantee it with a Lifetime Warranty for all RAM® components.
hardware included

Mounting Hardware
(1) RAM® Hi-Torq Wrench

hole pattern

See Drawing

ball size

D Size (2.25")

weight capacity

Standard Use: 6 lbs
Heavy-Duty Use: 5 lbs

materials

Marine-grade aluminum

packaging type

Poly Bag

Weight

0.0 kg

Består av

RAM® Double Socket Arm - D Size Medium RAM-D-201U
Ball Icon D SIZE
Arm Icon MED ARM
1 699 kr

Apex 13

Apex 16

Helix 8

Helix 9

Helix 10

Helix 12

Helix 15

Solix 10

Solix 12

Solix 15

XPLORE 9

XPLORE 10

XPLORE 12

Liquid error (snippets/solution line 10): Expected handle to be a String but got Hash