Cross Hydraulic Cylinder 3536DB - 3-1/2" x 36", 1-1/2" Rod 308-RAK1316 53 Brand TISCO Make Type O Ring Face Seal
USD337.60
USD366.60
Pay in 4 interest-free payments of $84.40 Learn more
Shipping Estimate
USA
- USA
- CAN
- USA
- CAN
Ships within 48 hours · Estimated delivery Nov 12 - Nov 17
Court notes
Description
Cross Hydraulic Cylinder 3536DB 3 1 2" x 36", 1 1 2" Rod 308 RAK1316 53 Brand TISCO Make Type O Ring Face Seal 53 Brand TISCO Make Type Model International Harvester Tractor 140 International Harvester Tractor 230 International Harvester Tractor 240 International Harvester Tractor H International Harvester Tractor M International Harvester Tractor O4 International Harvester Tractor OS4 International Harvester Tractor Super H International Harvester Tractor Super M International Harvester Tractor W4 Cast Iron Bearing Housing 4 Bolt Flange For bearing NA21031 1 1 2" Rod 5 Inch Cylinder Stroke 36 Inch Rod Diameter 1 1 2 Inch Clevis Pin Diameter 1 Inch Closed Center to Center Dimension 46 1 4 Inch Port Thread Size 1 2 NPT PSI Rating 2500 PSI Port Thread NPT Product Category Hydraulic Cylinder Cross Cylinder Series DB Brand Cross
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 Cross Hydraulic Cylinder 3536DB - 3-1/2" x 36", 1-1/2" Rod 308-RAK1316 53 Brand TISCO Make Type O Ring Face Seal
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.