sensors Mode-S transponder

401068

ICAO 24-bit transponder address · allocated to United Kingdom

Currently assigned to G-ZAZU · DIAMOND DA-42 Guardian

Hex
401068
Octal
20010150
Decimal
4,198,504
Country
GB
Tail
G-ZAZU
Type
DA42
No current signal · last broadcast 20h ago
Flights observed
251
Distinct callsigns
20
Country
GB
Last broadcast
20h ago

Last known position

Most recent position reported by Mode-S 401068.

Country allocation

The ICAO 24-bit address 401068 falls within the block assigned to United Kingdom (GB) by ICAO Annex 10, Volume III. Every aircraft registered in United Kingdom receives a permanent address from this block at the time of registration; the address stays with the airframe even if the aircraft is re-registered to a different operator within the country.

Callsign history 20 distinct

Callsign Airline Flights Last seen
LDG50 - 25 2026-07-03
LDG17 - 25 2026-07-05
LDG26 - 21 2026-07-11
LDG39 - 20 2026-07-10
LDG33 - 20 2026-07-11
LDG14 - 18 2026-06-26
LDG48 - 16 2026-06-20
LDG32 - 16 2026-07-11
LDG23 - 16 2026-07-04
LDG04 - 15 2026-07-07
LDG18 - 9 2026-07-08
EXM63 - 9 2026-07-13
LDG03 - 8 2026-07-10
LDG25 - 7 2026-06-26
LDG01 - 7 2026-07-02
LDG12 - 4 2026-06-02
GZAZU - 4 2026-07-01
EXM50 - 3 2026-07-02
EXM44 - 2 2026-05-05
LDG37 - 1 2026-05-28

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-13 EXM63 - Jul 13, 10:35 UTCJul 13, 11:50 UTC1h 15m
2026-07-11 LDG32 - Jul 11, 15:40 UTCJul 11, 17:25 UTC1h 45m
2026-07-11 LDG33 - Jul 11, 10:00 UTCJul 11, 11:45 UTC1h 45m
2026-07-11 LDG26 - Jul 11, 06:55 UTCJul 11, 08:30 UTC1h 35m
2026-07-10 LDG39 OXF → OXF Jul 10, 18:55 UTCJul 10, 20:40 UTC1h 45m
2026-07-10 LDG32 - Jul 10, 16:25 UTCJul 10, 18:00 UTC1h 35m
2026-07-10 LDG32 OXF → OXF Jul 10, 12:50 UTCJul 10, 14:30 UTC1h 40m
2026-07-10 LDG03 - Jul 10, 08:05 UTCJul 10, 09:20 UTC1h 15m
2026-07-08 LDG18 - Jul 8, 15:50 UTCJul 8, 16:40 UTC50m
2026-07-08 LDG32 OXF → OXF Jul 8, 12:20 UTCJul 8, 14:00 UTC1h 40m
2026-07-08 LDG32 - Jul 8, 09:15 UTCJul 8, 11:00 UTC1h 45m
2026-07-08 LDG03 OXF → OXF Jul 8, 07:05 UTCJul 8, 08:10 UTC1h 5m
2026-07-07 LDG04 - Jul 7, 15:10 UTCJul 7, 16:55 UTC1h 45m
2026-07-07 LDG03 - Jul 7, 11:50 UTCJul 7, 13:10 UTC1h 20m
2026-07-07 LDG39 OXF → OXF Jul 7, 08:05 UTCJul 7, 10:05 UTC2h 0m
2026-07-06 LDG26 OXF → OXF Jul 6, 16:00 UTCJul 6, 18:15 UTC2h 15m
2026-07-06 LDG04 - Jul 6, 08:50 UTCJul 6, 09:40 UTC50m
2026-07-05 LDG17 OXF → OXF Jul 5, 14:15 UTCJul 5, 15:50 UTC1h 35m
2026-07-04 LDG00 OXF → OXF Jul 4, 14:35 UTCJul 4, 15:55 UTC1h 20m
2026-07-04 LDG23 - Jul 4, 11:30 UTCJul 4, 13:00 UTC1h 30m
2026-07-04 LDG23 - Jul 4, 08:35 UTCJul 4, 10:00 UTC1h 25m
2026-07-03 LDG26 - Jul 3, 17:35 UTCJul 3, 19:20 UTC1h 45m
2026-07-03 LDG50 - Jul 3, 13:20 UTCJul 3, 14:45 UTC1h 25m
2026-07-03 LDG50 - Jul 3, 09:50 UTCJul 3, 11:45 UTC1h 55m
2026-07-02 LDG32 - Jul 2, 18:25 UTCJul 2, 20:15 UTC1h 50m
2026-07-02 LDG03 - Jul 2, 16:20 UTCJul 2, 17:10 UTC50m
2026-07-02 LDG01 - Jul 2, 13:10 UTCJul 2, 14:40 UTC1h 30m
2026-07-02 EXM63 OXF → OXF Jul 2, 10:50 UTCJul 2, 12:15 UTC1h 25m
2026-07-02 EXM50 - Jul 2, 08:15 UTCJul 2, 09:55 UTC1h 40m
2026-07-01 GZAZU - Jul 1, 16:00 UTCJul 1, 17:00 UTC1h 0m
2026-06-28 LDG39 OXF → OXF Jun 28, 07:05 UTCJun 28, 07:40 UTC35m
2026-06-27 LDG23 - Jun 27, 17:14 UTCJun 27, 18:15 UTC1h 0m
2026-06-26 LDG14 - Jun 26, 19:00 UTCJun 26, 19:45 UTC45m
2026-06-26 LDG23 OXF → OXF Jun 26, 16:05 UTCJun 26, 17:19 UTC1h 15m
2026-06-26 LDG25 - Jun 26, 11:00 UTCJun 26, 11:49 UTC50m
2026-06-26 LDG39 - Jun 26, 08:00 UTCJun 26, 09:55 UTC1h 55m
2026-06-25 LDG14 - Jun 25, 17:09 UTCJun 25, 18:50 UTC1h 40m
2026-06-25 LDG04 - Jun 25, 14:04 UTCJun 25, 15:54 UTC1h 50m
2026-06-25 LDG50 - Jun 25, 10:59 UTCJun 25, 13:00 UTC2h 0m
2026-06-25 LDG04 - Jun 25, 07:25 UTCJun 25, 09:10 UTC1h 45m
2026-06-24 LDG14 - Jun 24, 18:44 UTCJun 24, 20:24 UTC1h 40m
2026-06-24 LDG39 - Jun 24, 16:40 UTCJun 24, 17:55 UTC1h 15m
2026-06-24 LDG23 - Jun 24, 14:09 UTCJun 24, 15:49 UTC1h 40m
2026-06-24 LDG04 - Jun 24, 07:15 UTCJun 24, 09:09 UTC1h 55m
2026-06-23 LDG32 - Jun 23, 18:55 UTCJun 23, 20:34 UTC1h 40m
2026-06-23 LDG32 - Jun 23, 16:59 UTCJun 23, 17:39 UTC40m
2026-06-23 LDG26 - Jun 23, 13:59 UTCJun 23, 15:44 UTC1h 45m
2026-06-23 EXM63 - Jun 23, 11:10 UTCJun 23, 12:09 UTC1h 0m
2026-06-23 EXM63 - Jun 23, 08:35 UTCJun 23, 09:54 UTC1h 20m
2026-06-22 LDG18 OXF → OXF Jun 22, 17:04 UTCJun 22, 17:25 UTC20m

About Mode-S

A Mode-S transponder code (also called an "ICAO 24-bit address" or "hex code") is a 6-character hexadecimal identifier permanently assigned to an aircraft when it's first registered. Unlike callsigns (which change with each flight) or registrations (which can change if an aircraft is sold internationally), the Mode-S address stays with the airframe for the life of the aircraft in that country.

Every ADS-B transmission from an aircraft includes its Mode-S address, making it the most reliable way to identify a specific airframe. Flight-tracking services like Apparatus use the Mode-S address as the primary key for tying position broadcasts, callsigns, and ownership records together.

Prefer a tail-number view? See the G-ZAZU page for operator, model, and routing details .

Mode-S 401068 frequently asked

What is Mode-S code 401068?
401068 is an ICAO 24-bit transponder address. Allocated to United Kingdom. Assigned to G-ZAZU.
Where is Mode-S 401068 registered?
Mode-S code 401068 is allocated to United Kingdom (GB). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 401068 broadcasting right now?
No active broadcast right now. Last signal was 20h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 401068, octal 20010150, decimal 4,198,504.
What flights does 401068 operate?
Mode-S 401068 has broadcast 20 distinct callsigns, including LDG50, LDG17, LDG26, LDG39, LDG33.