sensors Mode-S transponder
459744
ICAO 24-bit transponder address · allocated to Denmark
Currently assigned to OY-EZD · DASSAULT Falcon 2000
- Hex
- 459744
- Octal
- 21313504
- Decimal
- 4,560,708
- Country
- DK
- Tail
- OY-EZD
- Type
- F2TH
- Flights observed
- 43
- Distinct callsigns
- 16
- Country
- DK
- Last broadcast
- 52m ago
Current position
Country allocation
The ICAO 24-bit address 459744 falls within the block assigned to Denmark (DK) by ICAO Annex 10, Volume III. Every aircraft registered in Denmark 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 16 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| MMD6780 | - | 6 | 2026-04-16 |
| MMD6849 | - | 5 | 2026-05-17 |
| MMD6874 | - | 3 | 2026-05-30 |
| MMD6833 | Air Alsie | 3 | 2026-05-05 |
| MMD6812 | - | 3 | 2026-04-27 |
| MMD6810 | - | 3 | 2026-04-23 |
| MMD6777 | - | 3 | 2026-04-22 |
| MMD6676 | - | 3 | 2026-04-22 |
| MMD9183 | - | 2 | 2026-06-01 |
| MMD6813 | Air Alsie | 2 | 2026-05-03 |
| MMD6803 | - | 2 | 2026-06-02 |
| MMD6797 | - | 2 | 2026-05-27 |
| MMD1394 | - | 2 | 2026-05-25 |
| MMD1393 | - | 2 | 2026-05-17 |
| MMD6885 | - | 1 | 2026-06-02 |
| MMD6669 | - | 1 | 2026-04-29 |
Recent flights last 43
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | MMD6885 | - | Jun 2, 16:45 UTC | Jun 2, 18:15 UTC | 1h 30m |
| 2026-06-02 | MMD6803 | - | Jun 2, 15:10 UTC | Jun 2, 16:10 UTC | 1h 0m |
| 2026-06-02 | MMD6803 | - | Jun 2, 11:55 UTC | Jun 2, 13:45 UTC | 1h 50m |
| 2026-06-01 | MMD9183 | - | Jun 1, 13:20 UTC | Jun 1, 13:40 UTC | 20m |
| 2026-06-01 | MMD9183 | - | Jun 1, 11:55 UTC | Jun 1, 12:10 UTC | 15m |
| 2026-05-30 | MMD6874 | ZRH → CPH | May 30, 14:05 UTC | May 30, 15:30 UTC | 1h 25m |
| 2026-05-30 | MMD6874 | - | May 30, 11:15 UTC | May 30, 13:00 UTC | 1h 45m |
| 2026-05-30 | MMD6874 | - | May 30, 09:10 UTC | May 30, 09:55 UTC | 45m |
| 2026-05-27 | MMD6797 | - | May 27, 14:35 UTC | May 27, 16:20 UTC | 1h 45m |
| 2026-05-26 | MMD6797 | - | May 26, 09:09 UTC | May 26, 10:50 UTC | 1h 40m |
| 2026-05-25 | MMD1394 | - | May 25, 15:50 UTC | May 25, 16:10 UTC | 20m |
| 2026-05-18 | MMD1394 | - | May 18, 05:55 UTC | May 18, 06:20 UTC | 25m |
| 2026-05-17 | MMD1393 | - | May 17, 12:50 UTC | May 17, 15:01 UTC | 2h 10m |
| 2026-05-17 | MMD6849 | - | May 17, 08:00 UTC | May 17, 11:50 UTC | 3h 50m |
| 2026-05-14 | MMD6849 | - | May 14, 17:45 UTC | May 14, 18:00 UTC | 15m |
| 2026-05-14 | MMD6849 | - | May 14, 13:15 UTC | May 14, 15:25 UTC | 2h 10m |
| 2026-05-14 | MMD6849 | LIN → LIN | May 14, 13:01 UTC | May 14, 13:05 UTC | 5m |
| 2026-05-14 | MMD6849 | - | May 14, 10:25 UTC | May 14, 11:01 UTC | 35m |
| 2026-05-13 | MMD1393 | - | May 13, 11:50 UTC | May 13, 13:50 UTC | 2h 0m |
| 2026-05-05 | MMD6833 | NCE → TEB | May 5, 13:25 UTC | May 5, 14:35 UTC | 1h 10m |
| 2026-05-05 | MMD6833 | NCE → TEB | May 5, 06:45 UTC | May 5, 08:35 UTC | 1h 50m |
| 2026-05-05 | MMD6833 | NCE → TEB | May 5, 04:40 UTC | May 5, 05:30 UTC | 50m |
| 2026-05-03 | MMD6813 | SGD → NCE | May 3, 13:00 UTC | May 3, 15:00 UTC | 2h 0m |
| 2026-04-30 | MMD6813 | SGD → NCE | Apr 30, 10:30 UTC | Apr 30, 12:25 UTC | 1h 55m |
| 2026-04-29 | MMD6669 | - | Apr 29, 05:05 UTC | Apr 29, 23:50 UTC | 18h 45m |
| 2026-04-27 | MMD6812 | IAD → LBG | Apr 27, 13:20 UTC | Apr 27, 21:05 UTC | 7h 45m |
| 2026-04-24 | MMD6812 | - | Apr 24, 15:00 UTC | Apr 24, 22:40 UTC | 7h 40m |
| 2026-04-24 | MMD6812 | - | Apr 24, 12:20 UTC | Apr 24, 13:40 UTC | 1h 20m |
| 2026-04-23 | MMD6810 | - | Apr 23, 13:00 UTC | Apr 23, 15:25 UTC | 2h 25m |
| 2026-04-23 | MMD6810 | - | Apr 23, 08:01 UTC | Apr 23, 09:05 UTC | 1h 5m |
| 2026-04-23 | MMD6810 | BMA → BGO | Apr 23, 06:01 UTC | Apr 23, 07:10 UTC | 1h 10m |
| 2026-04-22 | MMD6676 | - | Apr 22, 13:20 UTC | Apr 22, 17:20 UTC | 4h 0m |
| 2026-04-22 | MMD6777 | - | Apr 22, 08:55 UTC | Apr 22, 11:10 UTC | 2h 15m |
| 2026-04-20 | MMD6777 | BCN → ZRH | Apr 20, 11:55 UTC | Apr 20, 13:20 UTC | 1h 25m |
| 2026-04-19 | MMD6777 | - | Apr 19, 17:30 UTC | Apr 20, 10:50 UTC | 17h 20m |
| 2026-04-19 | MMD6676 | - | Apr 19, 11:45 UTC | Apr 19, 15:45 UTC | 4h 0m |
| 2026-04-17 | MMD6676 | - | Apr 17, 13:30 UTC | Apr 17, 14:30 UTC | 1h 0m |
| 2026-04-16 | MMD6780 | - | Apr 16, 21:14 UTC | Apr 16, 22:34 UTC | 1h 20m |
| 2026-04-16 | MMD6780 | - | Apr 16, 19:40 UTC | Apr 16, 21:10 UTC | 1h 30m |
| 2026-04-16 | MMD6780 | - | Apr 16, 17:40 UTC | Apr 16, 18:20 UTC | 40m |
| 2026-04-15 | MMD6780 | - | Apr 15, 20:05 UTC | Apr 15, 20:45 UTC | 40m |
| 2026-04-14 | MMD6780 | - | Apr 14, 14:50 UTC | Apr 14, 16:45 UTC | 1h 55m |
| 2026-04-14 | MMD6780 | - | Apr 14, 13:05 UTC | Apr 14, 14:45 UTC | 1h 40m |
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 OY-EZD page for operator, model, and routing details .