sensors Mode-S transponder
44046E
ICAO 24-bit transponder address · allocated to Austria
Currently assigned to OE-IGG · BOMBARDIER BD-700 Global 6000/6500
- Hex
- 44046E
- Octal
- 21002156
- Decimal
- 4,457,582
- Country
- AT
- Tail
- OE-IGG
- Type
- GLEX
- Flights observed
- 79
- Distinct callsigns
- 2
- Country
- AT
- Last broadcast
- 15h ago
Last known position
Country allocation
The ICAO 24-bit address 44046E 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 | GCK17 | - | Jul 17, 13:15 UTC | Jul 17, 14:20 UTC | 1h 5m |
| 2026-07-17 | GCK17 | - | Jul 17, 11:25 UTC | Jul 17, 12:15 UTC | 50m |
| 2026-07-17 | GCK17 | - | Jul 17, 06:45 UTC | Jul 17, 08:30 UTC | 1h 45m |
| 2026-07-15 | GCK17 | - | Jul 15, 08:40 UTC | Jul 15, 09:40 UTC | 1h 0m |
| 2026-07-14 | GCK17 | - | Jul 14, 22:15 UTC | Jul 15, 08:05 UTC | 9h 49m |
| 2026-07-13 | GCK17 | - | Jul 13, 15:05 UTC | Jul 13, 16:50 UTC | 1h 45m |
| 2026-07-12 | GCK17 | - | Jul 12, 09:40 UTC | Jul 12, 17:45 UTC | 8h 5m |
| 2026-07-12 | GCK17 | - | Jul 12, 06:25 UTC | Jul 12, 07:20 UTC | 55m |
| 2026-07-11 | GCK17 | - | Jul 11, 08:01 UTC | Jul 11, 09:30 UTC | 1h 30m |
| 2026-07-10 | GCK17 | - | Jul 10, 23:10 UTC | Jul 11, 07:10 UTC | 8h 0m |
| 2026-07-09 | GCK17 | - | Jul 9, 18:00 UTC | Jul 9, 18:40 UTC | 40m |
| 2026-07-09 | GCK17 | - | Jul 9, 14:35 UTC | Jul 9, 16:50 UTC | 2h 15m |
| 2026-07-09 | GCK17 | NQY → BGR | Jul 9, 08:10 UTC | Jul 9, 13:55 UTC | 5h 45m |
| 2026-07-09 | GCK17 | - | Jul 9, 05:20 UTC | Jul 9, 07:00 UTC | 1h 40m |
| 2026-07-07 | GCK17 | - | Jul 7, 08:40 UTC | Jul 7, 09:05 UTC | 25m |
| 2026-07-07 | GCK17 | - | Jul 7, 00:00 UTC | Jul 7, 07:10 UTC | 7h 10m |
| 2026-07-05 | GCK17 | - | Jul 5, 17:10 UTC | Jul 5, 19:35 UTC | 2h 25m |
| 2026-07-04 | GCK17 | NCE → FXE | Jul 4, 09:10 UTC | Jul 4, 19:25 UTC | 10h 15m |
| 2026-07-04 | GCK17 | - | Jul 4, 06:50 UTC | Jul 4, 07:55 UTC | 1h 5m |
| 2026-07-02 | GCK17 | - | Jul 2, 08:35 UTC | Jul 2, 09:30 UTC | 55m |
| 2026-07-02 | GCK17 | HPN → NCE | Jul 2, 00:25 UTC | Jul 2, 07:30 UTC | 7h 5m |
| 2026-06-29 | GCK17 | - | Jun 29, 20:09 UTC | Jun 29, 20:44 UTC | 35m |
| 2026-06-29 | GCK17 | DBV → TTN | Jun 29, 10:10 UTC | Jun 29, 18:55 UTC | 8h 45m |
| 2026-06-27 | GCK17 | - | Jun 27, 07:04 UTC | Jun 27, 08:05 UTC | 1h 0m |
| 2026-06-26 | GCK17 | - | Jun 26, 21:59 UTC | Jun 27, 06:40 UTC | 8h 40m |
| 2026-06-25 | GCK17 | - | Jun 25, 21:35 UTC | Jun 26, 00:05 UTC | 2h 30m |
| 2026-06-25 | GCK17 | - | Jun 25, 10:59 UTC | Jun 25, 20:25 UTC | 9h 25m |
| 2026-06-23 | GCK17 | - | Jun 23, 11:14 UTC | Jun 23, 19:39 UTC | 8h 25m |
| 2026-06-22 | GCK17 | - | Jun 22, 06:29 UTC | Jun 22, 16:20 UTC | 9h 50m |
| 2026-06-21 | GCK17 | - | Jun 21, 11:49 UTC | Jun 21, 12:19 UTC | 30m |
| 2026-06-21 | GCK17 | - | Jun 21, 09:59 UTC | Jun 21, 10:34 UTC | 35m |
| 2026-06-18 | GCK17 | - | Jun 18, 22:55 UTC | Jun 19, 06:54 UTC | 7h 59m |
| 2026-06-15 | GCK17 | - | Jun 15, 15:59 UTC | Jun 15, 19:14 UTC | 3h 15m |
| 2026-06-14 | GCK017 | - | Jun 14, 13:20 UTC | Jun 14, 14:30 UTC | 1h 10m |
| 2026-06-13 | GCK017 | BCN → LTN | Jun 13, 10:30 UTC | Jun 13, 12:15 UTC | 1h 45m |
| 2026-06-13 | GCK017 | VIE → BCN | Jun 13, 06:40 UTC | Jun 13, 08:30 UTC | 1h 50m |
| 2026-06-06 | GCK17 | STR → VIE | Jun 6, 12:04 UTC | Jun 6, 12:49 UTC | 45m |
| 2026-06-05 | GCK17 | - | Jun 5, 03:20 UTC | Jun 5, 05:10 UTC | 1h 50m |
| 2026-06-03 | GCK17 | - | Jun 3, 14:15 UTC | Jun 3, 16:20 UTC | 2h 5m |
| 2026-06-03 | GCK17 | - | Jun 3, 11:40 UTC | Jun 3, 11:50 UTC | 10m |
| 2026-06-01 | GCK17 | - | Jun 1, 21:50 UTC | Jun 2, 07:20 UTC | 9h 30m |
| 2026-05-30 | GCK17 | - | May 30, 02:06 UTC | May 30, 10:45 UTC | 8h 39m |
| 2026-05-28 | GCK17 | - | May 28, 10:25 UTC | May 28, 20:05 UTC | 9h 40m |
| 2026-05-27 | GCK17 | - | May 27, 11:15 UTC | May 27, 13:30 UTC | 2h 15m |
| 2026-05-27 | GCK17 | - | May 27, 03:24 UTC | May 27, 10:05 UTC | 6h 40m |
| 2026-05-25 | GCK17 | TEB → IAD | May 25, 22:44 UTC | May 25, 23:24 UTC | 40m |
| 2026-05-25 | GCK17 | - | May 25, 17:30 UTC | May 25, 21:09 UTC | 3h 39m |
| 2026-05-23 | GCK17 | - | May 23, 06:10 UTC | May 23, 08:55 UTC | 2h 45m |
| 2026-05-22 | GCK17 | - | May 22, 12:25 UTC | May 22, 13:10 UTC | 45m |
| 2026-05-18 | GCK17 | - | May 18, 18:00 UTC | May 18, 18:25 UTC | 25m |
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-IGG page for operator, model, and routing details .