sensors Mode-S transponder

151E0F

ICAO 24-bit transponder address · allocated to Russia

Currently assigned to RA-73231 · BOEING 737-800

Hex
151E0F
Octal
05217017
Decimal
1,383,951
Country
RU
Tail
RA-73231
Type
B738
No current signal · last broadcast 1h ago
Flights observed
56
Distinct callsigns
20
Country
RU
Last broadcast
1h ago

Last known position

Most recent position reported by Mode-S 151E0F.

Country allocation

The ICAO 24-bit address 151E0F 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

Callsign Airline Flights Last seen
PBD560 - 5 2026-05-19
PBD6837 - 3 2026-05-29
PBD340 - 3 2026-05-14
PBD968 - 2 2026-05-08
PBD6965 - 2 2026-05-21
PBD6862 - 2 2026-04-15
PBD6838 Pobeda 2 2026-05-29
PBD6824 - 2 2026-05-08
PBD5548 - 2 2026-05-18
PBD516 - 2 2026-05-15
PBD894 - 1 2026-04-29
PBD6927 - 1 2026-04-22
PBD6925 - 1 2026-05-25
PBD6901 - 1 2026-05-28
PBD6863 - 1 2026-04-27
PBD6861 - 1 2026-04-15
PBD6845 - 1 2026-04-25
PBD6840 Pobeda 1 2026-04-25
PBD6836 Pobeda 1 2026-04-23
PBD6834 - 1 2026-04-13

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-05-29 PBD6838 KGD → SVO May 29, 08:10 UTCMay 29, 23:40 UTC15h 31m
2026-05-29 PBD6837 - May 29, 05:35 UTCMay 29, 06:35 UTC1h 0m
2026-05-28 PBD6901 SVO → SVO May 28, 05:30 UTCMay 28, 06:00 UTC30m
2026-05-25 PBD6925 SVO → SVO May 25, 16:00 UTCMay 25, 16:25 UTC25m
2026-05-24 PBD338 - May 24, 02:05 UTCMay 24, 11:50 UTC9h 45m
2026-05-21 PBD6965 SVO → SVO May 21, 04:55 UTCMay 21, 05:30 UTC35m
2026-05-19 PBD560 - May 19, 01:20 UTCMay 19, 19:25 UTC18h 5m
2026-05-18 PBD560 - May 18, 22:40 UTCMay 19, 19:25 UTC20h 45m
2026-05-18 PBD5548 - May 18, 02:10 UTCMay 19, 01:45 UTC23h 34m
2026-05-17 PBD5548 - May 17, 23:55 UTCMay 18, 22:45 UTC22h 49m
2026-05-17 PBD5547 - May 17, 21:40 UTCMay 18, 02:45 UTC5h 5m
2026-05-17 PBD6502 - May 17, 08:00 UTCMay 17, 08:25 UTC25m
2026-05-16 PBD517 LED → LED May 16, 13:41 UTCMay 16, 14:05 UTC25m
2026-05-16 PBD560 - May 16, 00:55 UTCMay 16, 01:35 UTC40m
2026-05-15 PBD560 - May 15, 01:50 UTCMay 16, 01:35 UTC23h 44m
2026-05-15 PBD516 - May 15, 01:30 UTCMay 15, 01:55 UTC25m
2026-05-14 PBD516 - May 14, 03:50 UTCMay 15, 01:55 UTC22h 5m
2026-05-14 PBD340 - May 14, 02:55 UTCMay 15, 01:45 UTC22h 50m
2026-05-13 PBD340 - May 13, 11:35 UTCMay 14, 03:55 UTC16h 20m
2026-05-10 PBD6570 - May 10, 01:39 UTCMay 10, 02:14 UTC35m
2026-05-08 PBD6824 LED → LED May 8, 12:14 UTCMay 8, 12:49 UTC35m
2026-05-08 PBD968 - May 8, 03:30 UTCMay 8, 03:55 UTC25m
2026-05-06 PBD968 - May 6, 21:30 UTCMay 6, 22:05 UTC35m
2026-05-06 PBD617 LED → LED May 6, 14:20 UTCMay 6, 15:25 UTC1h 5m
2026-05-06 PBD560 - May 6, 02:10 UTCMay 6, 02:40 UTC30m
2026-05-03 PBD538 STW → STW May 3, 15:55 UTCMay 3, 16:05 UTC10m
2026-05-03 PBD537 LED → LED May 3, 11:35 UTCMay 3, 11:55 UTC20m
2026-05-01 PBD578 GSV → GSV May 1, 19:35 UTCMay 1, 20:05 UTC30m
2026-05-01 PBD577 - May 1, 16:40 UTCMay 1, 17:15 UTC35m
2026-05-01 PBD519 LED → LED May 1, 07:10 UTCMay 1, 07:40 UTC30m
2026-04-30 PBD6824 LED → LED Apr 30, 15:15 UTCApr 30, 16:30 UTC1h 15m
2026-04-29 PBD894 - Apr 29, 17:05 UTCApr 29, 18:10 UTC1h 5m
2026-04-27 PBD340 - Apr 27, 16:15 UTCApr 27, 17:20 UTC1h 5m
2026-04-27 PBD6863 SVO → SVO Apr 27, 04:45 UTCApr 27, 05:10 UTC25m
2026-04-26 PBD6965 SVO → SVO Apr 26, 05:10 UTCApr 26, 05:30 UTC20m
2026-04-25 PBD6845 SVO → SVO Apr 25, 15:40 UTCApr 25, 16:05 UTC25m
2026-04-25 PBD6840 KGD → SVO Apr 25, 07:50 UTCApr 25, 09:40 UTC1h 50m
2026-04-25 PBD6837 - Apr 25, 04:30 UTCApr 25, 06:35 UTC2h 5m
2026-04-24 PBD509 LED → LED Apr 24, 08:00 UTCApr 24, 09:00 UTC1h 0m
2026-04-24 PBD6821 SVO → SVO Apr 24, 06:10 UTCApr 24, 07:05 UTC55m
2026-04-23 PBD6569 SVO → SVO Apr 23, 21:05 UTCApr 23, 21:25 UTC20m
2026-04-23 PBD6816 SVO → SVO Apr 23, 19:50 UTCApr 23, 20:10 UTC20m
2026-04-23 PBD6836 KGD → SVO Apr 23, 13:55 UTCApr 23, 16:10 UTC2h 15m
2026-04-23 PBD6838 KGD → SVO Apr 23, 07:45 UTCApr 23, 13:00 UTC5h 15m
2026-04-23 PBD6837 SVO → SVO Apr 23, 04:40 UTCApr 23, 05:00 UTC20m
2026-04-22 PBD6927 SVO → SVO Apr 22, 06:25 UTCApr 22, 06:50 UTC25m
2026-04-16 PBD6561 SVO → SVO Apr 16, 21:14 UTCApr 16, 21:39 UTC25m
2026-04-16 PBD6808 - Apr 16, 07:54 UTCApr 16, 08:24 UTC30m
2026-04-16 PBD6807 SVO → SVO Apr 16, 05:34 UTCApr 16, 05:49 UTC15m
2026-04-15 PBD6582 SVO → SVO Apr 15, 21:25 UTCApr 15, 21: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-73231 page for operator, model, and routing details .

Mode-S 151E0F frequently asked

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