sensors Mode-S transponder
15203A
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73786 · AIRBUS A-330-300
- Hex
- 15203A
- Octal
- 05220072
- Decimal
- 1,384,506
- Country
- RU
- Tail
- RA-73786
- Type
- A333
- Flights observed
- 121
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address 15203A 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 |
|---|---|---|---|
| AFL643 | - | 10 | 2026-06-18 |
| AFL837 | - | 8 | 2026-07-10 |
| AFL642 | Aeroflot Russian Airlines | 7 | 2026-06-17 |
| AFL832 | Aeroflot Russian Airlines | 6 | 2026-06-05 |
| AFL650 | Aeroflot Russian Airlines | 6 | 2026-06-07 |
| AFL655 | Aeroflot Russian Airlines | 5 | 2026-06-07 |
| AFL651 | Aeroflot Russian Airlines | 5 | 2026-06-05 |
| AFL232 | - | 5 | 2026-06-21 |
| AFL855 | - | 4 | 2026-07-05 |
| AFL831 | Aeroflot Russian Airlines | 4 | 2026-06-06 |
| AFL830 | Aeroflot Russian Airlines | 4 | 2026-06-05 |
| AFL637 | Aeroflot Russian Airlines | 4 | 2026-06-19 |
| AFL233 | - | 4 | 2026-06-22 |
| AFL654 | Aeroflot Russian Airlines | 3 | 2026-06-01 |
| AFL652 | Aeroflot Russian Airlines | 3 | 2026-04-26 |
| AFL627 | - | 3 | 2026-07-10 |
| AFL224 | - | 3 | 2026-06-28 |
| AFL863 | Aeroflot Russian Airlines | 2 | 2026-05-08 |
| AFL860 | Aeroflot Russian Airlines | 2 | 2026-05-06 |
| AFL734 | - | 2 | 2026-06-23 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | AFL7775 | - | Jul 14, 06:35 UTC | Jul 14, 07:15 UTC | 40m |
| 2026-07-10 | AFL837 | - | Jul 10, 19:00 UTC | Jul 11, 10:30 UTC | 15h 31m |
| 2026-07-10 | AFL836 | - | Jul 10, 08:35 UTC | Jul 11, 05:25 UTC | 20h 50m |
| 2026-07-10 | AFL627 | - | Jul 10, 07:00 UTC | Jul 11, 05:25 UTC | 22h 25m |
| 2026-07-10 | AFL627 | - | Jul 10, 00:35 UTC | Jul 11, 00:05 UTC | 23h 30m |
| 2026-07-09 | AFL626 | - | Jul 9, 22:35 UTC | Jul 10, 19:25 UTC | 20h 50m |
| 2026-07-07 | AFL854 | - | Jul 7, 13:05 UTC | Jul 8, 06:00 UTC | 16h 55m |
| 2026-07-05 | AFL1701 | - | Jul 5, 14:15 UTC | Jul 6, 06:45 UTC | 16h 30m |
| 2026-07-05 | AFL855 | - | Jul 5, 00:30 UTC | Jul 5, 14:15 UTC | 13h 45m |
| 2026-07-04 | AFL855 | - | Jul 4, 11:50 UTC | Jul 5, 01:05 UTC | 13h 15m |
| 2026-06-30 | AFL855 | - | Jun 30, 11:15 UTC | Jul 1, 04:30 UTC | 17h 15m |
| 2026-06-28 | AFL224 | - | Jun 28, 10:04 UTC | Jun 29, 03:29 UTC | 17h 25m |
| 2026-06-26 | AFL007 | LED → LED | Jun 26, 07:05 UTC | Jun 26, 07:35 UTC | 30m |
| 2026-06-24 | AFL628 | - | Jun 24, 23:34 UTC | Jun 25, 10:59 UTC | 11h 25m |
| 2026-06-24 | AFL628 | - | Jun 24, 18:20 UTC | Jun 24, 18:29 UTC | 10m |
| 2026-06-24 | AFL735 | - | Jun 24, 09:55 UTC | Jun 24, 13:14 UTC | 3h 20m |
| 2026-06-23 | AFL734 | - | Jun 23, 10:35 UTC | Jun 24, 07:15 UTC | 20h 40m |
| 2026-06-23 | AFL734 | - | Jun 23, 09:24 UTC | Jun 24, 07:15 UTC | 21h 50m |
| 2026-06-23 | AFL732 | - | Jun 23, 05:00 UTC | Jun 23, 10:55 UTC | 5h 55m |
| 2026-06-22 | AFL026 | - | Jun 22, 16:45 UTC | Jun 22, 17:50 UTC | 1h 5m |
| 2026-06-22 | AFL233 | - | Jun 22, 02:50 UTC | Jun 22, 03:30 UTC | 40m |
| 2026-06-21 | AFL232 | - | Jun 21, 23:24 UTC | Jun 22, 00:10 UTC | 45m |
| 2026-06-21 | AFL232 | - | Jun 21, 02:40 UTC | Jun 22, 00:10 UTC | 21h 30m |
| 2026-06-20 | AFL232 | - | Jun 20, 19:55 UTC | Jun 20, 23:59 UTC | 4h 5m |
| 2026-06-19 | AFL637 | HKT → OVB | Jun 19, 10:44 UTC | Jun 19, 21:30 UTC | 10h 45m |
| 2026-06-18 | AFL643 | - | Jun 18, 03:50 UTC | Jun 18, 09:30 UTC | 5h 40m |
| 2026-06-17 | AFL643 | - | Jun 17, 12:35 UTC | Jun 18, 09:30 UTC | 20h 55m |
| 2026-06-17 | AFL642 | HKT → KHV | Jun 17, 12:20 UTC | Jun 18, 09:30 UTC | 21h 10m |
| 2026-06-17 | AFL642 | HKT → KHV | Jun 17, 08:35 UTC | Jun 18, 08:30 UTC | 23h 55m |
| 2026-06-17 | AFL642 | HKT → KHV | Jun 17, 07:50 UTC | Jun 18, 05:50 UTC | 22h 0m |
| 2026-06-17 | AFL642 | HKT → KHV | Jun 17, 01:50 UTC | Jun 17, 14:30 UTC | 12h 40m |
| 2026-06-16 | AFL637 | HKT → OVB | Jun 16, 03:45 UTC | Jun 16, 15:45 UTC | 12h 0m |
| 2026-06-15 | AFL634 | KJA → HKT | Jun 15, 08:35 UTC | Jun 16, 04:30 UTC | 19h 55m |
| 2026-06-15 | AFL635 | HKT → KJA | Jun 15, 08:00 UTC | Jun 16, 04:30 UTC | 20h 30m |
| 2026-06-15 | AFL643 | - | Jun 15, 01:30 UTC | Jun 15, 09:20 UTC | 7h 50m |
| 2026-06-14 | AFL643 | - | Jun 14, 10:50 UTC | Jun 15, 09:20 UTC | 22h 30m |
| 2026-06-14 | AFL642 | HKT → KHV | Jun 14, 09:15 UTC | Jun 15, 08:29 UTC | 23h 14m |
| 2026-06-14 | AFL642 | HKT → KHV | Jun 14, 04:50 UTC | Jun 15, 03:30 UTC | 22h 39m |
| 2026-06-13 | AFL642 | HKT → KHV | Jun 13, 23:05 UTC | Jun 14, 11:25 UTC | 12h 20m |
| 2026-06-13 | AFL1552 | SVO → OVB | Jun 13, 13:40 UTC | Jun 13, 14:10 UTC | 30m |
| 2026-06-09 | AFL837 | SVO → LED | Jun 9, 04:15 UTC | Jun 9, 21:10 UTC | 16h 55m |
| 2026-06-08 | AFL837 | SVO → LED | Jun 8, 23:15 UTC | Jun 9, 21:10 UTC | 21h 55m |
| 2026-06-08 | AFL837 | SVO → LED | Jun 8, 13:25 UTC | Jun 9, 09:50 UTC | 20h 25m |
| 2026-06-08 | AFL837 | SVO → LED | Jun 8, 12:00 UTC | Jun 9, 09:50 UTC | 21h 50m |
| 2026-06-07 | AFL655 | BKK → KHV | Jun 7, 12:10 UTC | Jun 8, 03:30 UTC | 15h 20m |
| 2026-06-07 | AFL650 | OVB → BKK | Jun 7, 02:55 UTC | Jun 7, 08:50 UTC | 5h 55m |
| 2026-06-06 | AFL831 | CXR → OVB | Jun 6, 09:24 UTC | Jun 6, 23:19 UTC | 13h 55m |
| 2026-06-06 | AFL831 | CXR → OVB | Jun 6, 02:40 UTC | Jun 6, 23:19 UTC | 20h 40m |
| 2026-06-05 | AFL832 | KUF → SVO | Jun 5, 23:45 UTC | Jun 6, 18:04 UTC | 18h 20m |
| 2026-06-05 | AFL832 | KUF → SVO | Jun 5, 18:45 UTC | Jun 6, 18:04 UTC | 23h 20m |
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-73786 page for operator, model, and routing details .