sensors Mode-S transponder
151DC7
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73159 · AIRBUS A-330-300
- Hex
- 151DC7
- Octal
- 05216707
- Decimal
- 1,383,879
- Country
- RU
- Tail
- RA-73159
- Type
- A333
- Flights observed
- 174
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- Jul 26, 20:25 UTC
Last known position
Country allocation
The ICAO 24-bit address 151DC7 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 |
|---|---|---|---|
| AFL831 | - | 10 | 2026-07-11 |
| AFL863 | Aeroflot Russian Airlines | 9 | 2026-07-24 |
| AFL865 | Aeroflot Russian Airlines | 8 | 2026-07-25 |
| AFL837 | - | 8 | 2026-06-23 |
| AFL292 | - | 8 | 2026-06-26 |
| AFL861 | Aeroflot Russian Airlines | 7 | 2026-07-25 |
| AFL860 | Aeroflot Russian Airlines | 7 | 2026-07-25 |
| AFL733 | - | 6 | 2026-07-19 |
| AFL650 | - | 6 | 2026-07-12 |
| AFL636 | Aeroflot Russian Airlines | 6 | 2026-05-13 |
| AFL832 | - | 5 | 2026-07-07 |
| AFL830 | - | 5 | 2026-07-10 |
| AFL654 | - | 5 | 2026-07-09 |
| AFL651 | - | 5 | 2026-07-10 |
| AFL637 | Aeroflot Russian Airlines | 5 | 2026-05-15 |
| AFL635 | Aeroflot Russian Airlines | 5 | 2026-05-14 |
| AFL628 | - | 4 | 2026-07-19 |
| AFL293 | Aeroflot Russian Airlines | 4 | 2026-06-04 |
| AFL232 | - | 4 | 2026-06-27 |
| AFL855 | Aeroflot Russian Airlines | 3 | 2026-06-06 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-25 | AFL865 | SYX → UFA | Jul 25, 21:50 UTC | Jul 26, 20:25 UTC | 22h 36m |
| 2026-07-25 | AFL860 | LED → SVO | Jul 25, 16:55 UTC | Jul 26, 15:45 UTC | 22h 51m |
| 2026-07-25 | AFL861 | SYX → LED | Jul 25, 06:35 UTC | Jul 25, 21:50 UTC | 15h 15m |
| 2026-07-24 | AFL861 | SYX → LED | Jul 24, 21:40 UTC | Jul 25, 17:30 UTC | 19h 50m |
| 2026-07-24 | AFL861 | SYX → LED | Jul 24, 16:45 UTC | Jul 25, 07:20 UTC | 14h 35m |
| 2026-07-24 | AFL863 | SYX → KZN | Jul 24, 04:05 UTC | Jul 24, 21:40 UTC | 17h 35m |
| 2026-07-23 | AFL864 | UFA → SYX | Jul 23, 04:15 UTC | Jul 23, 18:40 UTC | 14h 25m |
| 2026-07-22 | AFL860 | - | Jul 22, 14:35 UTC | Jul 23, 13:45 UTC | 23h 10m |
| 2026-07-22 | AFL860 | - | Jul 22, 11:20 UTC | Jul 23, 04:45 UTC | 17h 25m |
| 2026-07-21 | AFL7777 | - | Jul 21, 18:35 UTC | Jul 21, 19:40 UTC | 1h 5m |
| 2026-07-20 | AFL629 | HKT → LED | Jul 20, 22:00 UTC | Jul 21, 09:30 UTC | 11h 29m |
| 2026-07-20 | AFL629 | HKT → LED | Jul 20, 09:50 UTC | Jul 21, 09:30 UTC | 23h 39m |
| 2026-07-20 | AFL627 | HKT → SVX | Jul 20, 07:50 UTC | Jul 21, 07:45 UTC | 23h 54m |
| 2026-07-20 | AFL627 | HKT → SVX | Jul 20, 00:25 UTC | Jul 20, 22:55 UTC | 22h 30m |
| 2026-07-19 | AFL628 | - | Jul 19, 22:45 UTC | Jul 20, 10:15 UTC | 11h 30m |
| 2026-07-19 | AFL628 | - | Jul 19, 17:20 UTC | Jul 19, 17:40 UTC | 20m |
| 2026-07-19 | AFL733 | - | Jul 19, 03:55 UTC | Jul 19, 11:10 UTC | 7h 15m |
| 2026-07-18 | AFL733 | - | Jul 18, 11:50 UTC | Jul 19, 11:10 UTC | 23h 20m |
| 2026-07-18 | AFL735 | - | Jul 18, 10:00 UTC | Jul 19, 09:45 UTC | 23h 45m |
| 2026-07-18 | AFL734 | - | Jul 18, 05:50 UTC | Jul 18, 07:20 UTC | 1h 30m |
| 2026-07-17 | AFL2983 | - | Jul 17, 15:40 UTC | Jul 17, 15:55 UTC | 15m |
| 2026-07-17 | AFL2983 | - | Jul 17, 13:45 UTC | Jul 17, 14:24 UTC | 40m |
| 2026-07-15 | AFL735 | - | Jul 15, 10:10 UTC | Jul 15, 11:30 UTC | 1h 20m |
| 2026-07-14 | AFL734 | - | Jul 14, 11:50 UTC | Jul 15, 07:50 UTC | 19h 59m |
| 2026-07-14 | AFL733 | - | Jul 14, 09:50 UTC | Jul 15, 07:50 UTC | 21h 59m |
| 2026-07-14 | AFL733 | - | Jul 14, 05:35 UTC | Jul 14, 12:20 UTC | 6h 45m |
| 2026-07-12 | AFL1725 | - | Jul 12, 13:30 UTC | Jul 13, 04:20 UTC | 14h 50m |
| 2026-07-12 | AFL655 | - | Jul 12, 12:10 UTC | Jul 12, 12:25 UTC | 15m |
| 2026-07-12 | AFL650 | - | Jul 12, 08:50 UTC | Jul 12, 09:00 UTC | 10m |
| 2026-07-12 | AFL650 | - | Jul 12, 03:01 UTC | Jul 12, 08:15 UTC | 5h 15m |
| 2026-07-11 | AFL831 | - | Jul 11, 09:05 UTC | Jul 11, 23:05 UTC | 14h 0m |
| 2026-07-11 | AFL831 | - | Jul 11, 02:50 UTC | Jul 11, 23:05 UTC | 20h 15m |
| 2026-07-10 | AFL831 | - | Jul 10, 23:50 UTC | Jul 11, 23:05 UTC | 23h 15m |
| 2026-07-10 | AFL833 | - | Jul 10, 18:50 UTC | Jul 11, 17:45 UTC | 22h 55m |
| 2026-07-10 | AFL830 | - | Jul 10, 13:50 UTC | Jul 11, 11:45 UTC | 21h 56m |
| 2026-07-10 | AFL651 | - | Jul 10, 03:40 UTC | Jul 10, 10:05 UTC | 6h 25m |
| 2026-07-09 | AFL654 | - | Jul 9, 09:15 UTC | Jul 10, 00:25 UTC | 15h 10m |
| 2026-07-09 | AFL650 | - | Jul 9, 00:10 UTC | Jul 9, 06:25 UTC | 6h 15m |
| 2026-07-08 | AFL831 | - | Jul 8, 06:30 UTC | Jul 8, 20:05 UTC | 13h 35m |
| 2026-07-08 | AFL831 | - | Jul 8, 00:00 UTC | Jul 8, 20:05 UTC | 20h 5m |
| 2026-07-07 | AFL832 | - | Jul 7, 21:10 UTC | Jul 8, 19:45 UTC | 22h 35m |
| 2026-07-07 | AFL832 | - | Jul 7, 14:20 UTC | Jul 8, 09:50 UTC | 19h 30m |
| 2026-07-07 | AFL830 | - | Jul 7, 09:50 UTC | Jul 8, 09:45 UTC | 23h 55m |
| 2026-07-07 | AFL830 | - | Jul 7, 09:40 UTC | Jul 8, 06:50 UTC | 21h 10m |
| 2026-07-06 | AFL651 | - | Jul 6, 23:50 UTC | Jul 7, 06:30 UTC | 6h 40m |
| 2026-07-06 | AFL654 | - | Jul 6, 05:35 UTC | Jul 6, 21:00 UTC | 15h 25m |
| 2026-07-04 | AFL294 | - | Jul 4, 21:30 UTC | Jul 5, 10:40 UTC | 13h 10m |
| 2026-07-02 | AFL628 | - | Jul 2, 00:45 UTC | Jul 2, 11:40 UTC | 10h 55m |
| 2026-07-01 | AFL628 | - | Jul 1, 19:30 UTC | Jul 1, 19:45 UTC | 15m |
| 2026-07-01 | AFL735 | - | Jul 1, 10:35 UTC | Jul 1, 13:20 UTC | 2h 45m |
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-73159 page for operator, model, and routing details .