sensors Mode-S transponder

151E4F

ICAO 24-bit transponder address · allocated to Russia

Currently assigned to RA-73295 · BOEING 737-800

Hex
151E4F
Octal
05217117
Decimal
1,384,015
Country
RU
Tail
RA-73295
Type
B738
No current signal · last broadcast 7h ago
Flights observed
62
Distinct callsigns
20
Country
RU
Last broadcast
7h ago

Last known position

Most recent position reported by Mode-S 151E4F.

Country allocation

The ICAO 24-bit address 151E4F 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
PBD6837 - 4 2026-05-09
PBD530 Pobeda 4 2026-04-29
PBD529 Pobeda 4 2026-04-29
PBD6548 - 3 2026-05-21
PBD6838 Pobeda 2 2026-05-09
PBD6835 Pobeda 2 2026-05-22
PBD587 Pobeda 2 2026-05-14
PBD577 - 2 2026-04-25
PBD535 Pobeda 2 2026-05-05
PBD509 - 2 2026-05-24
PBD6969 - 1 2026-04-14
PBD6919 - 1 2026-04-13
PBD6913 - 1 2026-04-15
PBD6903 - 1 2026-04-15
PBD6862 - 1 2026-05-03
PBD6859 - 1 2026-05-22
PBD6846 - 1 2026-04-27
PBD6845 - 1 2026-05-03
PBD6844 - 1 2026-04-22
PBD6843 - 1 2026-04-16

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-05-29 PBD366 - May 29, 01:10 UTCMay 29, 22:25 UTC21h 16m
2026-05-28 PBD365 - May 28, 22:15 UTCMay 29, 01:30 UTC3h 15m
2026-05-24 PBD6822 - May 24, 19:10 UTCMay 24, 19:45 UTC35m
2026-05-24 PBD509 - May 24, 08:35 UTCMay 24, 09:00 UTC25m
2026-05-22 PBD6859 - May 22, 21:15 UTCMay 22, 21:30 UTC15m
2026-05-22 PBD6835 SVO → KGD May 22, 00:15 UTCMay 22, 15:20 UTC15h 5m
2026-05-21 PBD6548 - May 21, 04:10 UTCMay 22, 00:20 UTC20h 10m
2026-05-21 PBD6548 - May 21, 01:50 UTCMay 22, 00:20 UTC22h 30m
2026-05-20 PBD6548 - May 20, 23:10 UTCMay 21, 04:40 UTC5h 30m
2026-05-18 PBD343 - May 18, 01:10 UTCMay 18, 08:25 UTC7h 15m
2026-05-15 PBD6835 SVO → KGD May 15, 12:50 UTCMay 15, 13:40 UTC50m
2026-05-14 PBD588 KGD → LED May 14, 16:15 UTCMay 14, 17:30 UTC1h 15m
2026-05-14 PBD587 LED → KGD May 14, 14:05 UTCMay 14, 15:01 UTC55m
2026-05-14 PBD594 GSV → GSV May 14, 10:50 UTCMay 14, 11:10 UTC20m
2026-05-13 PBD592 - May 13, 02:00 UTCMay 13, 02:40 UTC40m
2026-05-10 PBD587 LED → KGD May 10, 14:59 UTCMay 10, 16:30 UTC1h 30m
2026-05-09 PBD6838 KGD → SVO May 9, 08:55 UTCMay 9, 14:20 UTC5h 25m
2026-05-09 PBD6837 - May 9, 05:40 UTCMay 9, 06:55 UTC1h 15m
2026-05-05 PBD535 LED → KGD May 5, 21:35 UTCMay 5, 22:40 UTC1h 5m
2026-05-05 PBD506 LED → LED May 5, 12:25 UTCMay 5, 13:00 UTC35m
2026-05-05 PBD1569 - May 5, 06:05 UTCMay 5, 06:25 UTC20m
2026-05-04 PBD6838 KGD → SVO May 4, 08:15 UTCMay 4, 09:15 UTC1h 0m
2026-05-04 PBD6837 - May 4, 06:10 UTCMay 4, 06:45 UTC35m
2026-05-03 PBD6845 - May 3, 15:40 UTCMay 3, 16:00 UTC20m
2026-05-03 PBD6862 GSV → GSV May 3, 12:45 UTCMay 3, 13:20 UTC35m
2026-05-02 PBD6837 - May 2, 10:10 UTCMay 2, 10:45 UTC35m
2026-05-02 PBD6837 SVO → SVO May 2, 08:25 UTCMay 2, 08:35 UTC10m
2026-05-02 PBD6502 - May 2, 01:20 UTCMay 2, 01:50 UTC30m
2026-05-01 PBD617 - May 1, 14:10 UTCMay 1, 14:35 UTC25m
2026-05-01 PBD538 STW → STW May 1, 09:40 UTCMay 1, 09:45 UTC5m
2026-04-30 PBD591 - Apr 30, 21:35 UTCApr 30, 21:50 UTC15m
2026-04-29 PBD206 LED → LED Apr 29, 16:50 UTCApr 29, 17:55 UTC1h 5m
2026-04-29 PBD528 - Apr 29, 13:40 UTCApr 29, 14:00 UTC20m
2026-04-29 PBD527 LED → LED Apr 29, 10:50 UTCApr 29, 11:10 UTC20m
2026-04-29 PBD530 KGD → LED Apr 29, 08:45 UTCApr 29, 09:35 UTC51m
2026-04-29 PBD529 LED → KGD Apr 29, 06:45 UTCApr 29, 07:20 UTC35m
2026-04-28 PBD509 LED → LED Apr 28, 11:10 UTCApr 28, 12:15 UTC1h 5m
2026-04-28 PBD6823 SVO → LED Apr 28, 05:00 UTCApr 28, 06:00 UTC1h 0m
2026-04-27 PBD6846 - Apr 27, 19:55 UTCApr 27, 20:05 UTC10m
2026-04-27 PBD6828 LED → SVO Apr 27, 13:35 UTCApr 27, 14:45 UTC1h 10m
2026-04-26 PBD571 - Apr 26, 16:10 UTCApr 26, 16:20 UTC10m
2026-04-25 PBD577 LED → LED Apr 25, 16:35 UTCApr 25, 17:40 UTC1h 5m
2026-04-24 PBD525 - Apr 24, 10:35 UTCApr 24, 22:45 UTC12h 10m
2026-04-24 PBD530 KGD → LED Apr 24, 08:25 UTCApr 24, 09:50 UTC1h 25m
2026-04-24 PBD529 LED → KGD Apr 24, 01:40 UTCApr 24, 07:20 UTC5h 40m
2026-04-23 PBD535 LED → KGD Apr 23, 16:45 UTCApr 23, 18:00 UTC1h 14m
2026-04-23 PBD530 KGD → LED Apr 23, 08:20 UTCApr 23, 09:50 UTC1h 30m
2026-04-23 PBD529 LED → KGD Apr 23, 06:40 UTCApr 23, 07:15 UTC35m
2026-04-22 PBD6501 SVO → SVO Apr 22, 21:05 UTCApr 22, 21:30 UTC25m
2026-04-22 PBD6844 SVO → SVO Apr 22, 18:40 UTCApr 22, 18:55 UTC15m

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

Mode-S 151E4F frequently asked

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