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
No current signal · last broadcast 2h ago
Flights observed
71
Distinct callsigns
20
Country
RU
Last broadcast
2h ago

Last known position

Most recent position reported by Mode-S 152039.

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

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-05-30 AFL860 LED → SVO May 30, 14:50 UTCMay 30, 15:10 UTC20m
2026-05-29 AFL862 KZN → SYX May 29, 18:25 UTCMay 30, 11:20 UTC16h 55m
2026-05-29 AFL862 KZN → SYX May 29, 04:40 UTCMay 30, 03:05 UTC22h 25m
2026-05-28 AFL863 SYX → KZN May 28, 23:40 UTCMay 29, 18:50 UTC19h 10m
2026-05-28 AFL865 SYX → UFA May 28, 04:10 UTCMay 28, 20:10 UTC16h 0m
2026-05-27 AFL865 SYX → UFA May 27, 19:40 UTCMay 28, 15:15 UTC19h 35m
2026-05-27 AFL865 SYX → UFA May 27, 10:50 UTCMay 28, 04:50 UTC18h 0m
2026-05-27 AFL010 SVO → LED May 27, 08:05 UTCMay 27, 08:15 UTC10m
2026-05-18 AFL837 SVO → LED May 18, 13:20 UTCMay 19, 06:00 UTC16h 39m
2026-05-18 AFL1470 SVO → SVX May 18, 12:10 UTCMay 18, 12:25 UTC15m
2026-05-15 AFL836 KUF → SVO May 15, 17:35 UTCMay 16, 10:16 UTC16h 41m
2026-05-15 AFL836 KUF → SVO May 15, 13:25 UTCMay 16, 10:16 UTC20h 50m
2026-05-15 AFL836 KUF → SVO May 15, 07:30 UTCMay 16, 00:45 UTC17h 14m
2026-05-15 AFL836 KUF → SVO May 15, 00:20 UTCMay 16, 00:15 UTC23h 54m
2026-05-14 AFL627 HKT → SVX May 14, 22:55 UTCMay 15, 22:15 UTC23h 19m
2026-05-14 AFL627 HKT → SVX May 14, 19:50 UTCMay 15, 17:40 UTC21h 49m
2026-05-14 AFL627 HKT → SVX May 14, 13:05 UTCMay 15, 10:05 UTC21h 0m
2026-05-10 AFL213 HKG → SVO May 10, 10:05 UTCMay 10, 13:35 UTC3h 30m
2026-05-10 AFL213 HKG → SVO May 10, 04:25 UTCMay 10, 04:39 UTC15m
2026-05-10 AFL212 SVO → HKG May 10, 01:14 UTCMay 10, 01:34 UTC20m
2026-05-09 AFL212 SVO → HKG May 9, 19:40 UTCMay 9, 23:05 UTC3h 25m
2026-05-08 AFL293 SGN → SVO May 8, 21:10 UTCMay 9, 13:30 UTC16h 20m
2026-05-08 AFL293 SGN → SVO May 8, 17:30 UTCMay 9, 13:30 UTC20h 0m
2026-05-08 AFL293 SGN → SVO May 8, 10:29 UTCMay 9, 09:10 UTC22h 40m
2026-05-07 AFL1735 PKC → SVO May 7, 18:20 UTCMay 8, 17:40 UTC23h 20m
2026-05-05 AFL1471 SVX → SVO May 5, 09:30 UTCMay 5, 23:25 UTC13h 55m
2026-05-04 AFL1471 SVX → SVO May 4, 18:20 UTCMay 5, 17:35 UTC23h 16m
2026-05-04 AFL837 SVO → LED May 4, 18:10 UTCMay 5, 10:05 UTC15h 56m
2026-05-04 AFL837 SVO → LED May 4, 12:55 UTCMay 5, 10:05 UTC21h 11m
2026-05-01 AFL298 - May 1, 22:20 UTCMay 2, 12:10 UTC13h 50m
2026-04-29 AFL293 SGN → SVO Apr 29, 20:55 UTCApr 30, 14:05 UTC17h 10m
2026-04-29 AFL293 SGN → SVO Apr 29, 17:15 UTCApr 30, 14:05 UTC20h 50m
2026-04-29 AFL029 LED → SVO Apr 29, 06:05 UTCApr 29, 06:59 UTC55m
2026-04-28 AFL629 HKT → LED Apr 28, 10:40 UTCApr 28, 12:30 UTC1h 50m
2026-04-28 AFL629 HKT → LED Apr 28, 09:25 UTCApr 28, 10:30 UTC1h 5m
2026-04-27 AFL627 HKT → SVX Apr 27, 10:20 UTCApr 28, 10:15 UTC23h 55m
2026-04-26 AFL627 HKT → SVX Apr 26, 17:15 UTCApr 27, 12:15 UTC19h 0m
2026-04-26 AFL733 HRG → LED Apr 26, 10:50 UTCApr 27, 10:15 UTC23h 25m
2026-04-26 AFL733 HRG → LED Apr 26, 02:45 UTCApr 26, 17:20 UTC14h 35m
2026-04-25 AFL732 LED → HRG Apr 25, 10:20 UTCApr 26, 10:10 UTC23h 50m
2026-04-25 AFL732 LED → HRG Apr 25, 06:20 UTCApr 26, 05:10 UTC22h 50m
2026-04-24 AFL734 LED → SSH Apr 24, 12:20 UTCApr 25, 11:40 UTC23h 20m
2026-04-24 AFL621 BKK → LED Apr 24, 10:20 UTCApr 25, 07:40 UTC21h 20m
2026-04-24 AFL621 BKK → LED Apr 24, 08:25 UTCApr 25, 07:40 UTC23h 15m
2026-04-23 AFL620 LED → BKK Apr 23, 22:50 UTCApr 24, 06:30 UTC7h 40m
2026-04-23 AFL620 LED → BKK Apr 23, 10:20 UTCApr 24, 06:30 UTC20h 10m
2026-04-23 AFL620 LED → BKK Apr 23, 08:30 UTCApr 24, 06:30 UTC21h 59m
2026-04-23 AFL629 HKT → LED Apr 23, 02:25 UTCApr 23, 22:55 UTC20h 30m
2026-04-22 AFL735 SSH → LED Apr 22, 10:20 UTCApr 23, 02:20 UTC16h 0m
2026-04-21 AFL734 LED → SSH Apr 21, 12:20 UTCApr 22, 07:20 UTC19h 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-73785 page for operator, model, and routing details .

Mode-S 152039 frequently asked

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