Talk:Lufthansa Cargo

Page contents not supported in other languages.
Source: Wikipedia, the free encyclopedia.

.

Fair use rationale for Image:Lhcargo.png

fair use
.

Please go to

Wikipedia:Fair use rationale guideline
is an easy way to insure that your image is in compliance with Wikipedia policy, but remember that you must complete the template. Do not simply insert a blank template on an image page.

If there is other other fair use media, consider checking that you have specified the fair use rationale on the other images used on this page. Note that any fair use images uploaded after 4 May, 2006, and lacking such an explanation will be deleted one week after they have been uploaded, as described on criteria for speedy deletion. If you have any questions please ask them at the Media copyright questions page. Thank you.BetacommandBot 04:02, 6 June 2007 (UTC)[reply]

C-TPAT certification

IS LH CTPAT certified in the USA ?

208.254.100.1 (talk) 16:05, 22 June 2009 (UTC)[reply]

C-TPAT certification

IS LH CTPAT certified in the USA ?

208.254.100.1 (talk) 16:05, 22 June 2009 (UTC)[reply]

External links modified

Hello fellow Wikipedians,

I have just modified one external link on Lufthansa Cargo. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

This message was posted before February 2018.

regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check
}} (last update: 18 January 2022).

Cheers.—InternetArchiveBot (Report bug) 12:20, 27 May 2017 (UTC)[reply]

External links modified

Hello fellow Wikipedians,

I have just modified 3 external links on Lufthansa Cargo. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

This message was posted before February 2018.

regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check
}} (last update: 18 January 2022).

Cheers.—InternetArchiveBot (Report bug) 12:46, 8 January 2018 (UTC)[reply]

Request edit on 12 January 2022


  • What I think should be changed:

A subsection with Lufthansa Cargo subsidiaries. One of its subsidiaries, is heyworld.

  • Why it should be changed:

As Lufthansa Cargo has subsidiary companies, which would not be entitled to have their pages, I strongly believe this page should have a subsection with these subsidiaries.

  • References supporting the possible change (format using the "cite" button):

heyworld GmbH was founded in 2019 as a fully owned subsidiary of Lufthansa Cargo, specialized in cross-border eCommerce logistics, with its base at Frankfurt Airport. [1] [2]

In 2021, Lufthansa Cargo announced it will introduce two Airbus freighters to be used on intra-European services, targeting the e-commerce market. [3]

In 2021, Lufthansa Cargo announced that heyworld and time:matters, both of its subsidiaries, would benefit from the A321P2F capacity. [4]

Bo6dan at heyworld (talk) 14:40, 12 January 2022 (UTC)[reply]

Hi
reliable secondary source? Thanks! CX Zoom[he/him] (let's talkCL) 22:18, 11 April 2022 (UTC)[reply
]
~StyyxTalk? 20:01, 19 September 2022 (UTC)[reply
]