sensors Mode-S transponder
458C4B
ICAO 24-bit transponder address · allocated to Denmark
Currently assigned to OY-CBK · PILATUS PC-12
- Hex
- 458C4B
- Octal
- 21306113
- Decimal
- 4,557,899
- Country
- DK
- Tail
- OY-CBK
- Type
- PC12
- Flights observed
- 60
- Distinct callsigns
- 2
- Country
- DK
- Last broadcast
- 37m ago
Last known position
Country allocation
The ICAO 24-bit address 458C4B 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 2 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | OYCBK | - | Jul 14, 13:00 UTC | Jul 14, 14:45 UTC | 1h 45m |
| 2026-07-10 | OYCBK | - | Jul 10, 14:25 UTC | Jul 10, 14:40 UTC | 15m |
| 2026-07-10 | OYCBK | - | Jul 10, 07:15 UTC | Jul 10, 08:05 UTC | 50m |
| 2026-07-06 | FXT12K | - | Jul 6, 12:30 UTC | Jul 6, 13:50 UTC | 1h 20m |
| 2026-07-06 | FXT12K | - | Jul 6, 11:05 UTC | Jul 6, 12:05 UTC | 1h 0m |
| 2026-07-06 | FXT12K | - | Jul 6, 08:35 UTC | Jul 6, 10:00 UTC | 1h 25m |
| 2026-07-04 | OYCBK | - | Jul 4, 08:30 UTC | Jul 4, 10:10 UTC | 1h 40m |
| 2026-07-03 | OYCBK | - | Jul 3, 13:20 UTC | Jul 3, 14:45 UTC | 1h 25m |
| 2026-06-30 | OYCBK | - | Jun 30, 16:45 UTC | Jun 30, 18:10 UTC | 1h 25m |
| 2026-06-30 | OYCBK | - | Jun 30, 10:35 UTC | Jun 30, 12:15 UTC | 1h 40m |
| 2026-06-29 | FXT12K | - | Jun 29, 02:35 UTC | Jun 29, 03:10 UTC | 35m |
| 2026-06-28 | FXT12K | - | Jun 28, 18:40 UTC | Jun 28, 19:14 UTC | 35m |
| 2026-06-26 | FXT12K | - | Jun 26, 16:24 UTC | Jun 26, 16:49 UTC | 25m |
| 2026-06-25 | FXT12K | - | Jun 25, 08:55 UTC | Jun 25, 09:29 UTC | 35m |
| 2026-06-18 | OYCBK | - | Jun 18, 09:50 UTC | Jun 18, 12:05 UTC | 2h 15m |
| 2026-06-16 | OYCBK | - | Jun 16, 10:55 UTC | Jun 16, 11:45 UTC | 50m |
| 2026-06-16 | OYCBK | BER → KZG | Jun 16, 07:55 UTC | Jun 16, 08:55 UTC | 1h 0m |
| 2026-06-15 | OYCBK | - | Jun 15, 12:10 UTC | Jun 15, 13:00 UTC | 50m |
| 2026-06-14 | OYCBK | - | Jun 14, 11:15 UTC | Jun 14, 13:35 UTC | 2h 20m |
| 2026-06-12 | OYCBK | - | Jun 12, 06:05 UTC | Jun 12, 08:35 UTC | 2h 30m |
| 2026-06-08 | OYCBK | - | Jun 8, 08:55 UTC | Jun 8, 12:30 UTC | 3h 35m |
| 2026-06-05 | OYCBK | - | Jun 5, 11:35 UTC | Jun 5, 13:05 UTC | 1h 30m |
| 2026-06-05 | OYCBK | - | Jun 5, 09:10 UTC | Jun 5, 10:45 UTC | 1h 35m |
| 2026-05-31 | OYCBK | - | May 31, 15:25 UTC | May 31, 17:30 UTC | 2h 5m |
| 2026-05-29 | OYCBK | - | May 29, 14:35 UTC | May 29, 16:25 UTC | 1h 50m |
| 2026-05-22 | OYCBK | STR → RKE | May 22, 12:10 UTC | May 22, 14:00 UTC | 1h 50m |
| 2026-05-22 | OYCBK | OBF → STR | May 22, 06:50 UTC | May 22, 07:20 UTC | 30m |
| 2026-05-20 | OYCBK | - | May 20, 12:55 UTC | May 20, 15:00 UTC | 2h 5m |
| 2026-05-19 | FXT12K | GWT → ZHI | May 19, 16:40 UTC | May 19, 18:35 UTC | 1h 55m |
| 2026-05-19 | FXT12K | GWT → ZHI | May 19, 10:35 UTC | May 19, 12:50 UTC | 2h 15m |
| 2026-05-19 | FXT12K | GWT → ZHI | May 19, 07:40 UTC | May 19, 08:00 UTC | 20m |
| 2026-05-18 | FXT12K | GWT → ZHI | May 18, 14:05 UTC | May 18, 15:25 UTC | 1h 20m |
| 2026-05-18 | FXT12K | GWT → ZHI | May 18, 06:20 UTC | May 18, 07:50 UTC | 1h 30m |
| 2026-05-17 | OYCBK | - | May 17, 12:10 UTC | May 17, 14:15 UTC | 2h 5m |
| 2026-05-13 | OYCBK | - | May 13, 15:45 UTC | May 13, 18:10 UTC | 2h 25m |
| 2026-05-12 | OYCBK | - | May 12, 13:55 UTC | May 12, 15:20 UTC | 1h 25m |
| 2026-05-12 | OYCBK | - | May 12, 07:55 UTC | May 12, 10:00 UTC | 2h 5m |
| 2026-05-11 | OYCBK | - | May 11, 05:55 UTC | May 11, 08:30 UTC | 2h 35m |
| 2026-05-10 | OYCBK | - | May 10, 13:35 UTC | May 10, 15:29 UTC | 1h 55m |
| 2026-05-10 | OYCBK | - | May 10, 10:35 UTC | May 10, 11:45 UTC | 1h 10m |
| 2026-05-09 | OYCBK | - | May 9, 11:20 UTC | May 9, 13:30 UTC | 2h 10m |
| 2026-05-06 | OYCBK | - | May 6, 11:25 UTC | May 6, 13:25 UTC | 2h 0m |
| 2026-05-04 | OYCBK | - | May 4, 15:30 UTC | May 4, 16:25 UTC | 55m |
| 2026-05-03 | OYCBK | - | May 3, 14:45 UTC | May 3, 16:25 UTC | 1h 40m |
| 2026-05-02 | OYCBK | - | May 2, 16:50 UTC | May 2, 18:40 UTC | 1h 50m |
| 2026-05-01 | OYCBK | - | May 1, 14:30 UTC | May 1, 16:30 UTC | 2h 0m |
| 2026-04-30 | OYCBK | - | Apr 30, 12:30 UTC | Apr 30, 14:30 UTC | 2h 0m |
| 2026-04-29 | OYCBK | - | Apr 29, 08:25 UTC | Apr 29, 10:10 UTC | 1h 46m |
| 2026-04-26 | FXT12K | GWT → ZHI | Apr 26, 11:15 UTC | Apr 26, 14:15 UTC | 3h 0m |
| 2026-04-24 | FXT12K | GWT → ZHI | Apr 24, 06:25 UTC | Apr 24, 09:15 UTC | 2h 50m |
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-CBK page for operator, model, and routing details .