Штанга Leeb

| Штанга Leeb

Штанга Leeb:

Техніка, продумана до дрібниць

Варіанти штанги

Базові варіанти штанг шириною захвату від 18 до 30 метрів
Опція: зменшення робочої ширини шляхом складання зовнішніх крил

Стабільність в транспортному положенні і швидке складання

Швидке складання
Стабільність в транспортному положенні
Оптимальний захист форсунок
Транспортна ширина 2,55 м залежно від ширини шин / колії
Транспортна висота 3,80 – 4,00 м залежно від штанги і розміру шин

Штанга: 5-секційна зі зменшенням ширини захвату до 12 м

Штанга: 5-секційна зі зменшенням ширини захвату до 14 м

Штанга: 5-секційна зі зменшенням ширини захвату до 15 м

Базове оснащення

We use cookies and similar technologies on our website to process personal data, such as your IP address.
The cookies we use have two functions: Firstly, they are required for the basic functionality of our website. Second, cookies help us continuously improve our content for you. We do this by collecting and analysing pseudonymised data from website visitors.
We also share personal data with other companies. Some services also process personal data in the USA. Your data is processed, for example, either with your consent, which you can revoke at any time via the data protection settings in our Privacy Statement, or on the basis of our legitimate interest, which you can object to at any time.
Click here for an overview of all services used on our public website, our login portals and in the HORSCH shop. You can consent to the categories described, call up detailed information about each service or exercise your right to revoke your consent. For detailed information on how your data is handled, see our Privacy Statement and for information about us, visit our Imprint.

Privacy Statement | Imprint

These cookies are needed for a smooth operation of our website.

Name	Purpose	Lifetime	Type	Provider
CookieConsent	Saves your consent to using cookies.	1 year	HTML	Website
PHPSessID	Retains user states on all page requests	3 months	HTTP	php
fe_typo_user	This cookie is set by TYPO3 to uniquely identify a user. It offers the user better user guidance.	1 session	HTTP	TYPO3
be_typo_user	be_typo_user Is used to identify a backend session when a backend user logs into the TYPO3 backend or frontend.	1 session	HTTP	TYPO3
mtm_cookie_consent	Saves your consent to use matomo tracking.	1 session	HTTP	TYPO3
mtm_consent_removed	Saves your opt-out from tracking with Matomo.	1 month	HTTP	Matomo

Marketing cookies are used to track visitors on websites. They have the purpose of showing ads that are relevant and engaging for the user and therefore more valuable for publishers and third-party advertisers. Facebook, Google, SAP, Twitter, Youtube

Name	Purpose	Lifetime	Type	Provider
personalization_id	Marketing Used to determine the number of visitors who access our website via Twitter advertising content and can be used for targeted advertising.	2 years	HTTP	Google Tag Manager / Twitter
ANID	Marketing Used to play out advertisements.	10 years		Google
_fbc	Marketing / Tracking Used by Facebook to deliver a range of advertising products, such as real-time bidding from third parties.	3 months		Google Tag Manager / Facebook
datr	Marketing / Tracking Used to identify the web browser that connects to Facebook, irrespective of the logged-in user. This cookie plays a key role in Facebook’s security and integrity functions.	2 years		Google Tag Manager / Facebook
fr	Marketing / Tracking Provides information to Facebook for linking the functionality of the social plugin. It sends information to Facebook irrespective of whether you have a Facebook account or are logged in to the social network.	3 months	HTML	Google Tag Manager / Facebook
sb	Marketing / Tracking Provides information to Facebook for linking the functionality of the social plugin. It sends information to Facebook irrespective of whether you have a Facebook account or are logged in to the social network.	3 months	HTML	Google Tag Manager / Facebook
_fbp	Marketing / Tracking Used by Facebook to display a range of advertising products, such as real-time bids from third-party advertisers.	7 days	Pixel	Google Tag Manager / Facebook
_gcl_au	Marketing / Tracking Used by Google AdSense to learn about the effectiveness of advertising on websites that use their services.	1 day	HTML	Google Tag Manager / Google Ad
RUL	Marketing / Tracking Used by DoubleClick to determine whether website ads are displayed correctly.	1 year		Google DoubleClick
IDE	Marketing / Tracking Contains a randomly generated user ID. Google uses this ID to identify users across different web sites and domains and display personalised advertising.	1 year		Google DoubleClick
__adroll_fpc	Marketing / Tracking Used to identify visitors on repeat visits and across different devices. Allows the website to present relevant ads to the visitor.	1 session	HTTP	Adroll
NID	Marketing / Tracking Google’s cookies store information about user settings and information for Google services.	6 months		Google Ads Optimazation
__Secure-3PAPISID	Marketing / Functional Used for targeting to create a profile of the interests of website visitors and to display relevant, personalised Google advertising.	2 years		Google
__Secure-3PSID	Marketing / Functional Used by Google for targeting to create a profile of the interests of website visitors and to display relevant, personalised Google advertising.	2 years		Google
__Secure-3PSIDCC	Marketing / Functional Used by YouTube / Google for targeting to create a profile of the interests of website visitors and to display relevant, personalised Google advertising.	1 year		YouTube / Google
CONSENT	Marketing / Functional Save CONSENT cookie settings.	10 years		Google / YouTube
_ar_v4	Optimises ad delivery based on the combination of the user’s online behaviour and bids from advertisers to display user ads.	1 year	HTTP	Google DoubleClick
MYSAPSSO2	Used for targeting to create a profile of the interests of website visitors and to display relevant, personalised Google advertising.	1 session		SAP

Statistics cookies help website operators understand how visitors interact with websites by collecting and reporting anonymised information. Hotjar, Matomo, Google Analytics

Name	Purpose	Lifetime	Type	Provider
_ga	Statistics Used to distinguish unique users by assigning a randomly generated number as a client identifier.	2 years	HTML	Google Analytics
_ga_XXXXXXXXXX	Statistics Contains a unique identifier used by Google Analytics 4 to determine whether two different hits across browsing sessions belong to the same user.	2 years	HTML	Google Analytics
_gid	Statistics Provides functionality for counting and tracking page views.	1 day	HTML	Google Analytics
1P_JAR	Statistics Used by Google to display personalised advertising on Google websites based on current search queries and previous interactions.	1 month		Google
_hjAbsoluteSessionInProgress	Statistics Used to detect the first page-view session of a user. It has a true/false value.	30 minutes		Hotjar
_hjFirstSeen	Statistics This cookie is set to identify a new user’s first session. It has a true/false value that specifies whether Hotjar has seen this user for the first time. It is used by recording filters to identify new user sessions.	1 session		Hotjar
_hjTLDTest	Statistics When the Hotjar script is executed, we try to determine the most generic cookie path to use in place of the hostname of the device hosting the page. This is done to allow cookies to be shared across subdomains (if applicable). To determine the most generic path, we try to store the _hjTLDTest cookie for different URL substring alternatives until it fails. After this check, the cookie is removed.	1 session		Hotjar
_hjid	Statistics Hotjar cookie that is set the first time a customer lands on a page running the Hotjar script. It is used to persist the Hotjar user ID, which is unique for this page, in the browser. This ensures that the behaviour on subsequent visits to the same page is assigned to the same user ID.	365 days		Hotjar
_hjIncludedInPageviewSample	Statistics This cookie is set to tell Hotjar whether this user is included in the data sample defined by the site’s page-view limit.	30 minutes		Hotjar
_hjIncludedInSessionSample	Statistics This cookie is set to tell Hotjar whether this user is included in the data sample defined by the website’s daily session limit.	30 minutes		Hotjar
_pk_id	Statistics Saves a few user details such as the unique user ID.	13 months		Matomo
_pk_ses	Statistics Temporary cookie that temporarily stores data about a visit.	90 minutes		Matomo

Content from video and social media platforms is blocked by default. Consent to external media here to view all external media without further manual approval. Google Maps, Vimeo, Youtube