sensors Mode-S transponder

151DF9

ICAO 24-bit transponder address · allocated to Russia

Currently assigned to RA-73209 · BOEING 737-800

Hex
151DF9
Octal
05216771
Decimal
1,383,929
Country
RU
Tail
RA-73209
Type
B738
No current signal · last broadcast 15h ago
Flights observed
90
Distinct callsigns
20
Country
RU
Last broadcast
15h ago

Last known position

Most recent position reported by Mode-S 151DF9.

Country allocation

The ICAO 24-bit address 151DF9 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-28 SDM5968 SSH → KUF May 28, 21:10 UTCMay 29, 14:15 UTC17h 5m
2026-05-28 SDM5969 PEE → SSH May 28, 05:45 UTCMay 28, 19:20 UTC13h 35m
2026-05-27 SDM5976 SSH → UFA May 27, 11:00 UTCMay 28, 03:40 UTC16h 40m
2026-05-26 SDM5976 SSH → UFA May 26, 22:25 UTCMay 27, 18:40 UTC20h 15m
2026-05-26 SDM5966 SSH → GOJ May 26, 20:29 UTCMay 27, 18:40 UTC22h 10m
2026-05-26 SDM5954 HRG → SVO May 26, 01:40 UTCMay 26, 18:19 UTC16h 40m
2026-05-23 SDM5980 HRG → GOJ May 23, 22:50 UTCMay 24, 17:40 UTC18h 50m
2026-05-23 SDM5964 HRG → KUF May 23, 06:30 UTCMay 24, 01:30 UTC19h 0m
2026-05-23 SDM5964 HRG → KUF May 23, 02:20 UTCMay 24, 01:30 UTC23h 10m
2026-05-20 SDM6365 SVO → TJM May 20, 22:15 UTCMay 21, 12:15 UTC14h 0m
2026-05-19 SDM6002 IKT → LED May 19, 06:25 UTCMay 19, 10:15 UTC3h 50m
2026-05-18 SDM6002 IKT → LED May 18, 08:30 UTCMay 19, 06:50 UTC22h 19m
2026-05-17 SDM6002 IKT → LED May 17, 23:25 UTCMay 18, 10:05 UTC10h 40m
2026-05-17 SDM6310 KGD → SVO May 17, 12:20 UTCMay 18, 10:05 UTC21h 45m
2026-05-17 SDM6310 KGD → SVO May 17, 11:45 UTCMay 18, 10:05 UTC22h 20m
2026-05-16 SDM6312 KGD → SVO May 16, 19:35 UTCMay 17, 09:55 UTC14h 20m
2026-05-16 SDM6272 LED → SVO May 16, 12:55 UTCMay 16, 13:15 UTC20m
2026-05-16 SDM6002 IKT → LED May 16, 01:25 UTCMay 16, 10:25 UTC9h 1m
2026-05-13 SDM6314 KGD → SVO May 13, 14:00 UTCMay 13, 15:05 UTC1h 5m
2026-05-13 SDM6313 SVO → KGD May 13, 11:20 UTCMay 13, 12:00 UTC40m
2026-05-11 SDM5954 HRG → SVO May 11, 22:15 UTCMay 12, 09:15 UTC11h 0m
2026-05-10 SDM5963 KUF → HRG May 10, 07:19 UTCMay 10, 18:09 UTC10h 50m
2026-05-09 SDM5977 CEK → HRG May 9, 06:25 UTCMay 10, 01:30 UTC19h 5m
2026-05-09 SDM5977 CEK → HRG May 9, 02:50 UTCMay 10, 01:30 UTC22h 40m
2026-05-08 SDM5978 HRG → CEK May 8, 18:20 UTCMay 9, 18:15 UTC23h 55m
2026-05-08 SDM5978 HRG → CEK May 8, 17:50 UTCMay 9, 16:15 UTC22h 25m
2026-05-08 SDM6661 SVO → KGD May 8, 15:20 UTCMay 8, 16:00 UTC40m
2026-05-07 SDM6310 KGD → SVO May 7, 13:20 UTCMay 7, 19:40 UTC6h 20m
2026-05-07 SDM6309 SVO → KGD May 7, 10:30 UTCMay 7, 11:10 UTC40m
2026-05-05 SDM5954 HRG → SVO May 5, 17:45 UTCMay 6, 01:05 UTC7h 20m
2026-05-03 SDM5980 HRG → GOJ May 3, 10:15 UTCMay 3, 18:25 UTC8h 10m
2026-05-02 SDM5964 HRG → KUF May 2, 08:20 UTCMay 3, 04:00 UTC19h 39m
2026-05-02 SDM5964 HRG → KUF May 2, 06:20 UTCMay 3, 04:00 UTC21h 39m
2026-05-02 SDM5978 HRG → CEK May 2, 02:20 UTCMay 3, 02:15 UTC23h 55m
2026-04-29 SDM5956 SSH → SVO Apr 29, 08:40 UTCApr 29, 10:05 UTC1h 26m
2026-04-28 SDM5962 SSH → CEK Apr 28, 12:40 UTCApr 29, 06:29 UTC17h 50m
2026-04-28 SDM5962 SSH → CEK Apr 28, 00:20 UTCApr 28, 20:15 UTC19h 55m
2026-04-27 SDM5962 SSH → CEK Apr 27, 22:20 UTCApr 28, 20:15 UTC21h 55m
2026-04-27 SDM5968 SSH → KUF Apr 27, 21:50 UTCApr 28, 20:15 UTC22h 25m
2026-04-27 SDM5976 SSH → UFA Apr 27, 07:00 UTCApr 27, 19:20 UTC12h 20m
2026-04-26 SDM5970 SSH → PEE Apr 26, 11:40 UTCApr 27, 05:00 UTC17h 20m
2026-04-25 SDM5965 GOJ → SSH Apr 25, 14:20 UTCApr 26, 13:50 UTC23h 30m
2026-04-25 SDM5966 SSH → GOJ Apr 25, 13:20 UTCApr 26, 11:55 UTC22h 35m
2026-04-25 SDM5967 KUF → SSH Apr 25, 05:55 UTCApr 25, 14:35 UTC8h 40m
2026-04-23 SDM5961 CEK → SSH Apr 23, 20:20 UTCApr 24, 14:30 UTC18h 10m
2026-04-23 SDM5961 CEK → SSH Apr 23, 19:35 UTCApr 24, 14:30 UTC18h 55m
2026-04-23 SDM5969 PEE → SSH Apr 23, 14:50 UTCApr 23, 17:25 UTC2h 35m
2026-04-22 SDM5976 SSH → UFA Apr 22, 08:20 UTCApr 23, 04:05 UTC19h 45m
2026-04-22 SDM5976 SSH → UFA Apr 22, 07:05 UTCApr 23, 04:05 UTC21h 0m
2026-04-21 SDM5976 SSH → UFA Apr 21, 20:40 UTCApr 22, 15:30 UTC18h 50m

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

Mode-S 151DF9 frequently asked

What is Mode-S code 151DF9?
151DF9 is an ICAO 24-bit transponder address. Allocated to Russia. Assigned to RA-73209.
Where is Mode-S 151DF9 registered?
Mode-S code 151DF9 is allocated to Russia (RU). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 151DF9 broadcasting right now?
No active broadcast right now. Last signal was 15h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 151DF9, octal 05216771, decimal 1,383,929.
What flights does 151DF9 operate?
Mode-S 151DF9 has broadcast 20 distinct callsigns, including SDM5954, SDM5978, SDM5976, SDM5964, SDM5980.