sensors Mode-S transponder
45F424
ICAO 24-bit transponder address · allocated to Denmark
Currently assigned to C-168 · BOMBARDIER CL-600 Challenger
- Hex
- 45F424
- Octal
- 21372044
- Decimal
- 4,584,484
- Country
- DK
- Tail
- C-168
- Type
- CL60
- Flights observed
- 44
- Distinct callsigns
- 15
- Country
- DK
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address 45F424 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 15 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| DAF002 | - | 6 | 2026-07-14 |
| DAF6839 | - | 5 | 2026-06-23 |
| DAF4392 | - | 5 | 2026-04-22 |
| DAF6302 | - | 4 | 2026-05-07 |
| DAF5684 | - | 4 | 2026-06-16 |
| DAF6876 | - | 3 | 2026-06-30 |
| DAF4391 | - | 3 | 2026-04-15 |
| DAF6838 | - | 2 | 2026-07-14 |
| DAF6718 | - | 2 | 2026-06-09 |
| DAF4991 | - | 2 | 2026-07-08 |
| DAF4985 | - | 2 | 2026-05-19 |
| DAF4398 | - | 2 | 2026-06-01 |
| BULLT01 | - | 2 | 2026-06-24 |
| DAF7076 | - | 1 | 2026-07-15 |
| BULLT02 | - | 1 | 2026-06-17 |
Recent flights last 44
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-15 | DAF7076 | - | Jul 15, 08:45 UTC | Jul 15, 11:35 UTC | 2h 50m |
| 2026-07-14 | DAF6838 | CPH → AAL | Jul 14, 16:30 UTC | Jul 14, 17:10 UTC | 40m |
| 2026-07-14 | DAF002 | - | Jul 14, 13:45 UTC | Jul 14, 15:15 UTC | 1h 30m |
| 2026-07-13 | DAF002 | CPH → LBG | Jul 13, 11:35 UTC | Jul 13, 13:10 UTC | 1h 35m |
| 2026-07-13 | DAF6838 | - | Jul 13, 09:35 UTC | Jul 13, 10:05 UTC | 30m |
| 2026-07-08 | DAF4991 | CPH → AAL | Jul 8, 17:35 UTC | Jul 8, 18:10 UTC | 35m |
| 2026-07-08 | DAF002 | - | Jul 8, 13:35 UTC | Jul 8, 16:40 UTC | 3h 5m |
| 2026-07-07 | DAF002 | - | Jul 7, 11:15 UTC | Jul 7, 13:45 UTC | 2h 30m |
| 2026-07-07 | DAF4991 | - | Jul 7, 09:10 UTC | Jul 7, 09:45 UTC | 35m |
| 2026-06-30 | DAF6876 | - | Jun 30, 08:45 UTC | Jun 30, 09:15 UTC | 30m |
| 2026-06-30 | DAF6876 | RZE → CPH | Jun 30, 06:50 UTC | Jun 30, 08:10 UTC | 1h 20m |
| 2026-06-29 | DAF6876 | - | Jun 29, 15:09 UTC | Jun 29, 16:44 UTC | 1h 35m |
| 2026-06-24 | BULLT01 | - | Jun 24, 06:04 UTC | Jun 24, 06:55 UTC | 50m |
| 2026-06-23 | DAF6839 | - | Jun 23, 10:35 UTC | Jun 23, 10:59 UTC | 25m |
| 2026-06-22 | DAF6839 | - | Jun 22, 19:54 UTC | Jun 22, 22:34 UTC | 2h 40m |
| 2026-06-21 | DAF6839 | - | Jun 21, 21:05 UTC | Jun 22, 21:00 UTC | 23h 55m |
| 2026-06-21 | DAF6839 | - | Jun 21, 18:20 UTC | Jun 21, 21:29 UTC | 3h 10m |
| 2026-06-21 | DAF6839 | - | Jun 21, 16:10 UTC | Jun 21, 16:39 UTC | 30m |
| 2026-06-17 | BULLT02 | - | Jun 17, 08:35 UTC | Jun 17, 09:25 UTC | 50m |
| 2026-06-16 | DAF5684 | - | Jun 16, 11:45 UTC | Jun 16, 12:20 UTC | 35m |
| 2026-06-16 | DAF5684 | - | Jun 16, 09:25 UTC | Jun 16, 10:40 UTC | 1h 15m |
| 2026-06-15 | DAF5684 | - | Jun 15, 06:40 UTC | Jun 15, 07:55 UTC | 1h 15m |
| 2026-06-15 | DAF5684 | - | Jun 15, 04:30 UTC | Jun 15, 05:04 UTC | 35m |
| 2026-06-09 | DAF6718 | - | Jun 9, 10:30 UTC | Jun 9, 11:50 UTC | 1h 20m |
| 2026-06-04 | DAF6718 | - | Jun 4, 07:05 UTC | Jun 4, 08:05 UTC | 1h 0m |
| 2026-06-01 | DAF4398 | - | Jun 1, 14:00 UTC | Jun 1, 16:20 UTC | 2h 20m |
| 2026-05-29 | DAF4398 | - | May 29, 09:40 UTC | May 29, 10:45 UTC | 1h 5m |
| 2026-05-27 | BULLT01 | - | May 27, 08:15 UTC | May 27, 09:40 UTC | 1h 25m |
| 2026-05-19 | DAF4985 | - | May 19, 19:15 UTC | May 19, 19:45 UTC | 30m |
| 2026-05-19 | DAF002 | - | May 19, 17:00 UTC | May 19, 17:50 UTC | 50m |
| 2026-05-19 | DAF002 | - | May 19, 07:05 UTC | May 19, 07:55 UTC | 50m |
| 2026-05-18 | DAF4985 | - | May 18, 13:05 UTC | May 18, 13:35 UTC | 30m |
| 2026-05-07 | DAF6302 | - | May 7, 15:50 UTC | May 7, 16:05 UTC | 15m |
| 2026-05-07 | DAF6302 | - | May 7, 12:15 UTC | May 7, 14:55 UTC | 2h 40m |
| 2026-05-04 | DAF6302 | - | May 4, 10:45 UTC | May 4, 13:45 UTC | 3h 0m |
| 2026-05-04 | DAF6302 | - | May 4, 09:30 UTC | May 4, 09:45 UTC | 15m |
| 2026-04-22 | DAF4392 | - | Apr 22, 12:35 UTC | Apr 22, 17:10 UTC | 4h 35m |
| 2026-04-17 | DAF4392 | - | Apr 17, 14:40 UTC | Apr 17, 15:00 UTC | 19m |
| 2026-04-17 | DAF4392 | - | Apr 17, 13:30 UTC | Apr 17, 13:55 UTC | 25m |
| 2026-04-17 | DAF4392 | - | Apr 17, 11:20 UTC | Apr 17, 11:35 UTC | 15m |
| 2026-04-17 | DAF4392 | - | Apr 17, 10:50 UTC | Apr 17, 11:15 UTC | 25m |
| 2026-04-15 | DAF4391 | - | Apr 15, 19:05 UTC | Apr 15, 20:00 UTC | 55m |
| 2026-04-15 | DAF4391 | - | Apr 15, 17:25 UTC | Apr 15, 19:00 UTC | 1h 35m |
| 2026-04-13 | DAF4391 | - | Apr 13, 12:30 UTC | Apr 13, 13:15 UTC | 45m |
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 C-168 page for operator, model, and routing details .