sensors Mode-S transponder
45CAB9
ICAO 24-bit transponder address · allocated to Denmark
Currently assigned to OY-RUY · AIRBUS A-320
- Hex
- 45CAB9
- Octal
- 21345271
- Decimal
- 4,573,881
- Country
- DK
- Tail
- OY-RUY
- Type
- A320
- Flights observed
- 44
- Distinct callsigns
- 20
- Country
- DK
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address 45CAB9 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 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| UGD901 | - | 10 | 2026-05-10 |
| UGD711 | - | 6 | 2026-05-06 |
| UGD710 | - | 5 | 2026-05-06 |
| UGD900 | - | 4 | 2026-05-07 |
| RZO3126 | - | 2 | 2026-05-25 |
| RZO178 | SATA International | 2 | 2026-05-24 |
| DNU937 | - | 2 | 2026-05-13 |
| UR900 | - | 1 | 2026-04-23 |
| UGDD711 | - | 1 | 2026-05-08 |
| UGD712 | - | 1 | 2026-04-19 |
| RZO9179 | - | 1 | 2026-05-25 |
| RZO9124 | - | 1 | 2026-05-23 |
| RZO3179 | - | 1 | 2026-05-25 |
| RZO127 | SATA International | 1 | 2026-05-23 |
| RZO124 | SATA International | 1 | 2026-05-23 |
| DNU952 | DOT LT | 1 | 2026-05-31 |
| DNU6811 | - | 1 | 2026-05-31 |
| DNA905P | - | 1 | 2026-05-30 |
| DNA904P | - | 1 | 2026-05-30 |
| DNA904 | - | 1 | 2026-05-30 |
Recent flights last 44
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-31 | DNU952 | - | May 31, 17:10 UTC | May 31, 19:00 UTC | 1h 50m |
| 2026-05-31 | DNU6811 | BER → BLQ | May 31, 12:30 UTC | May 31, 13:50 UTC | 1h 20m |
| 2026-05-30 | DNA905P | - | May 30, 13:20 UTC | May 30, 14:25 UTC | 1h 5m |
| 2026-05-30 | DNA904 | - | May 30, 10:00 UTC | May 30, 11:25 UTC | 1h 25m |
| 2026-05-30 | DNA904P | - | May 30, 04:55 UTC | May 30, 07:05 UTC | 2h 10m |
| 2026-05-25 | RZO9179 | LIS → BLL | May 25, 20:30 UTC | May 25, 23:35 UTC | 3h 5m |
| 2026-05-25 | RZO3126 | - | May 25, 19:00 UTC | May 25, 19:35 UTC | 34m |
| 2026-05-25 | RZO3126 | - | May 25, 17:30 UTC | May 25, 17:40 UTC | 10m |
| 2026-05-25 | RZO3179 | - | May 25, 13:50 UTC | May 25, 14:30 UTC | 40m |
| 2026-05-24 | RZO178 | PDL → OPO | May 24, 20:05 UTC | May 24, 20:55 UTC | 50m |
| 2026-05-24 | RZO178 | PDL → OPO | May 24, 18:40 UTC | May 24, 18:50 UTC | 10m |
| 2026-05-23 | RZO127 | LIS → PDL | May 23, 21:35 UTC | May 23, 23:35 UTC | 2h 0m |
| 2026-05-23 | RZO124 | PDL → LIS | May 23, 19:20 UTC | May 23, 20:00 UTC | 40m |
| 2026-05-23 | RZO9124 | - | May 23, 10:15 UTC | May 23, 13:40 UTC | 3h 25m |
| 2026-05-13 | DNU937 | LCA → BLL | May 13, 13:45 UTC | May 13, 17:55 UTC | 4h 10m |
| 2026-05-13 | DNU937 | - | May 13, 11:35 UTC | May 13, 12:50 UTC | 1h 15m |
| 2026-05-10 | UGD901 | - | May 10, 23:05 UTC | May 11, 11:40 UTC | 12h 35m |
| 2026-05-10 | UGD901 | - | May 10, 07:15 UTC | May 10, 21:25 UTC | 14h 10m |
| 2026-05-08 | UGDD711 | - | May 8, 11:19 UTC | May 8, 11:49 UTC | 30m |
| 2026-05-07 | UGD900 | - | May 7, 14:55 UTC | May 8, 09:19 UTC | 18h 25m |
| 2026-05-06 | UGD711 | - | May 6, 11:05 UTC | May 6, 11:35 UTC | 30m |
| 2026-05-06 | UGD710 | - | May 6, 08:55 UTC | May 6, 09:30 UTC | 35m |
| 2026-05-04 | UGD901 | - | May 4, 11:40 UTC | May 4, 11:55 UTC | 15m |
| 2026-05-03 | UGD900 | - | May 3, 06:55 UTC | May 3, 07:05 UTC | 10m |
| 2026-05-01 | UGD711 | - | May 1, 11:15 UTC | May 1, 11:50 UTC | 35m |
| 2026-04-30 | UGD900 | - | Apr 30, 15:50 UTC | May 1, 09:45 UTC | 17h 55m |
| 2026-04-29 | UGD711 | - | Apr 29, 11:20 UTC | Apr 29, 11:45 UTC | 25m |
| 2026-04-29 | UGD710 | - | Apr 29, 09:15 UTC | Apr 29, 09:55 UTC | 40m |
| 2026-04-26 | UGD901 | - | Apr 26, 23:20 UTC | Apr 27, 11:50 UTC | 12h 30m |
| 2026-04-26 | UGD901 | - | Apr 26, 07:20 UTC | Apr 26, 21:30 UTC | 14h 10m |
| 2026-04-23 | UR900 | - | Apr 23, 15:40 UTC | Apr 23, 19:50 UTC | 4h 10m |
| 2026-04-22 | UGD711 | - | Apr 22, 11:10 UTC | Apr 22, 11:45 UTC | 35m |
| 2026-04-22 | UGD710 | - | Apr 22, 08:55 UTC | Apr 22, 09:25 UTC | 30m |
| 2026-04-19 | UGD901 | - | Apr 19, 23:10 UTC | Apr 20, 11:45 UTC | 12h 35m |
| 2026-04-19 | UGD712 | - | Apr 19, 07:30 UTC | Apr 19, 21:40 UTC | 14h 10m |
| 2026-04-17 | UGD711 | - | Apr 17, 11:40 UTC | Apr 17, 12:10 UTC | 30m |
| 2026-04-17 | UGD710 | - | Apr 17, 09:20 UTC | Apr 17, 09:55 UTC | 35m |
| 2026-04-16 | UGD901 | - | Apr 16, 20:45 UTC | Apr 16, 21:10 UTC | 25m |
| 2026-04-16 | UGD900 | - | Apr 16, 17:15 UTC | Apr 16, 17:25 UTC | 10m |
| 2026-04-15 | UGD711 | - | Apr 15, 11:50 UTC | Apr 15, 12:15 UTC | 25m |
| 2026-04-15 | UGD710 | - | Apr 15, 09:45 UTC | Apr 15, 10:20 UTC | 35m |
| 2026-04-13 | UGD901 | - | Apr 13, 12:20 UTC | Apr 13, 12:40 UTC | 20m |
| 2026-04-13 | UGD901 | - | Apr 13, 12:00 UTC | Apr 13, 12:40 UTC | 40m |
| 2026-04-13 | UGD901 | - | Apr 13, 08:25 UTC | Apr 13, 12:15 UTC | 3h 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-RUY page for operator, model, and routing details .