sensors Mode-S transponder
151FF2
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73714 · AIRBUS A-321
- Hex
- 151FF2
- Octal
- 05217762
- Decimal
- 1,384,434
- Country
- RU
- Tail
- RA-73714
- Type
- A321
- Flights observed
- 201
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 16h ago
Last known position
Country allocation
The ICAO 24-bit address 151FF2 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 |
|---|---|---|---|
| AFL2143 | - | 10 | 2026-07-11 |
| AFL2146 | - | 7 | 2026-06-27 |
| AFL2170 | - | 5 | 2026-07-01 |
| AFL2147 | Aeroflot Russian Airlines | 5 | 2026-06-27 |
| AFL2142 | - | 5 | 2026-07-11 |
| AFL1011 | - | 5 | 2026-07-01 |
| AFL1947 | Aeroflot Russian Airlines | 4 | 2026-06-04 |
| AFL1946 | - | 4 | 2026-07-06 |
| AFL1833 | - | 4 | 2026-07-07 |
| AFL1511 | - | 4 | 2026-07-12 |
| AFL1451 | - | 4 | 2026-06-27 |
| AFL1310 | - | 4 | 2026-07-02 |
| AFL1025 | Aeroflot Russian Airlines | 4 | 2026-06-11 |
| AFL615 | - | 3 | 2026-07-13 |
| AFL2145 | Aeroflot Russian Airlines | 3 | 2026-06-28 |
| AFL2144 | Aeroflot Russian Airlines | 3 | 2026-06-28 |
| AFL1450 | - | 3 | 2026-06-26 |
| AFL1198 | Aeroflot Russian Airlines | 3 | 2026-05-11 |
| AFL1017 | Aeroflot Russian Airlines | 3 | 2026-05-28 |
| AFL1008 | Aeroflot Russian Airlines | 3 | 2026-05-31 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | AFL1861 | - | Jul 13, 21:05 UTC | Jul 13, 21:30 UTC | 25m |
| 2026-07-13 | AFL615 | - | Jul 13, 10:30 UTC | Jul 13, 12:00 UTC | 1h 30m |
| 2026-07-12 | AFL1511 | - | Jul 12, 02:50 UTC | Jul 12, 03:05 UTC | 15m |
| 2026-07-12 | AFL1511 | - | Jul 12, 01:20 UTC | Jul 12, 01:45 UTC | 25m |
| 2026-07-11 | AFL2143 | SVO → SVO | Jul 11, 15:30 UTC | Jul 11, 15:45 UTC | 15m |
| 2026-07-11 | AFL2143 | - | Jul 11, 11:10 UTC | Jul 11, 12:55 UTC | 1h 45m |
| 2026-07-11 | AFL2142 | - | Jul 11, 08:30 UTC | Jul 11, 09:40 UTC | 1h 10m |
| 2026-07-09 | AFL1033 | - | Jul 9, 08:40 UTC | Jul 9, 10:10 UTC | 1h 30m |
| 2026-07-08 | AFL1032 | - | Jul 8, 20:55 UTC | Jul 9, 06:25 UTC | 9h 30m |
| 2026-07-08 | AFL2134 | - | Jul 8, 18:20 UTC | Jul 8, 18:45 UTC | 25m |
| 2026-07-07 | AFL1833 | - | Jul 7, 19:25 UTC | Jul 7, 19:40 UTC | 15m |
| 2026-07-07 | AFL1867 | - | Jul 7, 11:40 UTC | Jul 7, 12:10 UTC | 30m |
| 2026-07-06 | AFL1866 | SVO → EVN | Jul 6, 19:25 UTC | Jul 7, 10:00 UTC | 14h 35m |
| 2026-07-06 | AFL1946 | - | Jul 6, 06:50 UTC | Jul 6, 19:35 UTC | 12h 45m |
| 2026-07-04 | AFL1524 | - | Jul 4, 23:10 UTC | Jul 5, 02:45 UTC | 3h 35m |
| 2026-07-04 | AFL1013 | - | Jul 4, 16:35 UTC | Jul 4, 17:35 UTC | 1h 0m |
| 2026-07-04 | AFL1012 | - | Jul 4, 03:25 UTC | Jul 4, 14:35 UTC | 11h 10m |
| 2026-07-03 | AFL1006 | - | Jul 3, 02:30 UTC | Jul 3, 18:05 UTC | 15h 35m |
| 2026-07-02 | AFL1006 | - | Jul 2, 21:10 UTC | Jul 3, 18:05 UTC | 20h 55m |
| 2026-07-02 | AFL1310 | SVO → SVO | Jul 2, 10:40 UTC | Jul 2, 11:05 UTC | 25m |
| 2026-07-01 | AFL1011 | - | Jul 1, 19:00 UTC | Jul 1, 19:50 UTC | 50m |
| 2026-07-01 | AFL1010 | - | Jul 1, 05:45 UTC | Jul 1, 16:55 UTC | 11h 10m |
| 2026-07-01 | AFL2170 | - | Jul 1, 03:20 UTC | Jul 1, 03:50 UTC | 30m |
| 2026-06-30 | AFL1015 | - | Jun 30, 09:30 UTC | Jun 30, 11:10 UTC | 1h 40m |
| 2026-06-29 | AFL2143 | - | Jun 29, 12:34 UTC | Jun 30, 07:55 UTC | 19h 21m |
| 2026-06-29 | AFL2143 | - | Jun 29, 11:35 UTC | Jun 30, 07:55 UTC | 20h 21m |
| 2026-06-28 | AFL2145 | AYT → SVO | Jun 28, 17:10 UTC | Jun 29, 09:25 UTC | 16h 15m |
| 2026-06-28 | AFL2144 | SVO → AYT | Jun 28, 14:50 UTC | Jun 28, 15:09 UTC | 20m |
| 2026-06-27 | AFL1894 | - | Jun 27, 22:20 UTC | Jun 27, 22:55 UTC | 35m |
| 2026-06-27 | AFL2147 | AYT → SVO | Jun 27, 15:19 UTC | Jun 27, 17:09 UTC | 1h 50m |
| 2026-06-27 | AFL2146 | - | Jun 27, 12:25 UTC | Jun 27, 13:35 UTC | 1h 10m |
| 2026-06-27 | AFL2146 | SVO → SVO | Jun 27, 08:49 UTC | Jun 27, 09:15 UTC | 25m |
| 2026-06-27 | AFL1451 | - | Jun 27, 01:19 UTC | Jun 27, 01:49 UTC | 30m |
| 2026-06-26 | AFL1450 | - | Jun 26, 07:24 UTC | Jun 27, 00:00 UTC | 16h 35m |
| 2026-06-25 | AFL1861 | EVN → SVO | Jun 25, 16:24 UTC | Jun 26, 07:55 UTC | 15h 30m |
| 2026-06-25 | AFL615 | - | Jun 25, 10:30 UTC | Jun 25, 11:25 UTC | 55m |
| 2026-06-25 | AFL1860 | - | Jun 25, 05:29 UTC | Jun 25, 08:09 UTC | 2h 40m |
| 2026-06-22 | AFL2143 | - | Jun 22, 12:44 UTC | Jun 22, 14:29 UTC | 1h 45m |
| 2026-06-22 | AFL2142 | - | Jun 22, 08:40 UTC | Jun 22, 09:19 UTC | 40m |
| 2026-06-22 | AFL2142 | SVO → SVO | Jun 22, 04:44 UTC | Jun 22, 05:34 UTC | 50m |
| 2026-06-19 | AFL1319 | - | Jun 19, 21:09 UTC | Jun 20, 08:05 UTC | 10h 55m |
| 2026-06-19 | AFL2134 | - | Jun 19, 14:04 UTC | Jun 19, 14:44 UTC | 40m |
| 2026-06-18 | AFL2147 | AYT → SVO | Jun 18, 18:35 UTC | Jun 18, 20:25 UTC | 1h 50m |
| 2026-06-18 | AFL2146 | - | Jun 18, 15:30 UTC | Jun 18, 17:05 UTC | 1h 35m |
| 2026-06-18 | AFL2146 | SVO → SVO | Jun 18, 11:50 UTC | Jun 18, 12:10 UTC | 20m |
| 2026-06-15 | AFL1033 | KGD → SVO | Jun 15, 10:00 UTC | Jun 15, 11:24 UTC | 1h 25m |
| 2026-06-15 | AFL1032 | SVO → KGD | Jun 15, 07:20 UTC | Jun 15, 08:04 UTC | 45m |
| 2026-06-14 | AFL2147 | AYT → SVO | Jun 14, 20:50 UTC | Jun 15, 01:04 UTC | 4h 14m |
| 2026-06-14 | AFL2146 | - | Jun 14, 18:40 UTC | Jun 14, 19:15 UTC | 35m |
| 2026-06-13 | AFL1886 | - | Jun 13, 06:50 UTC | Jun 13, 15:20 UTC | 8h 30m |
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-73714 page for operator, model, and routing details .