sensors Mode-S transponder

15203D

ICAO 24-bit transponder address · allocated to Russia

Currently assigned to RA-73789 · AIRBUS A-330-300

Hex
15203D
Octal
05220075
Decimal
1,384,509
Country
RU
Tail
RA-73789
Type
A333
No current signal · last broadcast 6h ago
Flights observed
75
Distinct callsigns
20
Country
RU
Last broadcast
6h ago

Last known position

Most recent position reported by Mode-S 15203D.

Country allocation

The ICAO 24-bit address 15203D 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

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-05-30 AFL224 SVO → SYX May 30, 14:45 UTCMay 30, 15:15 UTC30m
2026-05-30 AFL1553 OVB → SVO May 30, 05:45 UTCMay 30, 05:55 UTC10m
2026-05-29 AFL637 HKT → OVB May 29, 08:30 UTCMay 29, 19:25 UTC10h 55m
2026-05-27 AFL643 KHV → HKT May 27, 13:20 UTCMay 28, 08:10 UTC18h 50m
2026-05-27 AFL643 KHV → HKT May 27, 11:25 UTCMay 28, 08:10 UTC20h 45m
2026-05-27 AFL643 KHV → HKT May 27, 07:20 UTCMay 28, 07:15 UTC23h 55m
2026-05-27 AFL643 KHV → HKT May 27, 07:05 UTCMay 28, 04:15 UTC21h 10m
2026-05-27 AFL642 HKT → KHV May 27, 01:44 UTCMay 27, 23:55 UTC22h 11m
2026-05-26 AFL637 HKT → OVB May 26, 03:45 UTCMay 26, 15:45 UTC12h 0m
2026-05-25 AFL635 HKT → KJA May 25, 08:00 UTCMay 26, 04:54 UTC20h 54m
2026-05-25 AFL643 KHV → HKT May 25, 02:35 UTCMay 25, 09:15 UTC6h 40m
2026-05-24 AFL643 KHV → HKT May 24, 09:20 UTCMay 25, 09:15 UTC23h 55m
2026-05-24 AFL642 HKT → KHV May 24, 08:50 UTCMay 25, 03:50 UTC19h 0m
2026-05-24 AFL642 HKT → KHV May 24, 05:20 UTCMay 25, 03:50 UTC22h 30m
2026-05-24 AFL636 OVB → HKT May 24, 04:35 UTCMay 25, 03:15 UTC22h 40m
2026-05-23 AFL636 OVB → HKT May 23, 23:15 UTCMay 24, 10:05 UTC10h 50m
2026-05-23 AFL1552 SVO → OVB May 23, 12:15 UTCMay 23, 13:40 UTC1h 25m
2026-05-20 AFL225 SVO → ATH May 20, 13:30 UTCMay 21, 06:15 UTC16h 45m
2026-05-18 AFL626 SVX → HKT May 18, 22:15 UTCMay 19, 13:35 UTC15h 20m
2026-05-18 AFL626 SVX → HKT May 18, 19:00 UTCMay 19, 13:35 UTC18h 35m
2026-05-18 AFL627 HKT → SVX May 18, 09:15 UTCMay 18, 13:40 UTC4h 25m
2026-05-17 AFL733 HRG → LED May 17, 11:20 UTCMay 18, 10:15 UTC22h 55m
2026-05-17 AFL733 HRG → LED May 17, 09:20 UTCMay 18, 09:15 UTC23h 55m
2026-05-17 AFL733 HRG → LED May 17, 04:05 UTCMay 17, 12:20 UTC8h 15m
2026-05-16 AFL733 HRG → LED May 16, 11:21 UTCMay 17, 11:15 UTC23h 55m
2026-05-16 AFL735 SSH → LED May 16, 10:01 UTCMay 17, 09:15 UTC23h 15m
2026-05-16 AFL734 LED → SSH May 16, 05:15 UTCMay 16, 07:05 UTC1h 51m
2026-05-14 AFL733 HRG → LED May 14, 05:30 UTCMay 14, 12:40 UTC7h 10m
2026-05-11 AFL861 SYX → LED May 11, 16:10 UTCMay 12, 06:50 UTC14h 40m
2026-05-07 AFL295 SVO → ATH May 7, 21:25 UTCMay 8, 14:45 UTC17h 20m
2026-05-07 AFL294 VCE → SVO May 7, 02:35 UTCMay 8, 01:14 UTC22h 40m
2026-05-06 AFL224 SVO → SYX May 6, 10:35 UTCMay 7, 03:10 UTC16h 34m
2026-05-05 AFL861 SYX → LED May 5, 06:45 UTCMay 5, 07:45 UTC1h 0m
2026-05-03 AFL863 SYX → KZN May 3, 14:45 UTCMay 4, 04:20 UTC13h 35m
2026-05-03 AFL865 SYX → UFA May 3, 05:45 UTCMay 4, 04:20 UTC22h 35m
2026-05-02 AFL865 SYX → UFA May 2, 16:15 UTCMay 3, 15:10 UTC22h 54m
2026-05-02 AFL860 LED → SVO May 2, 12:40 UTCMay 2, 12:55 UTC15m
2026-05-01 AFL861 SYX → LED May 1, 16:10 UTCMay 2, 08:50 UTC16h 41m
2026-05-01 AFL863 SYX → KZN May 1, 03:45 UTCMay 1, 07:00 UTC3h 15m
2026-04-29 AFL860 LED → SVO Apr 29, 10:40 UTCApr 29, 10:55 UTC15m
2026-04-26 AFL1745 UUS → SVO Apr 26, 16:25 UTCApr 27, 08:00 UTC15h 35m
2026-04-26 AFL1744 SVO → UUS Apr 26, 14:45 UTCApr 26, 15:00 UTC15m
2026-04-26 AFL1411 SVX → SVO Apr 26, 11:25 UTCApr 26, 11:50 UTC25m
2026-04-25 AFL1411 SVX → SVO Apr 25, 15:35 UTCApr 26, 10:45 UTC19h 10m
2026-04-25 AFL855 SYX → SVX Apr 25, 09:25 UTCApr 26, 05:40 UTC20h 15m
2026-04-20 AFL626 SVX → HKT Apr 20, 22:50 UTCApr 21, 09:35 UTC10h 45m
2026-04-20 AFL626 SVX → HKT Apr 20, 09:20 UTCApr 21, 09:15 UTC23h 55m
2026-04-20 AFL626 SVX → HKT Apr 20, 07:45 UTCApr 21, 07:15 UTC23h 30m
2026-04-19 AFL627 HKT → SVX Apr 19, 23:20 UTCApr 20, 23:15 UTC23h 55m
2026-04-19 AFL628 LED → HKT Apr 19, 22:35 UTCApr 20, 10:15 UTC11h 40m

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-73789 page for operator, model, and routing details .

Mode-S 15203D frequently asked

What is Mode-S code 15203D?
15203D is an ICAO 24-bit transponder address. Allocated to Russia. Assigned to RA-73789.
Where is Mode-S 15203D registered?
Mode-S code 15203D is allocated to Russia (RU). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 15203D broadcasting right now?
No active broadcast right now. Last signal was 6h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 15203D, octal 05220075, decimal 1,384,509.
What flights does 15203D operate?
Mode-S 15203D has broadcast 20 distinct callsigns, including AFL733, AFL734, AFL643, AFL626, AFL735.