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 3d ago
Flights observed
123
Distinct callsigns
20
Country
RU
Last broadcast
3d 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
PBD530 - 12 2026-06-24
PBD529 - 12 2026-06-29
PBD6837 - 6 2026-07-03
PBD535 - 5 2026-07-07
PBD6548 - 4 2026-07-05
PBD587 Pobeda 4 2026-06-20
PBD525 - 4 2026-06-07
PBD893 - 3 2026-07-10
PBD6838 - 3 2026-07-03
PBD6835 - 3 2026-07-06
PBD577 - 3 2026-06-02
PBD1569 - 3 2026-07-07
PBD894 - 2 2026-06-14
PBD594 - 2 2026-07-07
PBD588 Pobeda 2 2026-06-20
PBD571 - 2 2026-07-08
PBD559 - 2 2026-06-09
PBD509 - 2 2026-05-24
PBD506 - 2 2026-06-04
PBD261 - 2 2026-07-09

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-11 PBD208 - Jul 11, 01:55 UTCJul 11, 02:10 UTC15m
2026-07-10 PBD893 - Jul 10, 15:45 UTCJul 10, 16:50 UTC1h 5m
2026-07-09 PBD261 - Jul 9, 05:40 UTCJul 9, 06:15 UTC35m
2026-07-08 PBD515 - Jul 8, 21:05 UTCJul 8, 21:15 UTC10m
2026-07-08 PBD571 - Jul 8, 15:00 UTCJul 8, 15:20 UTC20m
2026-07-07 PBD1569 - Jul 7, 23:40 UTCJul 7, 23:50 UTC10m
2026-07-07 PBD535 - Jul 7, 18:35 UTCJul 7, 19:50 UTC1h 15m
2026-07-07 PBD594 GSV → GSV Jul 7, 15:30 UTCJul 7, 15:40 UTC10m
2026-07-06 PBD6835 - Jul 6, 13:40 UTCJul 6, 14:20 UTC40m
2026-07-05 PBD6824 - Jul 5, 08:35 UTCJul 5, 08:55 UTC20m
2026-07-05 PBD6548 - Jul 5, 01:25 UTCJul 5, 02:05 UTC40m
2026-07-03 PBD6838 - Jul 3, 09:40 UTCJul 3, 10:50 UTC1h 10m
2026-07-03 PBD6837 - Jul 3, 07:25 UTCJul 3, 07:45 UTC20m
2026-07-03 PBD6837 - Jul 3, 06:10 UTCJul 3, 06:20 UTC10m
2026-06-29 PBD529 - Jun 29, 06:40 UTCJun 29, 07:20 UTC40m
2026-06-28 PBD6831 - Jun 28, 17:34 UTCJun 28, 18:05 UTC30m
2026-06-26 PBD261 VKO → KGD Jun 26, 11:30 UTCJun 26, 12:05 UTC35m
2026-06-24 PBD530 - Jun 24, 08:39 UTCJun 24, 09:59 UTC1h 20m
2026-06-24 PBD529 - Jun 24, 06:50 UTCJun 24, 07:24 UTC35m
2026-06-22 PBD589 - Jun 22, 20:14 UTCJun 22, 21:00 UTC45m
2026-06-21 PBD519 - Jun 21, 13:24 UTCJun 21, 13:44 UTC20m
2026-06-20 PBD588 KGD → LED Jun 20, 17:34 UTCJun 20, 18:29 UTC55m
2026-06-20 PBD587 LED → KGD Jun 20, 14:50 UTCJun 20, 16:00 UTC1h 10m
2026-06-19 PBD530 - Jun 19, 08:59 UTCJun 19, 09:55 UTC55m
2026-06-19 PBD529 - Jun 19, 06:59 UTCJun 19, 07:34 UTC35m
2026-06-18 PBD414 - Jun 18, 17:50 UTCJun 18, 18:10 UTC20m
2026-06-16 PBD587 LED → KGD Jun 16, 14:55 UTCJun 16, 16:10 UTC1h 15m
2026-06-15 PBD6839 SVO → KGD Jun 15, 20:34 UTCJun 15, 21:14 UTC40m
2026-06-14 PBD894 - Jun 14, 17:55 UTCJun 14, 19:00 UTC1h 5m
2026-06-14 PBD530 - Jun 14, 08:40 UTCJun 14, 09:35 UTC55m
2026-06-14 PBD529 - Jun 14, 06:30 UTCJun 14, 07:05 UTC35m
2026-06-13 PBD160 KRR → VKO Jun 13, 12:45 UTCJun 13, 13:00 UTC15m
2026-06-13 PBD563 - Jun 13, 06:10 UTCJun 13, 07:15 UTC1h 5m
2026-06-11 PBD894 - Jun 11, 18:45 UTCJun 11, 19:45 UTC1h 0m
2026-06-11 PBD893 - Jun 11, 16:50 UTCJun 11, 17:45 UTC55m
2026-06-09 PBD559 - Jun 9, 20:30 UTCJun 9, 20:45 UTC15m
2026-06-09 PBD893 - Jun 9, 15:20 UTCJun 9, 15:50 UTC30m
2026-06-08 PBD1569 - Jun 8, 22:00 UTCJun 8, 22:15 UTC15m
2026-06-08 PBD535 LED → KGD Jun 8, 17:25 UTCJun 8, 18:30 UTC1h 5m
2026-06-08 PBD526 - Jun 8, 14:45 UTCJun 8, 14:55 UTC10m
2026-06-08 PBD530 KGD → LED Jun 8, 09:30 UTCJun 8, 09:40 UTC10m
2026-06-07 PBD525 - Jun 7, 11:20 UTCJun 7, 11:40 UTC20m
2026-06-07 PBD530 KGD → LED Jun 7, 09:50 UTCJun 7, 10:30 UTC40m
2026-06-07 PBD529 LED → KGD Jun 7, 07:10 UTCJun 7, 08:20 UTC1h 10m
2026-06-05 PBD206 SVO → VKO Jun 5, 15:55 UTCJun 5, 16:15 UTC20m
2026-06-05 PBD530 KGD → LED Jun 5, 09:00 UTCJun 5, 09:50 UTC50m
2026-06-05 PBD529 LED → KGD Jun 5, 06:45 UTCJun 5, 07:30 UTC45m
2026-06-04 PBD535 LED → KGD Jun 4, 18:10 UTCJun 4, 19:35 UTC1h 25m
2026-06-04 PBD565 LED → LED Jun 4, 13:00 UTCJun 4, 13:20 UTC20m
2026-06-04 PBD506 - Jun 4, 04:45 UTCJun 4, 05:00 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 3d 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 PBD530, PBD529, PBD6837, PBD535, PBD6548.