sensors Mode-S transponder
50801F
ICAO 24-bit transponder address · allocated to Ukraine
Currently assigned to UR-82072 · ANTONOV An-124 Ruslan
- Hex
- 50801F
- Octal
- 24100037
- Decimal
- 5,275,679
- Country
- UA
- Tail
- UR-82072
- Type
- A124
- Flights observed
- 44
- Distinct callsigns
- 15
- Country
- UA
- Last broadcast
- 5d ago
Last known position
Country allocation
The ICAO 24-bit address 50801F falls within the block assigned to Ukraine (UA) by ICAO Annex 10, Volume III. Every aircraft registered in Ukraine 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 |
|---|---|---|---|
| ADB313F | - | 7 | 2026-04-23 |
| ADB3113 | - | 5 | 2026-04-22 |
| ADB7097 | - | 4 | 2026-05-28 |
| ADB315F | - | 4 | 2026-05-03 |
| ADB312F | - | 4 | 2026-04-14 |
| ADB3115 | - | 4 | 2026-05-01 |
| ADB3112 | - | 4 | 2026-04-17 |
| ADB797F | - | 2 | 2026-05-28 |
| ADB796F | - | 2 | 2026-05-24 |
| ADB7096 | - | 2 | 2026-05-23 |
| ADB5471 | - | 2 | 2026-05-19 |
| ADB572F | - | 1 | 2026-05-20 |
| ADB571F | - | 1 | 2026-05-16 |
| ADB5472 | - | 1 | 2026-05-19 |
| ADB372F | - | 1 | 2026-05-11 |
Recent flights last 44
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-28 | ADB797F | - | May 28, 16:10 UTC | May 28, 17:30 UTC | 1h 20m |
| 2026-05-28 | ADB7097 | KEF → RZE | May 28, 09:50 UTC | May 28, 13:35 UTC | 3h 45m |
| 2026-05-27 | ADB7097 | - | May 27, 17:05 UTC | May 27, 17:30 UTC | 25m |
| 2026-05-27 | ADB7097 | - | May 27, 12:40 UTC | May 27, 13:45 UTC | 1h 5m |
| 2026-05-27 | ADB7097 | - | May 27, 10:00 UTC | May 27, 10:55 UTC | 55m |
| 2026-05-26 | ADB797F | - | May 26, 15:54 UTC | May 26, 17:04 UTC | 1h 10m |
| 2026-05-24 | ADB796F | - | May 24, 13:45 UTC | May 24, 14:30 UTC | 45m |
| 2026-05-23 | ADB7096 | - | May 23, 13:20 UTC | May 23, 19:40 UTC | 6h 21m |
| 2026-05-22 | ADB7096 | - | May 22, 17:50 UTC | May 22, 18:25 UTC | 35m |
| 2026-05-22 | ADB796F | LEJ → BFS | May 22, 07:30 UTC | May 22, 09:25 UTC | 1h 55m |
| 2026-05-20 | ADB572F | - | May 20, 13:30 UTC | May 20, 15:50 UTC | 2h 20m |
| 2026-05-19 | ADB5472 | - | May 19, 16:00 UTC | May 19, 21:35 UTC | 5h 35m |
| 2026-05-19 | ADB5471 | - | May 19, 06:55 UTC | May 19, 08:35 UTC | 1h 40m |
| 2026-05-17 | ADB5471 | - | May 17, 10:35 UTC | May 17, 14:25 UTC | 3h 50m |
| 2026-05-16 | ADB571F | LEJ → PUF | May 16, 11:35 UTC | May 16, 13:51 UTC | 2h 15m |
| 2026-05-11 | ADB372F | LEJ → LEJ | May 11, 10:25 UTC | May 11, 11:15 UTC | 50m |
| 2026-05-03 | ADB315F | - | May 3, 13:55 UTC | May 3, 16:40 UTC | 2h 45m |
| 2026-05-03 | ADB315F | - | May 3, 10:35 UTC | May 3, 10:55 UTC | 20m |
| 2026-05-02 | ADB315F | - | May 2, 11:05 UTC | May 2, 16:30 UTC | 5h 25m |
| 2026-05-01 | ADB3115 | - | May 1, 13:50 UTC | May 2, 11:35 UTC | 21h 46m |
| 2026-05-01 | ADB3115 | - | May 1, 13:40 UTC | May 2, 11:35 UTC | 21h 55m |
| 2026-05-01 | ADB3115 | - | May 1, 08:30 UTC | May 1, 14:40 UTC | 6h 10m |
| 2026-04-30 | ADB3115 | MXP → DSS | Apr 30, 08:55 UTC | Apr 30, 15:10 UTC | 6h 15m |
| 2026-04-29 | ADB315F | LEJ → MXP | Apr 29, 12:15 UTC | Apr 29, 13:30 UTC | 1h 15m |
| 2026-04-23 | ADB313F | - | Apr 23, 21:45 UTC | Apr 24, 02:25 UTC | 4h 40m |
| 2026-04-22 | ADB313F | - | Apr 22, 19:30 UTC | Apr 22, 19:50 UTC | 20m |
| 2026-04-22 | ADB313F | - | Apr 22, 17:55 UTC | Apr 22, 18:50 UTC | 55m |
| 2026-04-22 | ADB3113 | - | Apr 22, 14:15 UTC | Apr 22, 14:45 UTC | 30m |
| 2026-04-22 | ADB3113 | - | Apr 22, 13:15 UTC | Apr 22, 13:30 UTC | 15m |
| 2026-04-21 | ADB3113 | - | Apr 21, 03:40 UTC | Apr 21, 04:15 UTC | 35m |
| 2026-04-20 | ADB3113 | - | Apr 20, 23:25 UTC | Apr 21, 00:10 UTC | 45m |
| 2026-04-20 | ADB3113 | - | Apr 20, 18:45 UTC | Apr 20, 19:05 UTC | 20m |
| 2026-04-19 | ADB313F | - | Apr 19, 09:20 UTC | Apr 19, 10:05 UTC | 45m |
| 2026-04-19 | ADB313F | - | Apr 19, 05:05 UTC | Apr 19, 05:40 UTC | 35m |
| 2026-04-17 | ADB313F | - | Apr 17, 18:10 UTC | Apr 17, 18:30 UTC | 20m |
| 2026-04-17 | ADB313F | - | Apr 17, 16:20 UTC | Apr 17, 17:15 UTC | 55m |
| 2026-04-17 | ADB3112 | - | Apr 17, 13:20 UTC | Apr 17, 13:30 UTC | 10m |
| 2026-04-17 | ADB3112 | - | Apr 17, 12:30 UTC | Apr 17, 12:55 UTC | 25m |
| 2026-04-17 | ADB3112 | - | Apr 17, 11:25 UTC | Apr 17, 11:35 UTC | 10m |
| 2026-04-15 | ADB3112 | - | Apr 15, 20:40 UTC | Apr 15, 21:00 UTC | 20m |
| 2026-04-14 | ADB312F | - | Apr 14, 12:50 UTC | Apr 14, 13:00 UTC | 10m |
| 2026-04-14 | ADB312F | - | Apr 14, 12:15 UTC | Apr 14, 12:45 UTC | 30m |
| 2026-04-12 | ADB312F | - | Apr 12, 18:15 UTC | Apr 12, 18:35 UTC | 20m |
| 2026-04-12 | ADB312F | - | Apr 12, 17:20 UTC | Apr 12, 17:35 UTC | 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 UR-82072 page for operator, model, and routing details .