sensors Mode-S transponder
151FE5
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73701 · AIRBUS A-330-300
- Hex
- 151FE5
- Octal
- 05217745
- Decimal
- 1,384,421
- Country
- RU
- Tail
- RA-73701
- Type
- A333
- Flights observed
- 141
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 17h ago
Last known position
Country allocation
The ICAO 24-bit address 151FE5 falls within the block assigned to Russia (RU) by ICAO Annex 10, Volume III. Every aircraft registered in Russia 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 |
|---|---|---|---|
| AFL626 | - | 11 | 2026-06-25 |
| AFL225 | - | 9 | 2026-06-24 |
| AFL733 | Aeroflot Russian Airlines | 6 | 2026-06-07 |
| AFL643 | - | 6 | 2026-07-06 |
| AFL224 | - | 6 | 2026-07-11 |
| AFL837 | - | 5 | 2026-06-29 |
| AFL627 | Aeroflot Russian Airlines | 5 | 2026-06-07 |
| AFL293 | - | 5 | 2026-06-19 |
| AFL836 | - | 4 | 2026-06-29 |
| AFL831 | Aeroflot Russian Airlines | 4 | 2026-05-09 |
| AFL734 | Aeroflot Russian Airlines | 4 | 2026-06-06 |
| AFL637 | - | 4 | 2026-07-10 |
| AFL861 | - | 3 | 2026-06-15 |
| AFL855 | Aeroflot Russian Airlines | 3 | 2026-05-19 |
| AFL655 | Aeroflot Russian Airlines | 3 | 2026-05-10 |
| AFL653 | Aeroflot Russian Airlines | 3 | 2026-04-19 |
| AFL652 | Aeroflot Russian Airlines | 3 | 2026-04-18 |
| AFL650 | Aeroflot Russian Airlines | 3 | 2026-05-09 |
| AFL642 | - | 3 | 2026-07-08 |
| AFL620 | Aeroflot Russian Airlines | 3 | 2026-04-25 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | AFL7774 | - | Jul 13, 08:01 UTC | Jul 13, 23:20 UTC | 15h 20m |
| 2026-07-11 | AFL224 | - | Jul 11, 11:55 UTC | Jul 12, 04:45 UTC | 16h 50m |
| 2026-07-11 | AFL1553 | - | Jul 11, 08:40 UTC | Jul 11, 09:10 UTC | 30m |
| 2026-07-10 | AFL637 | - | Jul 10, 07:45 UTC | Jul 10, 19:05 UTC | 11h 20m |
| 2026-07-09 | AFL634 | - | Jul 9, 09:20 UTC | Jul 10, 09:15 UTC | 23h 55m |
| 2026-07-08 | AFL635 | - | Jul 8, 15:55 UTC | Jul 9, 09:20 UTC | 17h 25m |
| 2026-07-08 | AFL635 | - | Jul 8, 13:20 UTC | Jul 9, 09:20 UTC | 20h 0m |
| 2026-07-08 | AFL642 | - | Jul 8, 11:35 UTC | Jul 9, 09:20 UTC | 21h 45m |
| 2026-07-08 | AFL642 | - | Jul 8, 07:20 UTC | Jul 9, 03:45 UTC | 20h 25m |
| 2026-07-08 | AFL642 | - | Jul 8, 06:00 UTC | Jul 9, 03:45 UTC | 21h 45m |
| 2026-07-08 | AFL636 | - | Jul 8, 01:30 UTC | Jul 8, 23:30 UTC | 22h 0m |
| 2026-07-06 | AFL637 | - | Jul 6, 22:00 UTC | Jul 7, 10:15 UTC | 12h 15m |
| 2026-07-06 | AFL637 | - | Jul 6, 07:20 UTC | Jul 7, 05:00 UTC | 21h 40m |
| 2026-07-06 | AFL637 | - | Jul 6, 07:10 UTC | Jul 7, 05:00 UTC | 21h 50m |
| 2026-07-06 | AFL634 | - | Jul 6, 03:20 UTC | Jul 6, 23:40 UTC | 20h 20m |
| 2026-07-06 | AFL643 | - | Jul 6, 01:35 UTC | Jul 6, 23:40 UTC | 22h 5m |
| 2026-07-05 | AFL643 | - | Jul 5, 22:45 UTC | Jul 6, 08:20 UTC | 9h 35m |
| 2026-07-05 | AFL643 | - | Jul 5, 09:20 UTC | Jul 6, 08:20 UTC | 23h 0m |
| 2026-07-05 | AFL643 | - | Jul 5, 08:55 UTC | Jul 6, 07:15 UTC | 22h 20m |
| 2026-07-05 | AFL643 | - | Jul 5, 05:20 UTC | Jul 6, 03:25 UTC | 22h 5m |
| 2026-07-05 | AFL643 | - | Jul 5, 05:05 UTC | Jul 6, 03:15 UTC | 22h 10m |
| 2026-07-05 | AFL636 | - | Jul 5, 00:05 UTC | Jul 5, 23:10 UTC | 23h 5m |
| 2026-07-03 | AFL292 | - | Jul 3, 22:00 UTC | Jul 4, 07:40 UTC | 9h 40m |
| 2026-06-29 | AFL837 | - | Jun 29, 18:39 UTC | Jun 30, 10:05 UTC | 15h 26m |
| 2026-06-29 | AFL836 | - | Jun 29, 02:45 UTC | Jun 29, 23:54 UTC | 21h 10m |
| 2026-06-28 | AFL232 | - | Jun 28, 19:04 UTC | Jun 28, 19:14 UTC | 10m |
| 2026-06-26 | AFL836 | - | Jun 26, 19:00 UTC | Jun 27, 10:29 UTC | 15h 30m |
| 2026-06-25 | AFL626 | - | Jun 25, 22:45 UTC | Jun 26, 09:24 UTC | 10h 40m |
| 2026-06-24 | AFL225 | - | Jun 24, 07:59 UTC | Jun 24, 08:20 UTC | 20m |
| 2026-06-23 | AFL225 | - | Jun 23, 23:29 UTC | Jun 24, 04:44 UTC | 5h 15m |
| 2026-06-19 | AFL293 | - | Jun 19, 20:59 UTC | Jun 20, 08:59 UTC | 12h 0m |
| 2026-06-18 | AFL1414 | SVO → SVX | Jun 18, 15:55 UTC | Jun 18, 16:10 UTC | 15m |
| 2026-06-17 | AFL225 | - | Jun 17, 22:30 UTC | Jun 18, 06:05 UTC | 7h 35m |
| 2026-06-17 | AFL224 | SVO → SYX | Jun 17, 14:15 UTC | Jun 17, 19:40 UTC | 5h 25m |
| 2026-06-16 | AFL025 | - | Jun 16, 17:24 UTC | Jun 16, 18:29 UTC | 1h 5m |
| 2026-06-15 | AFL861 | - | Jun 15, 17:25 UTC | Jun 16, 11:00 UTC | 17h 35m |
| 2026-06-15 | AFL863 | - | Jun 15, 03:50 UTC | Jun 15, 22:35 UTC | 18h 45m |
| 2026-06-14 | AFL863 | - | Jun 14, 22:35 UTC | Jun 15, 17:59 UTC | 19h 24m |
| 2026-06-14 | AFL865 | SYX → UFA | Jun 14, 01:30 UTC | Jun 14, 19:35 UTC | 18h 5m |
| 2026-06-13 | AFL860 | LED → SVO | Jun 13, 13:25 UTC | Jun 13, 13:40 UTC | 15m |
| 2026-06-12 | AFL861 | SYX → LED | Jun 12, 16:40 UTC | Jun 13, 09:10 UTC | 16h 29m |
| 2026-06-12 | AFL861 | SYX → LED | Jun 12, 09:20 UTC | Jun 13, 09:10 UTC | 23h 49m |
| 2026-06-10 | AFL292 | SVO → SGN | Jun 10, 16:30 UTC | Jun 11, 09:35 UTC | 17h 5m |
| 2026-06-09 | AFL629 | HKT → LED | Jun 9, 15:15 UTC | Jun 9, 15:25 UTC | 10m |
| 2026-06-08 | AFL626 | SVX → HKT | Jun 8, 22:20 UTC | Jun 9, 09:15 UTC | 10h 55m |
| 2026-06-08 | AFL626 | SVX → HKT | Jun 8, 12:45 UTC | Jun 9, 09:15 UTC | 20h 30m |
| 2026-06-08 | AFL626 | SVX → HKT | Jun 8, 07:30 UTC | Jun 9, 07:15 UTC | 23h 45m |
| 2026-06-08 | AFL626 | SVX → HKT | Jun 8, 06:25 UTC | Jun 9, 00:45 UTC | 18h 20m |
| 2026-06-07 | AFL627 | HKT → SVX | Jun 7, 23:20 UTC | Jun 8, 23:15 UTC | 23h 55m |
| 2026-06-07 | AFL627 | HKT → SVX | Jun 7, 19:05 UTC | Jun 8, 13:05 UTC | 18h 0m |
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 RA-73701 page for operator, model, and routing details .