sensors Mode-S transponder
151FE8
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73704 · AIRBUS A-321
- Hex
- 151FE8
- Octal
- 05217750
- Decimal
- 1,384,424
- Country
- RU
- Tail
- RA-73704
- Type
- A321
- Flights observed
- 207
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 2h ago
Last known position
Country allocation
The ICAO 24-bit address 151FE8 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 |
|---|---|---|---|
| AFL431 | - | 40 | 2026-06-30 |
| AFL430 | - | 25 | 2026-06-28 |
| AFL421 | - | 17 | 2026-06-24 |
| AFL420 | - | 15 | 2026-06-24 |
| AFL433 | Aeroflot Russian Airlines | 9 | 2026-06-27 |
| AFL1751 | - | 9 | 2026-07-11 |
| AFL423 | - | 8 | 2026-07-13 |
| AFL432 | Aeroflot Russian Airlines | 5 | 2026-06-27 |
| AFL1300 | Aeroflot Russian Airlines | 4 | 2026-06-17 |
| AFL660 | - | 3 | 2026-04-15 |
| AFL422 | - | 3 | 2026-07-12 |
| AFL2148 | Aeroflot Russian Airlines | 3 | 2026-04-26 |
| AFL1882 | Aeroflot Russian Airlines | 3 | 2026-04-23 |
| AFL1645 | - | 3 | 2026-04-15 |
| AFL1018 | Aeroflot Russian Airlines | 3 | 2026-05-07 |
| AFL1017 | Aeroflot Russian Airlines | 3 | 2026-05-05 |
| AFL1016 | Aeroflot Russian Airlines | 3 | 2026-05-05 |
| AFL1011 | Aeroflot Russian Airlines | 3 | 2026-05-06 |
| AFL1010 | Aeroflot Russian Airlines | 3 | 2026-05-06 |
| AFL853 | Aeroflot Russian Airlines | 2 | 2026-04-19 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | AFL423 | - | Jul 13, 13:35 UTC | Jul 14, 04:10 UTC | 14h 35m |
| 2026-07-12 | AFL422 | - | Jul 12, 18:30 UTC | Jul 13, 11:00 UTC | 16h 30m |
| 2026-07-11 | AFL1751 | - | Jul 11, 08:40 UTC | Jul 11, 18:40 UTC | 10h 0m |
| 2026-07-10 | AFL1751 | - | Jul 10, 10:05 UTC | Jul 11, 10:00 UTC | 23h 56m |
| 2026-07-09 | AFL1751 | - | Jul 9, 16:05 UTC | Jul 10, 10:30 UTC | 18h 25m |
| 2026-07-09 | AFL423 | - | Jul 9, 14:05 UTC | Jul 10, 10:30 UTC | 20h 25m |
| 2026-07-09 | AFL423 | - | Jul 9, 13:45 UTC | Jul 10, 10:30 UTC | 20h 45m |
| 2026-07-09 | AFL423 | - | Jul 9, 10:05 UTC | Jul 10, 10:00 UTC | 23h 55m |
| 2026-07-09 | AFL423 | - | Jul 9, 08:45 UTC | Jul 9, 23:10 UTC | 14h 25m |
| 2026-07-09 | AFL422 | SVO → SVO | Jul 9, 05:40 UTC | Jul 9, 06:35 UTC | 55m |
| 2026-07-07 | AFL423 | - | Jul 7, 22:05 UTC | Jul 8, 16:50 UTC | 18h 45m |
| 2026-07-07 | AFL423 | - | Jul 7, 21:25 UTC | Jul 8, 16:50 UTC | 19h 25m |
| 2026-07-07 | AFL480 | - | Jul 7, 01:40 UTC | Jul 7, 19:10 UTC | 17h 30m |
| 2026-07-06 | AFL484 | SVO → SVO | Jul 6, 21:35 UTC | Jul 6, 22:25 UTC | 50m |
| 2026-07-06 | AFL423 | - | Jul 6, 08:40 UTC | Jul 6, 15:10 UTC | 6h 30m |
| 2026-07-06 | AFL422 | SVO → SVO | Jul 6, 04:40 UTC | Jul 6, 05:30 UTC | 50m |
| 2026-07-05 | AFL427 | - | Jul 5, 12:40 UTC | Jul 5, 15:25 UTC | 2h 45m |
| 2026-07-05 | AFL426 | - | Jul 5, 04:40 UTC | Jul 5, 10:15 UTC | 5h 35m |
| 2026-07-04 | AFL481 | - | Jul 4, 21:10 UTC | Jul 5, 00:05 UTC | 2h 55m |
| 2026-07-04 | AFL1751 | - | Jul 4, 08:35 UTC | Jul 4, 18:40 UTC | 10h 5m |
| 2026-07-03 | AFL1751 | - | Jul 3, 10:05 UTC | Jul 4, 10:00 UTC | 23h 55m |
| 2026-07-03 | AFL1751 | - | Jul 3, 09:15 UTC | Jul 3, 10:45 UTC | 1h 30m |
| 2026-07-02 | AFL1751 | - | Jul 2, 10:10 UTC | Jul 3, 09:55 UTC | 23h 45m |
| 2026-07-01 | AFL1751 | - | Jul 1, 22:35 UTC | Jul 2, 10:50 UTC | 12h 15m |
| 2026-07-01 | AFL427 | - | Jul 1, 12:40 UTC | Jul 1, 15:30 UTC | 2h 50m |
| 2026-06-30 | AFL431 | - | Jun 30, 14:05 UTC | Jul 1, 10:00 UTC | 19h 55m |
| 2026-06-30 | AFL431 | - | Jun 30, 13:50 UTC | Jul 1, 10:00 UTC | 20h 10m |
| 2026-06-29 | AFL431 | - | Jun 29, 20:04 UTC | Jun 30, 20:00 UTC | 23h 56m |
| 2026-06-29 | AFL431 | - | Jun 29, 18:05 UTC | Jun 30, 18:00 UTC | 23h 56m |
| 2026-06-29 | AFL431 | - | Jun 29, 17:45 UTC | Jun 30, 15:20 UTC | 21h 36m |
| 2026-06-28 | AFL430 | - | Jun 28, 20:04 UTC | Jun 29, 15:09 UTC | 19h 5m |
| 2026-06-28 | AFL431 | - | Jun 28, 18:05 UTC | Jun 29, 15:09 UTC | 21h 5m |
| 2026-06-28 | AFL431 | - | Jun 28, 17:50 UTC | Jun 29, 15:09 UTC | 21h 20m |
| 2026-06-28 | AFL430 | - | Jun 28, 12:55 UTC | Jun 28, 15:14 UTC | 2h 20m |
| 2026-06-27 | AFL430 | - | Jun 27, 18:09 UTC | Jun 28, 15:14 UTC | 21h 5m |
| 2026-06-27 | AFL433 | HRG → SVO | Jun 27, 16:14 UTC | Jun 28, 15:14 UTC | 23h 0m |
| 2026-06-27 | AFL432 | SVO → HRG | Jun 27, 12:34 UTC | Jun 27, 13:55 UTC | 1h 20m |
| 2026-06-27 | AFL432 | SVO → HRG | Jun 27, 08:29 UTC | Jun 27, 09:15 UTC | 45m |
| 2026-06-26 | AFL431 | SSH → SVO | Jun 26, 17:59 UTC | Jun 26, 20:55 UTC | 2h 55m |
| 2026-06-26 | AFL430 | - | Jun 26, 12:39 UTC | Jun 26, 15:20 UTC | 2h 40m |
| 2026-06-25 | AFL430 | - | Jun 25, 18:04 UTC | Jun 26, 15:20 UTC | 21h 15m |
| 2026-06-25 | AFL430 | - | Jun 25, 17:49 UTC | Jun 26, 15:20 UTC | 21h 30m |
| 2026-06-24 | AFL430 | - | Jun 24, 20:44 UTC | Jun 25, 15:24 UTC | 18h 40m |
| 2026-06-24 | AFL421 | - | Jun 24, 18:05 UTC | Jun 25, 15:24 UTC | 21h 20m |
| 2026-06-24 | AFL421 | - | Jun 24, 14:09 UTC | Jun 25, 13:59 UTC | 23h 50m |
| 2026-06-24 | AFL420 | - | Jun 24, 10:10 UTC | Jun 24, 20:54 UTC | 10h 45m |
| 2026-06-23 | AFL431 | SSH → SVO | Jun 23, 17:59 UTC | Jun 23, 19:29 UTC | 1h 30m |
| 2026-06-23 | AFL430 | - | Jun 23, 13:29 UTC | Jun 23, 14:55 UTC | 1h 25m |
| 2026-06-22 | AFL431 | SSH → SVO | Jun 22, 18:04 UTC | Jun 23, 14:55 UTC | 20h 50m |
| 2026-06-22 | AFL430 | - | Jun 22, 14:40 UTC | Jun 22, 16:05 UTC | 1h 25m |
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-73704 page for operator, model, and routing details .