Toro 76605 TITAN Z-Turn Mower 24hp Kawasaki V-Twin w/60″ Fabricated Deck

Original price was: $6,399.00.Current price is: $4,269.30.

5 People watching this product now!
Toro 76605 TITAN Z-Turn Mower 24hp Kawasaki V-Twin w/60″ Fabricated Deck
  • The rubber discharge chute flexes without busting up your landscaping or your ride.
  • Its heavy duty steel IronForged® Deck doesn’t flinch no matter what you throw its way.
  • Massive 22″ rear tires feature aggressive treads meant to bring Mother Nature to her knees.
  • Treaded front casters dial the attitude up to 11, making this one mighty-looking machine.
  • The gaming-style seat gives you big time support exactly where you need it.
  • Built with a commercial-style I-beam front end for extreme durability and strength.
  • Spray blocking fenders keep tire spray off your engine, and more importantly, you.
  • Its gigantic engine delivers mega power so you can absolutely dominate nature’s worst.
  • A cast aluminum stomp pad helps you scrape your boots, get your grip, step up and let ‘er rip.
  • The same drop pin height of cut used by the pros. So you can adjust to the perfect height, quickly.
  • Download the MyToro app from your mobile device’s app store for easy access to product resources, including manuals, how-to’s, and more

Specifications

Air Filter Kawasaki Standard Air Cleaner
Anti Scalp Wheels 4 Standard
Armrests Optional
Blade Design 0.164 in. / 0.417 cm Steel with Blade Stiffner
Blade Tip Speed 18,908 ft/min / 5,763 m/min
Box Dimensions 91 in. x 70.3 in. x 52 in. / 178.6 cm x 132.1 cm x 231.1 cm
CARB Compliant Not CARB Compliant
Carrier Frame 3 in. x 1.5 in. x 0.120 in. (7.6 cm x 3.8 cm x 0.3 cm) Wall Tubular Steel
Caster Tires 13 in. x 6.5 in. – 6 in. (33 cm x 16.5 cm – 15.2 cm) Pneumatic
Clutch Electromagnetic
Comfort Platform Standard Suspension
Cooling System Air Cooled
Crankshaft 1″ (25 mm) w/Steel Protector
Cup Holder Standard
Deck Design 10-Gauge Steel IronForged® with Fully Weld Grade 50 Steel Bumper
Deck Material 10 Gauge Steel
Deck Size 60 in / 152 cm
Discharge Chute Rubber
Drive System Hydrostatic
Drive Tires 22 in. x 11 in. (55.8 cm x 27.9 cm)
Drive Type Rear-Wheel Drive
Engine 24 hp Kawasaki FR730 726cc
Engine Brand Kawasaki
Engine Displacement (cc) 726 cc
Engine Horsepower 24.0 hp
Engine Power (kW) 17.9 kW
Foot Operated Height of Cut Standard
Forward Ground/Transport Speed Up to 8.5 mph / 13.6 kph
Forward Mowing Speed Up to 8.5 mph / 13.6 kph
Frame 3 in. x 1.5 in. (7.6 cm x 3.8 cm) Steel Tubing
Front Bumper Reinforced Bull-Nose
Fuel Capacity 5 gal. / 18.9 L / 20 Qt.
Fuel Type Gasoline
Height of Cut 1.5 – 5.0 in. / 3.8 – 12.7 cm
Hitch Bracket Standard
Number of Blades 3
Product Type TITAN
Product Use Residential
Recommended Oil Type 10W-30
Roll-Over Protection System (ROPS) Optional
Seat 20″ Gaming Style
Spindle Housing Cast-Aluminum
Start Type Electric
Steering Controls Twin Lever
Steering Dampeners Standard Dampers
Terrain Type Flat with Obstacles
Tires 13 in. x 6.5 in. (33 cm x 16.5 cm) Front, 22 in. x 11 in. (55.8 cm x 27.9 cm) Rear
Transmission Dual hydrostatic HG ZT2800
Weight 845 lbs / 383.3 kg

Disclaimer

*24 HP gross (725 cc) at 3,600 RPM SAE J1940 and SAE J2723, as rated by Kawasaki®. As configured to meet safety, emission and operating requirements, the actual engine horsepower on this mower may be significantly lower.
†See retailer for warranty details.
‡Specifications subject to change without notice and without incurring obligation. Products depicted are for demonstration purposes only. Actual products offered for sale may vary in design, required attachments and safety features.

Customer Reviews

0 reviews
0
0
0
0
0

There are no reviews yet.

Be the first to review “Toro 76605 TITAN Z-Turn Mower 24hp Kawasaki V-Twin w/60″ Fabricated Deck”

Your email address will not be published. Required fields are marked *

You have to be logged in to be able to add photos to your review.

Online Sports Nutrition and Natural Dietetics.

Chances are there wasn't collaboration, communication, and checkpoints, there wasn't a process agreed upon or specified with the granularity required. It's content strategy gone awry right from the start. Forswearing the use of Lorem Ipsum wouldn't have helped, won't help now. It's like saying you're a bad designer, use less bold text, don't use italics in every other paragraph. True enough, but that's not all that it takes to get things back on track.

The villagers are out there with a vengeance to get that Frankenstein

You made all the required mock ups for commissioned layout, got all the approvals, built a tested code base or had them built, you decided on a content management system, got a license for it or adapted:

  • The toppings you may chose for that TV dinner pizza slice when you forgot to shop for foods, the paint you may slap on your face to impress the new boss is your business.
  • But what about your daily bread? Design comps, layouts, wireframes—will your clients accept that you go about things the facile way?
  • Authorities in our business will tell in no uncertain terms that Lorem Ipsum is that huge, huge no no to forswear forever.
  • Not so fast, I'd say, there are some redeeming factors in favor of greeking text, as its use is merely the symptom of a worse problem to take into consideration.
  • Websites in professional use templating systems.
  • Commercial publishing platforms and content management systems ensure that you can show different text, different data using the same template.
  • When it's about controlling hundreds of articles, product pages for web shops, or user profiles in social networks, all of them potentially with different sizes, formats, rules for differing elements things can break, designs agreed upon can have unintended consequences and look much different than expected.

This is quite a problem to solve, but just doing without greeking text won't fix it. Using test items of real content and data in designs will help, but there's no guarantee that every oddity will be found and corrected. Do you want to be sure? Then a prototype or beta site with real content published from the real CMS is needed—but you’re not going that far until you go through an initial design cycle.