sensors Mode-S transponder
45CF33
ICAO 24-bit transponder address · allocated to Denmark
Currently assigned to OY-SYS · PARTENAVIA P-68 Observer
- Hex
- 45CF33
- Octal
- 21347463
- Decimal
- 4,575,027
- Country
- DK
- Tail
- OY-SYS
- Type
- P68
- Flights observed
- 49
- Distinct callsigns
- 1
- Country
- DK
- Last broadcast
- 3d ago
Last known position
Country allocation
The ICAO 24-bit address 45CF33 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 1 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| OYSYS | - | 49 | 2026-05-30 |
Recent flights last 49
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | OYSYS | - | May 30, 15:05 UTC | May 30, 16:25 UTC | 1h 20m |
| 2026-05-30 | OYSYS | - | May 30, 12:55 UTC | May 30, 14:05 UTC | 1h 10m |
| 2026-05-30 | OYSYS | - | May 30, 10:55 UTC | May 30, 11:05 UTC | 10m |
| 2026-05-30 | OYSYS | - | May 30, 08:30 UTC | May 30, 10:20 UTC | 1h 50m |
| 2026-05-30 | OYSYS | - | May 30, 05:30 UTC | May 30, 06:35 UTC | 1h 5m |
| 2026-05-28 | OYSYS | - | May 28, 11:35 UTC | May 28, 13:30 UTC | 1h 55m |
| 2026-05-28 | OYSYS | - | May 28, 06:30 UTC | May 28, 07:20 UTC | 50m |
| 2026-05-28 | OYSYS | - | May 28, 05:00 UTC | May 28, 05:50 UTC | 50m |
| 2026-05-25 | OYSYS | - | May 25, 07:15 UTC | May 25, 12:35 UTC | 5h 20m |
| 2026-05-25 | OYSYS | - | May 25, 06:10 UTC | May 25, 06:45 UTC | 35m |
| 2026-05-25 | OYSYS | - | May 25, 04:10 UTC | May 25, 05:05 UTC | 55m |
| 2026-05-24 | OYSYS | - | May 24, 12:55 UTC | May 24, 13:55 UTC | 1h 0m |
| 2026-05-24 | OYSYS | - | May 24, 10:40 UTC | May 24, 11:50 UTC | 1h 10m |
| 2026-05-24 | OYSYS | - | May 24, 08:35 UTC | May 24, 09:10 UTC | 35m |
| 2026-05-24 | OYSYS | - | May 24, 06:40 UTC | May 24, 07:15 UTC | 35m |
| 2026-05-24 | OYSYS | - | May 24, 04:45 UTC | May 24, 05:35 UTC | 50m |
| 2026-05-18 | OYSYS | - | May 18, 13:50 UTC | May 18, 14:55 UTC | 1h 5m |
| 2026-05-18 | OYSYS | - | May 18, 11:45 UTC | May 18, 13:05 UTC | 1h 20m |
| 2026-05-17 | OYSYS | - | May 17, 13:20 UTC | May 17, 15:25 UTC | 2h 5m |
| 2026-05-17 | OYSYS | - | May 17, 11:50 UTC | May 17, 12:30 UTC | 40m |
| 2026-05-17 | OYSYS | - | May 17, 09:20 UTC | May 17, 10:00 UTC | 40m |
| 2026-05-12 | OYSYS | - | May 12, 07:05 UTC | May 12, 08:15 UTC | 1h 10m |
| 2026-05-09 | OYSYS | - | May 9, 07:00 UTC | May 9, 08:45 UTC | 1h 45m |
| 2026-05-08 | OYSYS | - | May 8, 14:00 UTC | May 8, 15:05 UTC | 1h 5m |
| 2026-05-08 | OYSYS | - | May 8, 04:49 UTC | May 8, 07:24 UTC | 2h 35m |
| 2026-05-07 | OYSYS | - | May 7, 14:10 UTC | May 7, 15:10 UTC | 1h 0m |
| 2026-05-07 | OYSYS | - | May 7, 13:15 UTC | May 7, 13:25 UTC | 10m |
| 2026-05-07 | OYSYS | - | May 7, 06:20 UTC | May 7, 06:30 UTC | 10m |
| 2026-05-06 | OYSYS | - | May 6, 12:01 UTC | May 6, 12:50 UTC | 49m |
| 2026-05-06 | OYSYS | - | May 6, 07:30 UTC | May 6, 08:20 UTC | 50m |
| 2026-04-29 | OYSYS | - | Apr 29, 13:20 UTC | Apr 29, 14:20 UTC | 1h 0m |
| 2026-04-29 | OYSYS | - | Apr 29, 06:15 UTC | Apr 29, 12:45 UTC | 6h 31m |
| 2026-04-27 | OYSYS | - | Apr 27, 14:35 UTC | Apr 27, 15:30 UTC | 55m |
| 2026-04-27 | OYSYS | - | Apr 27, 13:25 UTC | Apr 27, 13:50 UTC | 25m |
| 2026-04-27 | OYSYS | - | Apr 27, 08:05 UTC | Apr 27, 08:25 UTC | 20m |
| 2026-04-27 | OYSYS | - | Apr 27, 06:05 UTC | Apr 27, 07:25 UTC | 1h 20m |
| 2026-04-22 | OYSYS | - | Apr 22, 12:40 UTC | Apr 22, 14:00 UTC | 1h 20m |
| 2026-04-22 | OYSYS | QHU → QHU | Apr 22, 05:45 UTC | Apr 22, 12:05 UTC | 6h 20m |
| 2026-04-21 | OYSYS | QHU → QHU | Apr 21, 12:20 UTC | Apr 21, 15:25 UTC | 3h 5m |
| 2026-04-21 | OYSYS | - | Apr 21, 05:25 UTC | Apr 21, 10:40 UTC | 5h 15m |
| 2026-04-18 | OYSYS | - | Apr 18, 13:45 UTC | Apr 18, 15:05 UTC | 1h 20m |
| 2026-04-18 | OYSYS | - | Apr 18, 07:25 UTC | Apr 18, 09:20 UTC | 1h 55m |
| 2026-04-18 | OYSYS | - | Apr 18, 07:10 UTC | Apr 18, 12:15 UTC | 5h 5m |
| 2026-04-17 | OYSYS | - | Apr 17, 13:20 UTC | Apr 17, 13:50 UTC | 30m |
| 2026-04-17 | OYSYS | - | Apr 17, 12:55 UTC | Apr 17, 13:15 UTC | 20m |
| 2026-04-14 | OYSYS | - | Apr 14, 13:45 UTC | Apr 14, 13:55 UTC | 10m |
| 2026-04-14 | OYSYS | - | Apr 14, 12:10 UTC | Apr 14, 12:30 UTC | 20m |
| 2026-04-14 | OYSYS | - | Apr 14, 08:45 UTC | Apr 14, 09:00 UTC | 15m |
| 2026-04-13 | OYSYS | - | Apr 13, 13:00 UTC | Apr 13, 13:55 UTC | 55m |
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-SYS page for operator, model, and routing details .