sensors Mode-S transponder
45CEEF
ICAO 24-bit transponder address · allocated to Denmark
Currently assigned to OY-SWO · DASSAULT Falcon 2000
- Hex
- 45CEEF
- Octal
- 21347357
- Decimal
- 4,574,959
- Country
- DK
- Tail
- OY-SWO
- Type
- F2TH
- Flights observed
- 59
- Distinct callsigns
- 5
- Country
- DK
- Last broadcast
- 5d ago
Last known position
Country allocation
The ICAO 24-bit address 45CEEF 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 5 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-20 | BBB65 | - | Jul 20, 09:55 UTC | Jul 20, 12:55 UTC | 3h 0m |
| 2026-07-18 | BBB65P | ZRH → BLL | Jul 18, 18:25 UTC | Jul 18, 19:45 UTC | 1h 20m |
| 2026-07-18 | BBB65 | - | Jul 18, 13:35 UTC | Jul 18, 16:45 UTC | 3h 10m |
| 2026-07-18 | BBB65P | - | Jul 18, 10:40 UTC | Jul 18, 12:20 UTC | 1h 40m |
| 2026-07-16 | BBB65 | - | Jul 16, 07:40 UTC | Jul 16, 10:35 UTC | 2h 55m |
| 2026-07-15 | BBB65 | - | Jul 15, 14:45 UTC | Jul 15, 16:45 UTC | 2h 0m |
| 2026-07-15 | BBB65 | - | Jul 15, 10:40 UTC | Jul 15, 12:40 UTC | 2h 0m |
| 2026-07-15 | BBB65P | - | Jul 15, 08:45 UTC | Jul 15, 09:10 UTC | 25m |
| 2026-07-10 | BBB65P | - | Jul 10, 15:00 UTC | Jul 10, 15:30 UTC | 30m |
| 2026-07-10 | BBB65 | - | Jul 10, 12:15 UTC | Jul 10, 14:00 UTC | 1h 45m |
| 2026-07-10 | BBB65P | - | Jul 10, 07:35 UTC | Jul 10, 09:20 UTC | 1h 45m |
| 2026-07-08 | BBB65 | - | Jul 8, 08:10 UTC | Jul 8, 11:15 UTC | 3h 5m |
| 2026-07-07 | BBB65 | - | Jul 7, 12:10 UTC | Jul 7, 14:30 UTC | 2h 20m |
| 2026-07-07 | BBB65P | - | Jul 7, 08:35 UTC | Jul 7, 10:40 UTC | 2h 5m |
| 2026-07-06 | BBB65P | - | Jul 6, 09:20 UTC | Jul 6, 10:35 UTC | 1h 15m |
| 2026-07-04 | BBB65P | - | Jul 4, 15:45 UTC | Jul 4, 19:40 UTC | 3h 55m |
| 2026-07-04 | BBB65 | - | Jul 4, 09:40 UTC | Jul 4, 12:55 UTC | 3h 15m |
| 2026-07-03 | BBB65 | - | Jul 3, 15:00 UTC | Jul 3, 16:30 UTC | 1h 30m |
| 2026-07-03 | BBB65P | - | Jul 3, 13:40 UTC | Jul 3, 13:50 UTC | 10m |
| 2026-07-01 | BBB65 | - | Jul 1, 14:45 UTC | Jul 1, 16:45 UTC | 2h 0m |
| 2026-07-01 | BBB65P | - | Jul 1, 12:05 UTC | Jul 1, 13:55 UTC | 1h 50m |
| 2026-06-27 | BBB65P | - | Jun 27, 08:55 UTC | Jun 27, 09:44 UTC | 50m |
| 2026-06-27 | BBB65 | - | Jun 27, 06:25 UTC | Jun 27, 08:10 UTC | 1h 45m |
| 2026-06-27 | BBB65P | - | Jun 27, 04:00 UTC | Jun 27, 04:29 UTC | 30m |
| 2026-06-24 | BBB65P | - | Jun 24, 11:24 UTC | Jun 24, 13:40 UTC | 2h 15m |
| 2026-06-24 | BBB65 | - | Jun 24, 08:09 UTC | Jun 24, 10:19 UTC | 2h 10m |
| 2026-06-22 | BBB65P | IBZ → BLL | Jun 22, 14:24 UTC | Jun 22, 17:04 UTC | 2h 40m |
| 2026-06-22 | BBB65 | - | Jun 22, 09:40 UTC | Jun 22, 13:10 UTC | 3h 30m |
| 2026-06-22 | BBB65P | - | Jun 22, 06:54 UTC | Jun 22, 07:54 UTC | 1h 0m |
| 2026-06-20 | BBB76P | CFR → BLL | Jun 20, 11:05 UTC | Jun 20, 12:24 UTC | 1h 20m |
| 2026-06-20 | BBB65 | - | Jun 20, 09:19 UTC | Jun 20, 10:09 UTC | 50m |
| 2026-06-20 | BBB76P | - | Jun 20, 06:24 UTC | Jun 20, 07:59 UTC | 1h 35m |
| 2026-06-12 | BBB5 | - | Jun 12, 12:05 UTC | Jun 12, 13:10 UTC | 1h 5m |
| 2026-06-12 | BBB5 | - | Jun 12, 09:45 UTC | Jun 12, 11:05 UTC | 1h 20m |
| 2026-05-29 | BBB65P | BQH → BLL | May 29, 21:10 UTC | May 29, 22:20 UTC | 1h 10m |
| 2026-05-29 | BBB65 | - | May 29, 17:40 UTC | May 29, 20:35 UTC | 2h 55m |
| 2026-05-29 | BBB65P | - | May 29, 12:15 UTC | May 29, 14:50 UTC | 2h 35m |
| 2026-05-25 | BBB65 | - | May 25, 14:20 UTC | May 25, 16:55 UTC | 2h 35m |
| 2026-05-25 | BBB65P | - | May 25, 12:30 UTC | May 25, 13:00 UTC | 30m |
| 2026-05-25 | BBB65 | - | May 25, 10:25 UTC | May 25, 11:50 UTC | 1h 25m |
| 2026-05-25 | BBB65P | - | May 25, 05:50 UTC | May 25, 08:25 UTC | 2h 35m |
| 2026-05-17 | BBB65 | - | May 17, 11:01 UTC | May 17, 13:10 UTC | 2h 10m |
| 2026-05-14 | BBB65 | - | May 14, 06:40 UTC | May 14, 08:40 UTC | 2h 0m |
| 2026-05-10 | BBB65P | - | May 10, 14:54 UTC | May 10, 15:19 UTC | 25m |
| 2026-05-10 | BBB65 | - | May 10, 12:15 UTC | May 10, 14:09 UTC | 1h 55m |
| 2026-05-10 | BBB65P | - | May 10, 09:50 UTC | May 10, 11:10 UTC | 1h 20m |
| 2026-05-08 | BBB65 | - | May 8, 06:25 UTC | May 8, 07:14 UTC | 50m |
| 2026-05-07 | BBB65 | - | May 7, 13:00 UTC | May 7, 13:40 UTC | 40m |
| 2026-05-07 | BBB65 | - | May 7, 10:30 UTC | May 7, 11:55 UTC | 1h 25m |
| 2026-05-05 | BBB65P | - | May 5, 17:30 UTC | May 5, 18:45 UTC | 1h 15m |
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-SWO page for operator, model, and routing details .