KPS Summer Run 2019 Spendenübergabe

38.890 Kilometer für einen guten Zweck

24,165 miles for a good cause

News

KPS Summer Run 2019

Munich, December 16th 2019. Almost once around the world over the course of a summer for a good cause: From June 21 to September 2, 2019, KPS employees once again donned their running shoes and ran an impressive 24,165 miles. Together, they almost circumnavigated the globe - and in the process collected 9,724 euros in donations for initiatives in Munich, Barcelona, London, and Copenhagen. As in previous years, charities for children and young people were the main beneficiaries.

All miles that were run over summer 2019 by the nearly 200 runners were logged by the in-house myCompany app. Photos of the runs could also be posted to the app and the races of coworkers could be followed. Runners from Germany, Austria, Switzerland, England, Spain, Denmark, and Norway were therefore spurred on to complete 5,396 runs altogether. The top three runners each managed to run around 621 miles in the three months. For the first time this year, the initiative was also open to families of KPS employees and there was no lack of commitment on their part! A large number of employees took part, with some experienced runners among them, including marathon runners, but also a great many for whom running was not their usual daily activity.

 

The goal this year was to run 24,901 miles - equivalent to one circumnavigation of the equator. With the final figure standing at 24,165 miles, the KPS runners across seven countries almost reached their target - and did a lot of good in the process. In total, KPS donated 9,724 euros to four charities in Denmark, Germany, Great Britain, and Spain. Munich-based initiative IMMA e.V. which supports young people in crisis, Danish children's cancer charity boerne cancer fonden, Pallapupas hospital clowns from Barcelona, and children’s charity Jigsaw4u, which runs numerous projects in the UK, received 2,431 euros each. The checks were handed over to the charities at their premises by the top runners from the respective countries.

 

By the way, did you know that the father of all marathon runners is said to be Greek runner Pheidippides? When Greece was attacked by the Persians in 490 BC, Pheidippides jogged 152 miles from Athens to Sparta to seek help against the Persian superpower. Having failed to achieve his objective, he then returned to the beach of Marathon (running another 152 miles) and the Athens army. The marathon race as we know it today dates back to 1908 in England. A 25-mile course was planned that began at Windsor and finished in the newly built Olympic stadium in White City. This was until Her Majesty let it be known that she would like the race to start on the lawn at Windsor Castle. In order to gratify this royal whim, an extra mile had to be added to the beginning of the course. Then an additional 385 yards was appended to the end of the race so that it would finish under the Royal Box. This resulted in an extra mile and a bit for the marathon runners, and led to a tradition that survives to this day where marathon runners shout “God Save the Queen” as they pass Mile 25.

Spende an PALLAPUPAS

Privacy settings

We use cookies on our website. Some of them are essential, while others help us to improve this website and your experience. With your consent, we use cookies to analyse the usage of our website.

We also use cookies for marketing to help us measure the success of our marketing efforts. In the settings you will find detailed information about the individual cookies, and you can refuse the use of cookies.

You can change or revoke your selection at any time on any KPS.com page in the footer under Privacy Settings.

Essential Cookies

Essential cookies enable basic functions and are necessary for the proper functioning of the website.

Cookie Banner

  • Cookie Name: kps-privacy-settings
    Value: PrivacyLevel_0#a
    Storage Duration: 4 weeks
    Description: This cookie is required to save cookie settings. It is a purely technical cookie.

HubSpot:

  • Cookie Name: __hs_opt_out
    Storage Duration: 6 months
    Description: This cookie is used by the opt-in privacy policy to prompt the visitor to accept cookies again. It is set when you allow visitors to disable cookies. It contains the string "Yes" or "No."

  • Cookie Name: __hs_d_not_tracking
    Storage Duration: 6 months
    Description: This cookie can be set to prevent the tracking code from sending information to HubSpot. It contains the string "Yes."

  • Cookie Name: _hs_initial_opt
    Storage Duration: 7 days
    Description: This cookie is used to prevent banners from being displayed every time visitors access your website in strict mode. It contains the string "Yes" or "No."

  • Cookie Name: __hs_cookie_cat_pref
    Storage Duration: 6 months
    Description: This cookie is used to capture the categories a visitor has consented to. It contains data about those categories.

  • Cookie Name: __hs_gpc_banner_dismiss
    Storage Duration: 3 months
    Description: This cookie is used when the Global Privacy Control banner is dismissed.

  • Cookie Name: hs_ab_test
    Storage Duration: Until the end of the session
    Description: This cookie is used to ensure that visitors see the same version of an A/B test page they were shown previously. It contains the ID of the A/B test page and the ID of the variant selected for the visitor.

  • Cookie Name: __cfruid
    Storage Duration: Until the end of the session
    Description: This cookie is set by HubSpot's CDN provider in accordance with its rate-limiting policies.

  • Cookie Name: ___cfuvid
    Storage Duration: Until the end of the session
    Description: This cookie is set by HubSpot's CDN provider in accordance with its rate-limiting policies.

  • Cookie Name: ___cf_bm
    Storage Duration: Until the end of the session
    Description: This cookie is set by HubSpot's CDN provider in accordance with its rate-limiting policies.

Functional cookies

Functional cookies are used by third parties or publishers to display personalised advertisements. They do this by tracking visitors across websites.

Google Analytics

Cookie Name: _ga
Storage Duration: 2 years
Description: Used to distinguish between users.

Cookie Name: _gid
Storage Duration: 24 months
Description: Used to distinguish between users.

Cookie Name: _gat
Storage Duration: 1 minute
Description: Used to throttle the request rate. If Google Analytics is provided via Google Tag Manager, this cookie is named dc_gtm<property-ID>.

Cookie Name: hide-cookieinfo
Storage Duration: 30 days
Description: Cookie set for querying the cookies.

HubSpot

Cookie Name: __hstc
Storage Duration: 6 months
Description: The main cookie for visitor tracking. It contains the domain, the user token (hubspotutk), the first timestamp (of the first visit), the last timestamp (of the last visit), the current timestamp (for this visit), and the session count (increases with each subsequent session).

Cookie Name: hubspotutk
Storage Duration: 6 months
Description: This cookie tracks the identity of a visitor. This cookie is passed to the HubSpot software when submitting a form and is used for deduplicating contacts. It contains an opaque GUID to represent the current visitor.

Cookie Name: __hssc
Storage Duration: 30 minutes
Description: This cookie tracks sessions. It is used to determine whether the HubSpot software needs to increment the session count and timestamps in the __hstc cookie. It contains the domain, the number of page views (viewCount, increases with each page view in a session), and the session start timestamp.

Cookie Name: __hssrc
Storage Duration: End of session
Description: Whenever the HubSpot software changes the session cookie, this cookie is also set. It determines whether the visitor has restarted the browser. If this cookie is not present when HubSpot manages cookies, it is considered a new session. It contains the value "1" if present.

External media

Content from video platforms and social media platforms is blocked by default. If cookies from external media are accepted, access to this content no longer requires manual consent.

LinkedIn Tag

Cookie Name: bcookie
Storage Duration: 365 days
Description: Browser Identifier cookie to uniquely identify devices accessing LinkedIn to detect abuse on the platform and for diagnostic purposes.

Cookie Name: bscookie
Storage Duration: 365 days
Description: Used for remembering that a logged-in user is verified by two-factor authentication and has previously logged in.

Cookie Name: JSESSIONID
Storage Duration: Session
Description: Used for Cross-Site Request Forgery (CSRF) protection and URL signature validation.

Cookie Name: lang
Storage Duration: Session
Description: Used to remember a user's language setting to ensure LinkedIn.com displays in the language selected by the user in their settings.

Cookie Name: lidc
Storage Duration: 1 day
Description: To facilitate data center selection.

Cookie Name: sdsc
Storage Duration: Session
Description: Signed data service context cookie used for database routing to ensure consistency across all databases when a change is made. Used to ensure that user-inputted content is immediately available to the submitting user upon submission.

Cookie Name: li_gc
Storage Duration: 180 days
Description: Used to store consent of guests regarding the use of cookies for non-essential purposes.

Cookie Name: li_mc
Storage Duration: 180 days
Description: Used as a temporary cache to avoid database lookups for a member's consent for use of non-essential cookies and used for having consent information on the client side to enforce consent on the client side.

Cookie Name: UID
Storage Duration: 720 days
Description: Cookie used for market and user research.

Cookie Name: UserMatchHistory
Storage Duration: 30 days
Description: LinkedIn Ads ID syncing.

Cookie Name: AnalyticsSyncHistory
Storage Duration: 30 days
Description: Used to store information about the time a sync took place with the lms_analytics cookie.

Cookie Name: lms_ads
Storage Duration: 30 days
Description: Used to identify LinkedIn Members off LinkedIn for advertising.

Cookie Name: lms_analytics
Storage Duration: 30 days
Description: Used to identify LinkedIn Members off LinkedIn for analytics.

Cookie Name: li_fat_id
Storage Duration: 30 days
Description: Member indirect identifier for Members for conversion tracking, retargeting, and analytics.

Cookie Name: li_sugr
Storage Duration: 90 days
Description: Used to make a probabilistic match of a user's identity.

Cookie Name: _guid
Storage Duration: 90 days
Description: Used to identify a LinkedIn Member for advertising through Google Ads.

Cookie Name: BizographicsOptOut
Storage Duration: 10 years
Description: Used to determine opt-out status for non-members.

Cookie Name: li_giant
Storage Duration: 7 days
Description: Indirect identifier for groups of LinkedIn Members used for conversion tracking.

Cookie Name: oribi_cookie_test
Storage Duration: Session
Description: To determine if tracking can be enabled on the current domain.

Cookie Name: oribili_user_guid
Storage Duration: 365 days
Description: Used to count unique visitors to a website.

Cookie Name: ln_or
Storage Duration: 1 day
Description: Used to determine if Oribi analytics can be carried out on a specific domain.

Cookie Name: ar_debug
Storage Duration: Session
Description: Supports Google attribution reporting API integration to mitigate signal loss.

Lead Forensics

Cookie Name: __lfluuid
Storage Duration: 10 years
Description: The _lfuuid cookie allows a website to track visitor behavior on the sites on which the cookie is installed. Tracking is performed anonymously until a user identifies himself by submitting a form.

Changing privacy settings

Imprint

Data protection statement