sensors Mode-S transponder
15203C
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73788 · AIRBUS A-330-300
- Hex
- 15203C
- Octal
- 05220074
- Decimal
- 1,384,508
- Country
- RU
- Tail
- RA-73788
- Type
- A333
- Flights observed
- 126
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 15203C 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 |
|---|---|---|---|
| AFL627 | Aeroflot Russian Airlines | 9 | 2026-06-12 |
| AFL628 | Aeroflot Russian Airlines | 7 | 2026-05-10 |
| AFL865 | - | 6 | 2026-07-11 |
| AFL629 | Aeroflot Russian Airlines | 6 | 2026-05-11 |
| AFL233 | - | 6 | 2026-06-24 |
| AFL733 | Aeroflot Russian Airlines | 5 | 2026-05-10 |
| AFL860 | - | 4 | 2026-07-11 |
| AFL832 | - | 4 | 2026-06-20 |
| AFL831 | Aeroflot Russian Airlines | 4 | 2026-05-02 |
| AFL232 | - | 4 | 2026-06-23 |
| AFL1471 | Aeroflot Russian Airlines | 4 | 2026-05-26 |
| AFL863 | - | 3 | 2026-07-13 |
| AFL861 | - | 3 | 2026-07-11 |
| AFL830 | - | 3 | 2026-06-19 |
| AFL650 | - | 3 | 2026-06-21 |
| AFL294 | Aeroflot Russian Airlines | 3 | 2026-04-25 |
| AFL225 | Aeroflot Russian Airlines | 3 | 2026-06-11 |
| AFL224 | Aeroflot Russian Airlines | 3 | 2026-06-10 |
| AFL1411 | Aeroflot Russian Airlines | 3 | 2026-05-24 |
| AFL864 | - | 2 | 2026-07-12 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | AFL863 | - | Jul 13, 03:30 UTC | Jul 13, 18:50 UTC | 15h 20m |
| 2026-07-12 | AFL864 | - | Jul 12, 03:45 UTC | Jul 12, 19:25 UTC | 15h 40m |
| 2026-07-11 | AFL865 | - | Jul 11, 19:55 UTC | Jul 12, 14:50 UTC | 18h 55m |
| 2026-07-11 | AFL865 | - | Jul 11, 15:05 UTC | Jul 12, 14:50 UTC | 23h 45m |
| 2026-07-11 | AFL865 | - | Jul 11, 14:55 UTC | Jul 12, 04:20 UTC | 13h 25m |
| 2026-07-11 | AFL860 | - | Jul 11, 11:05 UTC | Jul 11, 11:25 UTC | 20m |
| 2026-07-11 | AFL861 | - | Jul 11, 03:50 UTC | Jul 11, 07:20 UTC | 3h 30m |
| 2026-07-09 | AFL864 | - | Jul 9, 14:00 UTC | Jul 10, 04:05 UTC | 14h 5m |
| 2026-07-09 | AFL865 | - | Jul 9, 04:15 UTC | Jul 9, 14:30 UTC | 10h 15m |
| 2026-07-08 | AFL860 | - | Jul 8, 14:45 UTC | Jul 8, 19:40 UTC | 4h 55m |
| 2026-07-08 | AFL860 | - | Jul 8, 11:05 UTC | Jul 8, 11:15 UTC | 10m |
| 2026-07-08 | AFL010 | - | Jul 8, 08:00 UTC | Jul 8, 08:15 UTC | 15m |
| 2026-07-06 | AFL213 | - | Jul 6, 11:55 UTC | Jul 6, 12:40 UTC | 45m |
| 2026-07-06 | AFL213 | - | Jul 6, 06:45 UTC | Jul 6, 07:00 UTC | 15m |
| 2026-07-05 | AFL212 | - | Jul 5, 22:20 UTC | Jul 6, 04:50 UTC | 6h 30m |
| 2026-07-05 | AFL212 | SVO → SVO | Jul 5, 19:00 UTC | Jul 5, 19:20 UTC | 20m |
| 2026-07-03 | AFL861 | - | Jul 3, 23:20 UTC | Jul 4, 17:10 UTC | 17h 50m |
| 2026-07-03 | AFL863 | - | Jul 3, 06:25 UTC | Jul 3, 23:55 UTC | 17h 30m |
| 2026-07-02 | AFL863 | - | Jul 2, 22:00 UTC | Jul 3, 12:15 UTC | 14h 15m |
| 2026-07-02 | AFL865 | - | Jul 2, 04:50 UTC | Jul 2, 22:35 UTC | 17h 45m |
| 2026-07-01 | AFL865 | - | Jul 1, 23:45 UTC | Jul 2, 22:35 UTC | 22h 50m |
| 2026-07-01 | AFL860 | - | Jul 1, 14:30 UTC | Jul 1, 19:45 UTC | 5h 15m |
| 2026-06-27 | AFL855 | - | Jun 27, 19:34 UTC | Jun 28, 00:59 UTC | 5h 25m |
| 2026-06-27 | AFL854 | - | Jun 27, 11:25 UTC | Jun 27, 16:35 UTC | 5h 10m |
| 2026-06-24 | AFL233 | - | Jun 24, 02:40 UTC | Jun 24, 03:19 UTC | 40m |
| 2026-06-23 | AFL232 | - | Jun 23, 02:34 UTC | Jun 24, 00:05 UTC | 21h 30m |
| 2026-06-22 | AFL1725 | KHV → SVO | Jun 22, 03:10 UTC | Jun 22, 19:19 UTC | 16h 10m |
| 2026-06-21 | AFL655 | - | Jun 21, 12:10 UTC | Jun 22, 04:30 UTC | 16h 20m |
| 2026-06-21 | AFL650 | - | Jun 21, 03:14 UTC | Jun 21, 09:29 UTC | 6h 15m |
| 2026-06-20 | AFL832 | - | Jun 20, 09:05 UTC | Jun 20, 23:10 UTC | 14h 5m |
| 2026-06-20 | AFL832 | - | Jun 20, 02:44 UTC | Jun 20, 23:10 UTC | 20h 25m |
| 2026-06-19 | AFL832 | - | Jun 19, 19:04 UTC | Jun 20, 18:04 UTC | 23h 0m |
| 2026-06-19 | AFL832 | - | Jun 19, 18:44 UTC | Jun 20, 12:30 UTC | 17h 45m |
| 2026-06-19 | AFL830 | - | Jun 19, 14:04 UTC | Jun 20, 12:30 UTC | 22h 25m |
| 2026-06-12 | AFL837 | SVO → LED | Jun 12, 21:00 UTC | Jun 13, 12:20 UTC | 15h 19m |
| 2026-06-12 | AFL836 | KUF → SVO | Jun 12, 09:05 UTC | Jun 13, 07:05 UTC | 21h 59m |
| 2026-06-12 | AFL627 | HKT → SVX | Jun 12, 07:05 UTC | Jun 13, 07:00 UTC | 23h 54m |
| 2026-06-11 | AFL627 | HKT → SVX | Jun 11, 23:05 UTC | Jun 12, 21:35 UTC | 22h 31m |
| 2026-06-11 | AFL627 | HKT → SVX | Jun 11, 22:45 UTC | Jun 12, 21:00 UTC | 22h 16m |
| 2026-06-11 | AFL1404 | SVO → SVX | Jun 11, 12:50 UTC | Jun 11, 13:10 UTC | 20m |
| 2026-06-11 | AFL225 | SVO → ATH | Jun 11, 07:10 UTC | Jun 11, 07:20 UTC | 10m |
| 2026-06-11 | AFL225 | SVO → ATH | Jun 11, 02:50 UTC | Jun 11, 03:25 UTC | 35m |
| 2026-06-10 | AFL224 | SVO → SYX | Jun 10, 14:00 UTC | Jun 10, 19:05 UTC | 5h 5m |
| 2026-06-10 | AFL224 | SVO → SYX | Jun 10, 10:20 UTC | Jun 10, 10:40 UTC | 20m |
| 2026-06-08 | AFL861 | SYX → LED | Jun 8, 19:05 UTC | Jun 9, 13:45 UTC | 18h 40m |
| 2026-06-08 | AFL862 | KZN → SYX | Jun 8, 18:40 UTC | Jun 9, 13:45 UTC | 19h 5m |
| 2026-06-08 | AFL1780 | SVO → STW | Jun 8, 12:55 UTC | Jun 8, 13:15 UTC | 20m |
| 2026-06-04 | AFL637 | HKT → OVB | Jun 4, 04:25 UTC | Jun 4, 11:20 UTC | 6h 55m |
| 2026-06-01 | AFL634 | KJA → HKT | Jun 1, 09:05 UTC | Jun 2, 04:55 UTC | 19h 50m |
| 2026-06-01 | AFL635 | HKT → KJA | Jun 1, 07:55 UTC | Jun 2, 04:55 UTC | 21h 0m |
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-73788 page for operator, model, and routing details .