sensors Mode-S transponder
152039
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73785 · AIRBUS A-330-300
- Hex
- 152039
- Octal
- 05220071
- Decimal
- 1,384,505
- Country
- RU
- Tail
- RA-73785
- Type
- A333
- Flights observed
- 144
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 5h ago
Last known position
Country allocation
The ICAO 24-bit address 152039 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 |
|---|---|---|---|
| AFL232 | - | 14 | 2026-07-02 |
| AFL233 | - | 7 | 2026-07-03 |
| AFL865 | Aeroflot Russian Airlines | 6 | 2026-06-06 |
| AFL733 | Aeroflot Russian Airlines | 6 | 2026-04-26 |
| AFL2983 | - | 6 | 2026-07-11 |
| AFL295 | Aeroflot Russian Airlines | 6 | 2026-04-17 |
| AFL864 | Aeroflot Russian Airlines | 5 | 2026-06-07 |
| AFL862 | Aeroflot Russian Airlines | 5 | 2026-06-05 |
| AFL860 | Aeroflot Russian Airlines | 5 | 2026-06-06 |
| AFL836 | Aeroflot Russian Airlines | 5 | 2026-05-15 |
| AFL627 | Aeroflot Russian Airlines | 5 | 2026-05-14 |
| AFL293 | Aeroflot Russian Airlines | 5 | 2026-05-08 |
| AFL863 | Aeroflot Russian Airlines | 4 | 2026-06-04 |
| AFL855 | - | 4 | 2026-06-23 |
| AFL854 | - | 4 | 2026-07-14 |
| AFL837 | Aeroflot Russian Airlines | 4 | 2026-05-18 |
| AFL598 | Aeroflot Russian Airlines | 4 | 2026-04-18 |
| AFL224 | - | 4 | 2026-06-30 |
| AFL1701 | - | 4 | 2026-07-08 |
| AFL629 | Aeroflot Russian Airlines | 3 | 2026-04-28 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | AFL854 | - | Jul 14, 11:00 UTC | Jul 14, 16:05 UTC | 5h 5m |
| 2026-07-11 | AFL2983 | - | Jul 11, 20:35 UTC | Jul 12, 12:15 UTC | 15h 40m |
| 2026-07-11 | AFL2983 | - | Jul 11, 11:10 UTC | Jul 11, 21:15 UTC | 10h 5m |
| 2026-07-10 | AFL2983 | - | Jul 10, 19:00 UTC | Jul 11, 11:55 UTC | 16h 56m |
| 2026-07-09 | AFL1723 | - | Jul 9, 14:30 UTC | Jul 10, 05:50 UTC | 15h 20m |
| 2026-07-09 | AFL1722 | - | Jul 9, 03:05 UTC | Jul 9, 15:15 UTC | 12h 10m |
| 2026-07-08 | AFL1701 | - | Jul 8, 05:15 UTC | Jul 8, 19:10 UTC | 13h 55m |
| 2026-07-07 | AFL1701 | - | Jul 7, 13:50 UTC | Jul 8, 06:35 UTC | 16h 45m |
| 2026-07-07 | AFL1701 | - | Jul 7, 06:20 UTC | Jul 8, 06:15 UTC | 23h 55m |
| 2026-07-07 | AFL1701 | - | Jul 7, 05:20 UTC | Jul 7, 14:00 UTC | 8h 40m |
| 2026-07-04 | AFL2982 | - | Jul 4, 18:45 UTC | Jul 5, 11:55 UTC | 17h 10m |
| 2026-07-03 | AFL2983 | - | Jul 3, 19:10 UTC | Jul 4, 14:00 UTC | 18h 50m |
| 2026-07-03 | AFL040 | SVO → LED | Jul 3, 16:20 UTC | Jul 3, 16:30 UTC | 10m |
| 2026-07-03 | AFL233 | - | Jul 3, 02:30 UTC | Jul 3, 03:05 UTC | 35m |
| 2026-07-02 | AFL232 | - | Jul 2, 23:30 UTC | Jul 3, 00:15 UTC | 45m |
| 2026-07-02 | AFL233 | - | Jul 2, 03:00 UTC | Jul 2, 07:35 UTC | 4h 35m |
| 2026-07-01 | AFL232 | - | Jul 1, 06:20 UTC | Jul 2, 00:25 UTC | 18h 5m |
| 2026-06-30 | AFL224 | - | Jun 30, 16:25 UTC | Jul 1, 06:55 UTC | 14h 30m |
| 2026-06-30 | AFL233 | - | Jun 30, 02:45 UTC | Jun 30, 21:40 UTC | 18h 55m |
| 2026-06-29 | AFL232 | - | Jun 29, 23:25 UTC | Jun 30, 00:09 UTC | 45m |
| 2026-06-28 | AFL029 | LED → SVO | Jun 28, 16:00 UTC | Jun 28, 16:25 UTC | 25m |
| 2026-06-28 | AFL2983 | - | Jun 28, 11:59 UTC | Jun 28, 12:39 UTC | 40m |
| 2026-06-26 | AFL1745 | - | Jun 26, 06:35 UTC | Jun 26, 07:50 UTC | 1h 15m |
| 2026-06-25 | AFL233 | - | Jun 25, 04:10 UTC | Jun 25, 04:49 UTC | 40m |
| 2026-06-25 | AFL232 | - | Jun 25, 00:59 UTC | Jun 25, 01:50 UTC | 50m |
| 2026-06-24 | AFL232 | - | Jun 24, 04:20 UTC | Jun 25, 01:50 UTC | 21h 30m |
| 2026-06-24 | AFL232 | - | Jun 24, 03:44 UTC | Jun 25, 01:50 UTC | 22h 5m |
| 2026-06-23 | AFL855 | - | Jun 23, 23:10 UTC | Jun 24, 04:20 UTC | 5h 10m |
| 2026-06-23 | AFL854 | - | Jun 23, 03:49 UTC | Jun 23, 16:35 UTC | 12h 45m |
| 2026-06-20 | AFL2982 | - | Jun 20, 18:54 UTC | Jun 20, 21:00 UTC | 2h 5m |
| 2026-06-19 | AFL2983 | - | Jun 19, 18:59 UTC | Jun 20, 12:54 UTC | 17h 55m |
| 2026-06-19 | AFL233 | - | Jun 19, 03:44 UTC | Jun 19, 04:25 UTC | 40m |
| 2026-06-18 | AFL232 | - | Jun 18, 23:25 UTC | Jun 19, 00:14 UTC | 49m |
| 2026-06-18 | AFL232 | - | Jun 18, 02:55 UTC | Jun 19, 00:14 UTC | 21h 19m |
| 2026-06-17 | AFL232 | - | Jun 17, 23:35 UTC | Jun 18, 00:15 UTC | 40m |
| 2026-06-17 | AFL232 | SVO → SVO | Jun 17, 19:00 UTC | Jun 17, 19:45 UTC | 45m |
| 2026-06-16 | AFL855 | SYX → SVX | Jun 16, 23:20 UTC | Jun 17, 05:35 UTC | 6h 15m |
| 2026-06-16 | AFL854 | SVX → SYX | Jun 16, 12:00 UTC | Jun 16, 17:10 UTC | 5h 10m |
| 2026-06-15 | AFL233 | - | Jun 15, 03:00 UTC | Jun 15, 07:45 UTC | 4h 45m |
| 2026-06-14 | AFL232 | SVO → DEL | Jun 14, 23:59 UTC | Jun 15, 00:40 UTC | 40m |
| 2026-06-14 | AFL855 | SYX → SVX | Jun 14, 01:25 UTC | Jun 15, 00:15 UTC | 22h 50m |
| 2026-06-13 | AFL855 | SYX → SVX | Jun 13, 20:15 UTC | Jun 14, 02:00 UTC | 5h 45m |
| 2026-06-13 | AFL854 | SVX → SYX | Jun 13, 11:25 UTC | Jun 13, 16:45 UTC | 5h 20m |
| 2026-06-13 | AFL1410 | SVO → SVX | Jun 13, 03:50 UTC | Jun 13, 04:10 UTC | 20m |
| 2026-06-12 | AFL233 | DEL → SVO | Jun 12, 03:00 UTC | Jun 12, 07:55 UTC | 4h 55m |
| 2026-06-11 | AFL232 | SVO → DEL | Jun 11, 20:30 UTC | Jun 12, 00:45 UTC | 4h 16m |
| 2026-06-11 | AFL232 | SVO → DEL | Jun 11, 03:00 UTC | Jun 12, 00:45 UTC | 21h 45m |
| 2026-06-10 | AFL232 | SVO → DEL | Jun 10, 20:10 UTC | Jun 11, 00:10 UTC | 4h 0m |
| 2026-06-10 | AFL225 | SVO → ATH | Jun 10, 08:25 UTC | Jun 10, 08:40 UTC | 15m |
| 2026-06-09 | AFL224 | SVO → SYX | Jun 9, 10:20 UTC | Jun 10, 05:05 UTC | 18h 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-73785 page for operator, model, and routing details .