Quicklinks
The company submits all necessary transport and container data with a status request for each container (step 1). The terminal reviews the information and checks whether transport is executable. Based on this, the terminal reports back with reliable status information (step 2) including specific instructions for processing (for example: bring documents). The haulage company or truck driver subsequently makes the booking for the entire transport (inbound and outbound containers) (step 3). The terminal allocates a specific pre-announcement number to each truck visit (step 4), which the driver must have ready upon arrival at the terminal.
Status | Processing codes | |
Not executable | 500–699 Incorrect data must be corrected by the truck driver or the haulage company. | |
Waiting | 300-499 Transport cannot be carried out yet. Automatic notification if status changes. | |
Executable | 100-299 The terminal transmits a pre-announcement number (PAN) to the truck driver or the haulage company. |
Haulage companies and forwarders can also be connected to the TR02 data interface using a software provider or systems vendor. Companies that have their own software can communicate directly via the electronic data interchange (EDI).
Further information about this can be found online at www.truckgate.de
A free web application is available to truck drivers. A valid trucker card is required in order to use the application. The application can be found online at
web.truckgate.de
For mobile devices, please use the link
app.truckgate.de
If you do not have a smartphone or any other access to the internet, you can use the self-service kiosks at different locations in the port of Hamburg.
The following table outlines the various transport cases and their specific features when pre-announcing them via TR02. The obligatory pre-announcement applies to all types of visit, apart from some particular transports which cannot be pre-announced. Please note that a further document check is required in some cases in the manual pre-check (MPC) even though the visit has been pre-announced. Certain types of visit must be indicated in the form of a flag in the status request.
Use case | Obligation | Flag | MPC | Note |
Standard Ccontainers | ||||
Delivery | Applies to export and transfer | |||
Collection | Applies to import and transfer | |||
Empty Depot Inbound | ( ) | Container with turn-in reference (only CTB) via MPC; in all other cases without MPC. | ||
Empty Depot Outboung | ||||
Special Containers | ||||
Reefer | ( ) | Collection of reefer container at CTA without MPC; in all other cases via MPC. Reefer containers are identified by ISO code; non-operating reefers must be indicated. | ||
OOG | ||||
Dangerous Goods | ||||
Other Special Cases | ||||
Customs - NCTS Transit Procedure T1 | ( ) | Collections in transit procedure at CTA without MPC; in all other cases via MPC. | ||
KLV rail (land-land transport) | ||||
BInspection (customs, veterinary office) | ||||
Container Freight Station (CFS) at CTB |
Answers to further questions on the obligatory pre-announcement can be found in the FAQ.