sensors Mode-S transponder
151FE7
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73703 · AIRBUS A-321
- Hex
- 151FE7
- Octal
- 05217747
- Decimal
- 1,384,423
- Country
- RU
- Tail
- RA-73703
- Type
- A321
- Flights observed
- 196
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 8h ago
Last known position
Country allocation
The ICAO 24-bit address 151FE7 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 |
|---|---|---|---|
| AFL421 | - | 36 | 2026-06-30 |
| AFL420 | - | 18 | 2026-06-29 |
| AFL430 | - | 17 | 2026-06-19 |
| AFL431 | Aeroflot Russian Airlines | 15 | 2026-06-18 |
| AFL1751 | - | 8 | 2026-07-05 |
| AFL427 | - | 6 | 2026-07-13 |
| AFL661 | Aeroflot Russian Airlines | 5 | 2026-05-06 |
| AFL233 | Aeroflot Russian Airlines | 5 | 2026-04-20 |
| AFL232 | Aeroflot Russian Airlines | 5 | 2026-04-23 |
| AFL439 | - | 4 | 2026-07-11 |
| AFL426 | - | 4 | 2026-07-12 |
| AFL2160 | Aeroflot Russian Airlines | 4 | 2026-05-02 |
| AFL1645 | Aeroflot Russian Airlines | 4 | 2026-05-06 |
| AFL1644 | Aeroflot Russian Airlines | 4 | 2026-05-05 |
| AFL480 | - | 3 | 2026-07-11 |
| AFL1014 | Aeroflot Russian Airlines | 3 | 2026-06-21 |
| AFL1003 | Aeroflot Russian Airlines | 3 | 2026-05-04 |
| AFL462 | - | 2 | 2026-07-05 |
| AFL438 | - | 2 | 2026-07-04 |
| AFL433 | Aeroflot Russian Airlines | 2 | 2026-06-20 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | AFL485 | - | Jul 14, 06:25 UTC | Jul 14, 07:50 UTC | 1h 25m |
| 2026-07-13 | AFL427 | - | Jul 13, 12:25 UTC | Jul 14, 04:10 UTC | 15h 45m |
| 2026-07-12 | AFL426 | - | Jul 12, 15:50 UTC | Jul 13, 10:10 UTC | 18h 20m |
| 2026-07-12 | AFL427 | - | Jul 12, 13:50 UTC | Jul 13, 10:10 UTC | 20h 20m |
| 2026-07-12 | AFL427 | - | Jul 12, 13:30 UTC | Jul 13, 10:10 UTC | 20h 40m |
| 2026-07-11 | AFL426 | - | Jul 11, 21:50 UTC | Jul 12, 11:10 UTC | 13h 20m |
| 2026-07-11 | AFL480 | - | Jul 11, 16:35 UTC | Jul 11, 19:20 UTC | 2h 45m |
| 2026-07-11 | AFL480 | SVO → SVO | Jul 11, 13:35 UTC | Jul 11, 14:10 UTC | 35m |
| 2026-07-11 | AFL439 | SVO → SVO | Jul 11, 11:15 UTC | Jul 11, 11:25 UTC | 10m |
| 2026-07-11 | AFL439 | - | Jul 11, 07:45 UTC | Jul 11, 09:10 UTC | 1h 25m |
| 2026-07-11 | AFL439 | - | Jul 11, 06:25 UTC | Jul 11, 07:40 UTC | 1h 15m |
| 2026-07-10 | AFL427 | - | Jul 10, 12:40 UTC | Jul 11, 04:20 UTC | 15h 40m |
| 2026-07-09 | AFL426 | - | Jul 9, 21:35 UTC | Jul 10, 10:25 UTC | 12h 50m |
| 2026-07-09 | AFL429 | - | Jul 9, 05:20 UTC | Jul 9, 18:30 UTC | 13h 10m |
| 2026-07-09 | AFL428 | - | Jul 9, 01:30 UTC | Jul 9, 03:05 UTC | 1h 35m |
| 2026-07-08 | AFL428 | SVO → SVO | Jul 8, 21:30 UTC | Jul 8, 22:10 UTC | 40m |
| 2026-07-08 | AFL427 | - | Jul 8, 08:30 UTC | Jul 8, 14:55 UTC | 6h 25m |
| 2026-07-07 | AFL423 | - | Jul 7, 14:05 UTC | Jul 8, 13:45 UTC | 23h 40m |
| 2026-07-07 | AFL423 | - | Jul 7, 10:10 UTC | Jul 8, 09:45 UTC | 23h 35m |
| 2026-07-05 | AFL1751 | - | Jul 5, 20:40 UTC | Jul 6, 08:30 UTC | 11h 50m |
| 2026-07-05 | AFL463 | - | Jul 5, 07:10 UTC | Jul 5, 10:05 UTC | 2h 55m |
| 2026-07-05 | AFL462 | - | Jul 5, 03:00 UTC | Jul 5, 04:35 UTC | 1h 35m |
| 2026-07-04 | AFL462 | SVO → SVO | Jul 4, 22:55 UTC | Jul 4, 23:20 UTC | 25m |
| 2026-07-04 | AFL439 | SSH → SVO | Jul 4, 15:30 UTC | Jul 4, 18:30 UTC | 3h 0m |
| 2026-07-04 | AFL438 | - | Jul 4, 11:15 UTC | Jul 4, 13:25 UTC | 2h 10m |
| 2026-07-04 | AFL438 | SVO → SVO | Jul 4, 07:55 UTC | Jul 4, 08:20 UTC | 25m |
| 2026-07-03 | AFL427 | - | Jul 3, 12:25 UTC | Jul 3, 15:20 UTC | 2h 55m |
| 2026-07-02 | AFL426 | - | Jul 2, 21:15 UTC | Jul 3, 10:20 UTC | 13h 5m |
| 2026-07-02 | AFL480 | - | Jul 2, 05:20 UTC | Jul 2, 18:35 UTC | 13h 15m |
| 2026-07-01 | AFL422 | - | Jul 1, 08:20 UTC | Jul 2, 03:05 UTC | 18h 45m |
| 2026-06-30 | AFL422 | - | Jun 30, 19:50 UTC | Jul 1, 14:55 UTC | 19h 5m |
| 2026-06-30 | AFL421 | - | Jun 30, 17:50 UTC | Jul 1, 14:55 UTC | 21h 5m |
| 2026-06-29 | AFL420 | - | Jun 29, 19:49 UTC | Jun 30, 15:35 UTC | 19h 46m |
| 2026-06-29 | AFL420 | - | Jun 29, 17:59 UTC | Jun 30, 15:35 UTC | 21h 36m |
| 2026-06-29 | AFL420 | - | Jun 29, 13:49 UTC | Jun 30, 13:25 UTC | 23h 36m |
| 2026-06-29 | AFL421 | - | Jun 29, 13:39 UTC | Jun 29, 20:44 UTC | 7h 5m |
| 2026-06-28 | AFL421 | - | Jun 28, 12:39 UTC | Jun 28, 20:39 UTC | 8h 0m |
| 2026-06-27 | AFL421 | - | Jun 27, 23:50 UTC | Jun 28, 20:39 UTC | 20h 50m |
| 2026-06-27 | AFL421 | - | Jun 27, 23:34 UTC | Jun 28, 20:39 UTC | 21h 5m |
| 2026-06-26 | AFL1751 | - | Jun 26, 10:55 UTC | Jun 26, 11:14 UTC | 20m |
| 2026-06-25 | AFL1751 | - | Jun 25, 21:29 UTC | Jun 26, 09:45 UTC | 12h 15m |
| 2026-06-25 | AFL1751 | - | Jun 25, 11:50 UTC | Jun 26, 09:45 UTC | 21h 55m |
| 2026-06-25 | AFL1751 | - | Jun 25, 10:35 UTC | Jun 26, 09:45 UTC | 23h 10m |
| 2026-06-23 | AFL1751 | - | Jun 23, 21:29 UTC | Jun 24, 10:19 UTC | 12h 50m |
| 2026-06-23 | AFL1751 | - | Jun 23, 09:54 UTC | Jun 23, 11:24 UTC | 1h 30m |
| 2026-06-22 | AFL1751 | - | Jun 22, 09:19 UTC | Jun 22, 10:15 UTC | 55m |
| 2026-06-21 | AFL1301 | MRV → SVO | Jun 21, 19:34 UTC | Jun 21, 20:00 UTC | 25m |
| 2026-06-21 | AFL1015 | KGD → SVO | Jun 21, 09:04 UTC | Jun 21, 10:09 UTC | 1h 5m |
| 2026-06-21 | AFL1014 | SVO → KGD | Jun 21, 05:10 UTC | Jun 21, 07:20 UTC | 2h 10m |
| 2026-06-20 | AFL433 | HRG → SVO | Jun 20, 16:24 UTC | Jun 20, 18:59 UTC | 2h 35m |
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-73703 page for operator, model, and routing details .