sensors Mode-S transponder
15203B
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73787 · AIRBUS A-330-300
- Hex
- 15203B
- Octal
- 05220073
- Decimal
- 1,384,507
- Country
- RU
- Tail
- RA-73787
- Type
- A333
- Flights observed
- 185
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- Jul 26, 22:20 UTC
Last known position
Country allocation
The ICAO 24-bit address 15203B 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 |
|---|---|---|---|
| AFL733 | - | 19 | 2026-07-12 |
| AFL643 | Aeroflot Russian Airlines | 12 | 2026-07-22 |
| AFL635 | Aeroflot Russian Airlines | 12 | 2026-07-20 |
| AFL629 | - | 11 | 2026-06-23 |
| AFL628 | - | 10 | 2026-07-13 |
| AFL626 | - | 10 | 2026-07-13 |
| AFL735 | - | 8 | 2026-07-11 |
| AFL734 | - | 7 | 2026-07-11 |
| AFL233 | Aeroflot Russian Airlines | 7 | 2026-07-25 |
| AFL232 | Aeroflot Russian Airlines | 7 | 2026-07-25 |
| AFL627 | - | 6 | 2026-06-22 |
| AFL620 | Aeroflot Russian Airlines | 5 | 2026-05-02 |
| AFL225 | - | 5 | 2026-07-18 |
| AFL837 | Aeroflot Russian Airlines | 4 | 2026-06-06 |
| AFL621 | Aeroflot Russian Airlines | 4 | 2026-05-03 |
| AFL293 | - | 4 | 2026-07-16 |
| AFL224 | Aeroflot Russian Airlines | 4 | 2026-07-26 |
| AFL861 | Aeroflot Russian Airlines | 3 | 2026-04-14 |
| AFL831 | Aeroflot Russian Airlines | 3 | 2026-05-23 |
| AFL651 | Aeroflot Russian Airlines | 3 | 2026-05-22 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | AFL224 | SVO → SYX | Jul 26, 13:25 UTC | Jul 26, 22:20 UTC | 8h 55m |
| 2026-07-26 | AFL224 | SVO → SYX | Jul 26, 10:00 UTC | Jul 26, 10:15 UTC | 15m |
| 2026-07-25 | AFL233 | DEL → SVO | Jul 25, 02:40 UTC | Jul 25, 03:35 UTC | 55m |
| 2026-07-25 | AFL232 | SVO → DEL | Jul 25, 00:10 UTC | Jul 25, 00:50 UTC | 40m |
| 2026-07-22 | AFL643 | KHV → HKT | Jul 22, 18:50 UTC | Jul 23, 13:25 UTC | 18h 35m |
| 2026-07-22 | AFL643 | KHV → HKT | Jul 22, 18:40 UTC | Jul 23, 13:25 UTC | 18h 45m |
| 2026-07-22 | AFL643 | KHV → HKT | Jul 22, 14:50 UTC | Jul 23, 13:25 UTC | 22h 35m |
| 2026-07-22 | AFL642 | HKT → KHV | Jul 22, 14:00 UTC | Jul 23, 12:45 UTC | 22h 45m |
| 2026-07-22 | AFL636 | OVB → HKT | Jul 22, 04:50 UTC | Jul 22, 11:20 UTC | 6h 30m |
| 2026-07-21 | AFL637 | HKT → OVB | Jul 21, 03:15 UTC | Jul 21, 10:20 UTC | 7h 5m |
| 2026-07-20 | AFL635 | HKT → KJA | Jul 20, 07:00 UTC | Jul 20, 23:50 UTC | 16h 50m |
| 2026-07-20 | AFL635 | HKT → KJA | Jul 20, 02:50 UTC | Jul 20, 23:50 UTC | 21h 0m |
| 2026-07-20 | AFL635 | HKT → KJA | Jul 20, 01:35 UTC | Jul 20, 23:50 UTC | 22h 15m |
| 2026-07-19 | AFL635 | HKT → KJA | Jul 19, 22:50 UTC | Jul 20, 22:45 UTC | 23h 55m |
| 2026-07-19 | AFL635 | HKT → KJA | Jul 19, 22:40 UTC | Jul 20, 08:50 UTC | 10h 10m |
| 2026-07-19 | AFL635 | HKT → KJA | Jul 19, 13:30 UTC | Jul 20, 08:50 UTC | 19h 20m |
| 2026-07-19 | AFL635 | HKT → KJA | Jul 19, 10:50 UTC | Jul 20, 08:50 UTC | 22h 0m |
| 2026-07-19 | AFL635 | HKT → KJA | Jul 19, 09:00 UTC | Jul 20, 08:45 UTC | 23h 45m |
| 2026-07-19 | AFL636 | OVB → HKT | Jul 19, 03:55 UTC | Jul 19, 05:40 UTC | 1h 45m |
| 2026-07-18 | AFL225 | - | Jul 18, 08:00 UTC | Jul 18, 08:30 UTC | 30m |
| 2026-07-18 | AFL225 | - | Jul 18, 04:05 UTC | Jul 18, 07:20 UTC | 3h 15m |
| 2026-07-17 | AFL225 | - | Jul 17, 11:30 UTC | Jul 18, 07:20 UTC | 19h 51m |
| 2026-07-17 | AFL225 | - | Jul 17, 09:20 UTC | Jul 18, 07:20 UTC | 22h 1m |
| 2026-07-16 | AFL293 | - | Jul 16, 17:25 UTC | Jul 16, 17:35 UTC | 10m |
| 2026-07-16 | AFL292 | - | Jul 16, 00:00 UTC | Jul 16, 12:00 UTC | 12h 0m |
| 2026-07-13 | AFL626 | - | Jul 13, 22:15 UTC | Jul 14, 09:25 UTC | 11h 10m |
| 2026-07-13 | AFL626 | - | Jul 13, 09:25 UTC | Jul 14, 08:45 UTC | 23h 20m |
| 2026-07-13 | AFL626 | - | Jul 13, 07:50 UTC | Jul 14, 02:35 UTC | 18h 45m |
| 2026-07-13 | AFL626 | - | Jul 13, 02:50 UTC | Jul 14, 02:35 UTC | 23h 45m |
| 2026-07-13 | AFL628 | - | Jul 13, 00:50 UTC | Jul 14, 00:35 UTC | 23h 45m |
| 2026-07-12 | AFL628 | - | Jul 12, 22:50 UTC | Jul 13, 22:45 UTC | 23h 55m |
| 2026-07-12 | AFL628 | - | Jul 12, 17:20 UTC | Jul 12, 17:35 UTC | 15m |
| 2026-07-12 | AFL733 | - | Jul 12, 04:15 UTC | Jul 12, 11:20 UTC | 7h 5m |
| 2026-07-11 | AFL733 | - | Jul 11, 12:50 UTC | Jul 12, 11:20 UTC | 22h 30m |
| 2026-07-11 | AFL735 | - | Jul 11, 11:40 UTC | Jul 12, 10:45 UTC | 23h 5m |
| 2026-07-11 | AFL734 | - | Jul 11, 07:35 UTC | Jul 11, 09:10 UTC | 1h 35m |
| 2026-07-09 | AFL2982 | - | Jul 9, 21:15 UTC | Jul 9, 23:20 UTC | 2h 5m |
| 2026-07-09 | AFL733 | - | Jul 9, 15:15 UTC | Jul 9, 15:40 UTC | 25m |
| 2026-07-09 | AFL733 | - | Jul 9, 05:05 UTC | Jul 9, 12:40 UTC | 7h 35m |
| 2026-07-04 | AFL1553 | SVO → SVO | Jul 4, 09:05 UTC | Jul 4, 09:15 UTC | 10m |
| 2026-07-03 | AFL637 | - | Jul 3, 07:35 UTC | Jul 3, 19:25 UTC | 11h 50m |
| 2026-07-02 | AFL635 | - | Jul 2, 08:50 UTC | Jul 3, 08:45 UTC | 23h 55m |
| 2026-07-01 | AFL643 | - | Jul 1, 16:05 UTC | Jul 2, 09:25 UTC | 17h 20m |
| 2026-07-01 | AFL643 | - | Jul 1, 13:00 UTC | Jul 2, 09:25 UTC | 20h 25m |
| 2026-07-01 | AFL643 | - | Jul 1, 11:30 UTC | Jul 2, 09:25 UTC | 21h 55m |
| 2026-07-01 | AFL643 | - | Jul 1, 06:50 UTC | Jul 2, 04:00 UTC | 21h 10m |
| 2026-07-01 | AFL643 | - | Jul 1, 06:25 UTC | Jul 2, 04:00 UTC | 21h 35m |
| 2026-07-01 | AFL642 | - | Jul 1, 01:30 UTC | Jul 1, 23:30 UTC | 22h 0m |
| 2026-06-29 | AFL637 | - | Jun 29, 22:15 UTC | Jun 30, 09:45 UTC | 11h 31m |
| 2026-06-29 | AFL635 | - | Jun 29, 06:59 UTC | Jun 30, 04:45 UTC | 21h 46m |
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-73787 page for operator, model, and routing details .