sensors Mode-S transponder

151DE9

ICAO 24-bit transponder address · allocated to Russia

Currently assigned to RA-73193 · BOEING 737-800

Hex
151DE9
Octal
05216751
Decimal
1,383,913
Country
RU
Tail
RA-73193
Type
B738
No current signal · last broadcast 1d ago
Flights observed
60
Distinct callsigns
20
Country
RU
Last broadcast
1d ago

Last known position

Most recent position reported by Mode-S 151DE9.

Country allocation

The ICAO 24-bit address 151DE9 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-29 SDM6130 PEE → AER May 29, 00:40 UTCMay 29, 01:00 UTC20m
2026-05-28 SDM6602 SVX → AER May 28, 05:50 UTCMay 28, 14:25 UTC8h 35m
2026-05-27 SDM6605 AER → UFA May 27, 08:00 UTCMay 27, 15:05 UTC7h 5m
2026-05-27 SDM6642 OVB → AER May 27, 04:24 UTCMay 27, 04:49 UTC25m
2026-05-26 SDM6642 OVB → AER May 26, 06:20 UTCMay 27, 04:49 UTC22h 30m
2026-05-26 SDM6601 AER → SVX May 26, 05:49 UTCMay 26, 06:20 UTC30m
2026-05-25 SDM6129 AER → PEE May 25, 19:54 UTCMay 25, 22:49 UTC2h 55m
2026-05-25 SDM6602 SVX → AER May 25, 06:10 UTCMay 25, 13:50 UTC7h 40m
2026-05-23 SDM6201 AER → KZN May 23, 14:20 UTCMay 23, 14:30 UTC10m
2026-05-23 SDM7710 - May 23, 08:45 UTCMay 23, 09:15 UTC30m
2026-05-20 SDM7709 - May 20, 19:25 UTCMay 20, 19:55 UTC30m
2026-05-20 SDM6605 AER → UFA May 20, 09:20 UTCMay 20, 15:10 UTC5h 50m
2026-05-18 SDM6642 OVB → AER May 18, 18:45 UTCMay 19, 03:40 UTC8h 55m
2026-05-18 SDM6642 OVB → AER May 18, 04:20 UTCMay 19, 03:40 UTC23h 19m
2026-05-18 SDM6642 OVB → AER May 18, 03:05 UTCMay 18, 19:30 UTC16h 24m
2026-05-17 SDM6204 KUF → AER May 17, 13:01 UTCMay 18, 04:20 UTC15h 20m
2026-05-16 SDM6204 KUF → AER May 16, 14:31 UTCMay 17, 09:25 UTC18h 55m
2026-05-16 SDM6203 AER → KUF May 16, 11:25 UTCMay 16, 11:35 UTC10m
2026-05-14 SDM6002 IKT → LED May 14, 23:05 UTCMay 15, 10:35 UTC11h 30m
2026-05-12 SDM6108 GOJ → LED May 12, 19:00 UTCMay 12, 19:20 UTC20m
2026-05-12 SDM6107 LED → GOJ May 12, 14:50 UTCMay 12, 15:45 UTC55m
2026-05-12 SDM6002 IKT → LED May 12, 08:45 UTCMay 12, 10:45 UTC2h 0m
2026-05-09 SDM6002 IKT → LED May 9, 06:15 UTCMay 9, 11:10 UTC4h 55m
2026-05-09 SDM6002 IKT → LED May 9, 04:45 UTCMay 9, 04:55 UTC10m
2026-05-08 SDM6002 IKT → LED May 8, 06:20 UTCMay 8, 23:15 UTC16h 55m
2026-05-08 SDM6002 IKT → LED May 8, 04:49 UTCMay 8, 05:00 UTC10m
2026-05-08 SDM6001 LED → IKT May 8, 02:44 UTCMay 8, 02:59 UTC15m
2026-05-07 SDM6001 LED → IKT May 7, 23:05 UTCMay 7, 23:14 UTC10m
2026-05-05 SDM6002 IKT → LED May 5, 08:55 UTCMay 5, 10:30 UTC1h 35m
2026-05-04 SDM6001 LED → IKT May 4, 21:50 UTCMay 4, 22:05 UTC15m
2026-05-03 SDM6310 KGD → SVO May 3, 14:55 UTCMay 3, 22:25 UTC7h 30m
2026-05-02 SDM6662 KGD → SVO May 2, 18:20 UTCMay 3, 13:05 UTC18h 44m
2026-05-02 SDM6662 KGD → SVO May 2, 18:00 UTCMay 3, 13:05 UTC19h 4m
2026-05-02 SDM6661 SVO → KGD May 2, 15:20 UTCMay 2, 15:55 UTC35m
2026-04-29 SDM6312 KGD → SVO Apr 29, 19:35 UTCApr 29, 21:30 UTC1h 55m
2026-04-29 SDM6311 SVO → KGD Apr 29, 17:05 UTCApr 29, 17:45 UTC40m
2026-04-24 SDM6002 IKT → LED Apr 24, 08:45 UTCApr 24, 10:15 UTC1h 30m
2026-04-24 SDM6002 IKT → LED Apr 24, 05:00 UTCApr 24, 05:10 UTC10m
2026-04-24 SDM6001 LED → IKT Apr 24, 03:00 UTCApr 24, 03:10 UTC10m
2026-04-21 SDM6002 IKT → LED Apr 21, 08:50 UTCApr 21, 10:20 UTC1h 30m
2026-04-21 SDM6002 IKT → LED Apr 21, 05:05 UTCApr 21, 05:15 UTC10m
2026-04-21 SDM6001 LED → IKT Apr 21, 03:05 UTCApr 21, 03:20 UTC15m
2026-04-20 SDM6001 LED → IKT Apr 20, 08:30 UTCApr 21, 02:00 UTC17h 30m
2026-04-20 SDM6002 IKT → LED Apr 20, 04:50 UTCApr 21, 02:00 UTC21h 10m
2026-04-20 SDM6001 LED → IKT Apr 20, 03:00 UTCApr 20, 03:10 UTC10m
2026-04-19 SDM6001 LED → IKT Apr 19, 23:10 UTCApr 19, 23:25 UTC15m
2026-04-18 SDM6002 IKT → LED Apr 18, 10:00 UTCApr 18, 10:40 UTC40m
2026-04-18 SDM6002 IKT → LED Apr 18, 05:30 UTCApr 18, 05:45 UTC15m
2026-04-18 SDM6001 LED → IKT Apr 18, 02:55 UTCApr 18, 03:20 UTC25m
2026-04-18 SDM6001 LED → IKT Apr 18, 01:25 UTCApr 18, 01:35 UTC10m

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

Mode-S 151DE9 frequently asked

What is Mode-S code 151DE9?
151DE9 is an ICAO 24-bit transponder address. Allocated to Russia. Assigned to RA-73193.
Where is Mode-S 151DE9 registered?
Mode-S code 151DE9 is allocated to Russia (RU). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 151DE9 broadcasting right now?
No active broadcast right now. Last signal was 1d ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 151DE9, octal 05216751, decimal 1,383,913.
What flights does 151DE9 operate?
Mode-S 151DE9 has broadcast 20 distinct callsigns, including SDM6002, SDM6001, SDM6642, SDM6662, SDM6605.