sensors Mode-S transponder

151F0D

ICAO 24-bit transponder address · allocated to Russia

Currently assigned to RA-73485 · BOEING 737-900

Hex
151F0D
Octal
05217415
Decimal
1,384,205
Country
RU
Tail
RA-73485
Type
B739
No current signal · last broadcast 9h ago
Flights observed
114
Distinct callsigns
12
Country
RU
Last broadcast
9h ago

Last known position

Most recent position reported by Mode-S 151F0D.

Country allocation

The ICAO 24-bit address 151F0D 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 12 distinct

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-05-29 SDM6312 KGD → SVO May 29, 19:00 UTCMay 29, 20:35 UTC1h 35m
2026-05-29 SDM6311 SVO → KGD May 29, 15:30 UTCMay 29, 17:25 UTC1h 55m
2026-05-29 SDM6314 KGD → SVO May 29, 12:00 UTCMay 29, 13:40 UTC1h 40m
2026-05-29 SDM6313 SVO → KGD May 29, 08:55 UTCMay 29, 09:40 UTC45m
2026-05-29 SDM6313 SVO → KGD May 29, 07:45 UTCMay 29, 08:05 UTC20m
2026-05-28 SDM6365 SVO → TJM May 28, 22:20 UTCMay 29, 02:25 UTC4h 5m
2026-05-28 SDM6365 SVO → TJM May 28, 21:00 UTCMay 28, 21:40 UTC40m
2026-05-28 SDM6662 KGD → SVO May 28, 17:35 UTCMay 28, 18:45 UTC1h 10m
2026-05-28 SDM6310 KGD → SVO May 28, 09:15 UTCMay 28, 15:40 UTC6h 25m
2026-05-28 SDM6309 SVO → KGD May 28, 06:50 UTCMay 28, 07:25 UTC35m
2026-05-27 SDM6662 KGD → SVO May 27, 17:35 UTCMay 27, 22:40 UTC5h 5m
2026-05-26 SDM6661 SVO → KGD May 26, 22:05 UTCMay 27, 15:30 UTC17h 26m
2026-05-26 SDM6314 KGD → SVO May 26, 12:05 UTCMay 27, 02:14 UTC14h 10m
2026-05-25 SDM6313 SVO → KGD May 25, 21:49 UTCMay 26, 10:10 UTC12h 20m
2026-05-25 SDM6661 SVO → KGD May 25, 13:35 UTCMay 25, 16:00 UTC2h 25m
2026-05-25 SDM6310 KGD → SVO May 25, 09:50 UTCMay 25, 11:25 UTC1h 35m
2026-05-25 SDM6309 SVO → KGD May 25, 02:10 UTCMay 25, 07:45 UTC5h 35m
2026-05-24 SDM6662 KGD → SVO May 24, 17:45 UTCMay 24, 19:40 UTC1h 55m
2026-05-24 SDM6661 SVO → KGD May 24, 13:30 UTCMay 24, 15:35 UTC2h 5m
2026-05-24 SDM6310 KGD → SVO May 24, 10:05 UTCMay 24, 11:40 UTC1h 35m
2026-05-24 SDM6309 SVO → KGD May 24, 07:05 UTCMay 24, 07:45 UTC40m
2026-05-23 SDM6312 KGD → SVO May 23, 19:30 UTCMay 23, 21:00 UTC1h 30m
2026-05-23 SDM6311 SVO → KGD May 23, 15:20 UTCMay 23, 17:25 UTC2h 5m
2026-05-23 SDM6314 KGD → SVO May 23, 11:30 UTCMay 23, 13:45 UTC2h 15m
2026-05-22 SDM6313 SVO → KGD May 22, 22:05 UTCMay 23, 10:05 UTC11h 59m
2026-05-22 SDM6520 LED → SVO May 22, 18:05 UTCMay 22, 18:35 UTC30m
2026-05-21 SDM6314 KGD → SVO May 21, 11:45 UTCMay 21, 22:55 UTC11h 10m
2026-05-21 SDM6313 SVO → KGD May 21, 09:15 UTCMay 21, 09:55 UTC40m
2026-05-20 SDM6313 SVO → KGD May 20, 13:20 UTCMay 21, 09:55 UTC20h 35m
2026-05-20 SDM6314 KGD → SVO May 20, 12:10 UTCMay 21, 09:55 UTC21h 45m
2026-05-20 SDM6313 SVO → KGD May 20, 09:30 UTCMay 20, 10:10 UTC40m
2026-05-19 SDM6310 KGD → SVO May 19, 09:30 UTCMay 19, 15:55 UTC6h 25m
2026-05-19 SDM6309 SVO → KGD May 19, 07:15 UTCMay 19, 07:45 UTC30m
2026-05-17 SDM6662 KGD → SVO May 17, 17:40 UTCMay 17, 20:20 UTC2h 40m
2026-05-17 SDM6661 SVO → KGD May 17, 15:01 UTCMay 17, 15:45 UTC45m
2026-05-15 SDM6662 KGD → SVO May 15, 19:05 UTCMay 15, 20:10 UTC1h 5m
2026-05-15 SDM6310 KGD → SVO May 15, 10:00 UTCMay 15, 16:55 UTC6h 54m
2026-05-14 SDM6662 KGD → SVO May 14, 17:50 UTCMay 15, 07:50 UTC14h 0m
2026-05-14 SDM6310 KGD → SVO May 14, 09:50 UTCMay 14, 15:45 UTC5h 55m
2026-05-13 SDM6662 KGD → SVO May 13, 21:30 UTCMay 14, 07:35 UTC10h 5m
2026-05-13 SDM6310 KGD → SVO May 13, 13:45 UTCMay 13, 19:50 UTC6h 5m
2026-05-12 SDM6662 KGD → SVO May 12, 17:35 UTCMay 13, 07:45 UTC14h 10m
2026-05-12 SDM6310 KGD → SVO May 12, 09:40 UTCMay 12, 15:50 UTC6h 10m
2026-05-12 SDM6309 SVO → KGD May 12, 06:55 UTCMay 12, 07:30 UTC35m
2026-05-11 SDM6314 KGD → SVO May 11, 01:25 UTCMay 11, 17:45 UTC16h 21m
2026-05-10 SDM6310 KGD → SVO May 10, 09:35 UTCMay 10, 15:45 UTC6h 10m
2026-05-10 SDM6309 SVO → KGD May 10, 07:04 UTCMay 10, 07:45 UTC40m
2026-05-09 SDM6661 SVO → KGD May 9, 14:20 UTCMay 9, 15:35 UTC1h 15m
2026-05-09 SDM6309 SVO → KGD May 9, 05:30 UTCMay 9, 07:45 UTC2h 15m
2026-05-08 SDM6312 KGD → SVO May 8, 19:35 UTCMay 8, 20:40 UTC1h 5m

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

Mode-S 151F0D frequently asked

What is Mode-S code 151F0D?
151F0D is an ICAO 24-bit transponder address. Allocated to Russia. Assigned to RA-73485.
Where is Mode-S 151F0D registered?
Mode-S code 151F0D is allocated to Russia (RU). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 151F0D broadcasting right now?
No active broadcast right now. Last signal was 9h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 151F0D, octal 05217415, decimal 1,384,205.
What flights does 151F0D operate?
Mode-S 151F0D has broadcast 12 distinct callsigns, including SDM6310, SDM6309, SDM6314, SDM6312, SDM6313.