sensors Mode-S transponder
440325
ICAO 24-bit transponder address · allocated to Austria
Currently assigned to OE-LGG · BOMBARDIER BD-700 Global 7000/7500
- Hex
- 440325
- Octal
- 21001445
- Decimal
- 4,457,253
- Country
- AT
- Tail
- OE-LGG
- Type
- GL7T
- Flights observed
- 79
- Distinct callsigns
- 2
- Country
- AT
- Last broadcast
- 15h ago
Last known position
Country allocation
The ICAO 24-bit address 440325 falls within the block assigned to Austria (AT) by ICAO Annex 10, Volume III. Every aircraft registered in Austria 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 2 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | GCK19X | - | Jul 17, 10:00 UTC | Jul 17, 11:45 UTC | 1h 45m |
| 2026-07-15 | GCK19X | - | Jul 15, 15:10 UTC | Jul 15, 16:50 UTC | 1h 40m |
| 2026-07-15 | GCK19X | - | Jul 15, 11:20 UTC | Jul 15, 13:45 UTC | 2h 25m |
| 2026-07-15 | GCK19X | - | Jul 15, 08:20 UTC | Jul 15, 10:00 UTC | 1h 40m |
| 2026-07-11 | GCK19X | - | Jul 11, 22:50 UTC | Jul 12, 07:01 UTC | 8h 10m |
| 2026-07-10 | GCK19X | - | Jul 10, 10:15 UTC | Jul 10, 19:30 UTC | 9h 15m |
| 2026-07-08 | GCK19X | - | Jul 8, 21:15 UTC | Jul 9, 05:40 UTC | 8h 25m |
| 2026-07-07 | GCK19X | - | Jul 7, 22:45 UTC | Jul 7, 23:30 UTC | 45m |
| 2026-07-06 | GCK19X | - | Jul 6, 21:35 UTC | Jul 6, 22:45 UTC | 1h 10m |
| 2026-07-06 | GCK19X | - | Jul 6, 19:50 UTC | Jul 6, 20:30 UTC | 40m |
| 2026-07-06 | GCK19X | - | Jul 6, 11:20 UTC | Jul 6, 13:20 UTC | 2h 0m |
| 2026-07-05 | GCK19X | NCE → MAH | Jul 5, 15:05 UTC | Jul 5, 15:50 UTC | 45m |
| 2026-07-03 | GCK19X | - | Jul 3, 23:50 UTC | Jul 4, 06:30 UTC | 6h 40m |
| 2026-07-02 | GCK19X | FTY → HPN | Jul 2, 15:45 UTC | Jul 2, 17:35 UTC | 1h 50m |
| 2026-06-29 | GCK19X | - | Jun 29, 02:30 UTC | Jun 29, 12:24 UTC | 9h 55m |
| 2026-06-25 | GCK19X | - | Jun 25, 21:20 UTC | Jun 25, 21:29 UTC | 10m |
| 2026-06-25 | GCK19X | FCO → LJU | Jun 25, 19:49 UTC | Jun 25, 20:45 UTC | 55m |
| 2026-06-25 | GCK19X | - | Jun 25, 07:59 UTC | Jun 25, 08:45 UTC | 45m |
| 2026-06-23 | GCK19X | - | Jun 23, 20:24 UTC | Jun 24, 05:09 UTC | 8h 45m |
| 2026-06-23 | GCK19X | - | Jun 23, 02:09 UTC | Jun 23, 02:24 UTC | 15m |
| 2026-06-22 | GCK19X | - | Jun 22, 19:40 UTC | Jun 22, 23:35 UTC | 3h 55m |
| 2026-06-21 | GCK019X | - | Jun 21, 07:55 UTC | Jun 21, 18:25 UTC | 10h 30m |
| 2026-06-20 | GCK019X | - | Jun 20, 09:34 UTC | Jun 20, 12:24 UTC | 2h 50m |
| 2026-06-20 | GCK19X | - | Jun 20, 06:39 UTC | Jun 20, 07:19 UTC | 40m |
| 2026-06-17 | GCK19X | - | Jun 17, 18:00 UTC | Jun 17, 19:00 UTC | 1h 0m |
| 2026-06-17 | GCK19X | - | Jun 17, 05:45 UTC | Jun 17, 07:15 UTC | 1h 30m |
| 2026-06-15 | GCK19X | - | Jun 15, 11:19 UTC | Jun 15, 12:10 UTC | 50m |
| 2026-06-15 | GCK19X | SVQ → CIA | Jun 15, 08:29 UTC | Jun 15, 10:30 UTC | 2h 0m |
| 2026-06-15 | GCK019X | - | Jun 15, 06:40 UTC | Jun 15, 07:00 UTC | 20m |
| 2026-06-13 | GCK019X | - | Jun 13, 13:05 UTC | Jun 13, 19:10 UTC | 6h 5m |
| 2026-06-12 | GCK19X | - | Jun 12, 16:00 UTC | Jun 12, 16:45 UTC | 45m |
| 2026-06-11 | GCK19X | - | Jun 11, 11:20 UTC | Jun 11, 18:25 UTC | 7h 5m |
| 2026-06-11 | GCK19X | - | Jun 11, 08:00 UTC | Jun 11, 09:40 UTC | 1h 40m |
| 2026-06-10 | GCK19X | - | Jun 10, 15:30 UTC | Jun 10, 16:00 UTC | 30m |
| 2026-06-10 | GCK19X | - | Jun 10, 05:35 UTC | Jun 10, 06:05 UTC | 30m |
| 2026-06-07 | GCK19X | - | Jun 7, 15:10 UTC | Jun 7, 16:15 UTC | 1h 5m |
| 2026-06-07 | GCK19X | VIE → LBG | Jun 7, 12:35 UTC | Jun 7, 14:05 UTC | 1h 30m |
| 2026-06-07 | GCK19X | - | Jun 7, 10:00 UTC | Jun 7, 11:15 UTC | 1h 15m |
| 2026-06-06 | GCK19X | - | Jun 6, 01:35 UTC | Jun 6, 12:49 UTC | 11h 15m |
| 2026-06-02 | GCK19X | - | Jun 2, 22:00 UTC | Jun 3, 02:15 UTC | 4h 15m |
| 2026-06-02 | GCK19X | - | Jun 2, 18:35 UTC | Jun 2, 20:45 UTC | 2h 10m |
| 2026-06-01 | GCK19X | - | Jun 1, 11:20 UTC | Jun 1, 20:05 UTC | 8h 45m |
| 2026-05-30 | GCK19X | - | May 30, 22:50 UTC | May 31, 01:11 UTC | 2h 21m |
| 2026-05-28 | GCK19X | - | May 28, 19:45 UTC | May 28, 20:30 UTC | 45m |
| 2026-05-27 | GCK19X | - | May 27, 15:00 UTC | May 27, 23:45 UTC | 8h 45m |
| 2026-05-27 | GCK19X | - | May 27, 11:45 UTC | May 27, 13:30 UTC | 1h 45m |
| 2026-05-26 | GCK19X | NCE → FAB | May 26, 07:45 UTC | May 26, 09:15 UTC | 1h 30m |
| 2026-05-23 | GCK19X | MTY → NCE | May 23, 11:15 UTC | May 23, 21:00 UTC | 9h 46m |
| 2026-05-21 | GCK19X | - | May 21, 13:55 UTC | May 21, 19:35 UTC | 5h 40m |
| 2026-05-20 | GCK19X | - | May 20, 09:05 UTC | May 20, 11:10 UTC | 2h 5m |
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 OE-LGG page for operator, model, and routing details .