sensors Mode-S transponder

151E0B

ICAO 24-bit transponder address · allocated to Russia

Currently assigned to RA-73227 · BOEING 737-800

Hex
151E0B
Octal
05217013
Decimal
1,383,947
Country
RU
Tail
RA-73227
Type
B738
No current signal · last broadcast 1d ago
Flights observed
57
Distinct callsigns
20
Country
RU
Last broadcast
1d ago

Last known position

Most recent position reported by Mode-S 151E0B.

Country allocation

The ICAO 24-bit address 151E0B 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
PBD535 Pobeda 4 2026-05-15
PBD894 - 3 2026-05-20
PBD6845 - 3 2026-05-31
PBD587 Pobeda 3 2026-05-24
PBD6961 - 2 2026-05-29
PBD6582 - 2 2026-05-31
PBD588 Pobeda 2 2026-05-24
PBD565 - 2 2026-05-22
PBD536 Pobeda 2 2026-04-26
PBD529 Pobeda 2 2026-05-12
PBD506 - 2 2026-05-15
PBD6967 - 1 2026-06-01
PBD6963 - 1 2026-04-24
PBD6923 - 1 2026-04-14
PBD6912 - 1 2026-04-14
PBD6864 - 1 2026-06-01
PBD6863 - 1 2026-04-20
PBD6842 - 1 2026-05-26
PBD6841 - 1 2026-05-26
PBD6837 - 1 2026-05-30

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-06-01 PBD6967 - Jun 1, 16:35 UTCJun 1, 17:25 UTC50m
2026-06-01 PBD6864 GSV → GSV Jun 1, 13:40 UTCJun 1, 14:10 UTC30m
2026-06-01 PBD330 GSV → GSV Jun 1, 06:50 UTCJun 1, 06:55 UTC5m
2026-05-31 PBD6582 - May 31, 21:10 UTCMay 31, 21:25 UTC15m
2026-05-31 PBD6582 - May 31, 20:15 UTCMay 31, 20:30 UTC15m
2026-05-31 PBD6845 SVO → SVO May 31, 13:10 UTCMay 31, 13:30 UTC20m
2026-05-30 PBD6584 - May 30, 13:40 UTCMay 30, 13:50 UTC10m
2026-05-30 PBD6837 - May 30, 06:05 UTCMay 30, 07:20 UTC1h 15m
2026-05-29 PBD6961 SVO → SVO May 29, 04:20 UTCMay 29, 04:45 UTC25m
2026-05-26 PBD6842 - May 26, 13:29 UTCMay 26, 13:54 UTC25m
2026-05-26 PBD6841 SVO → SVO May 26, 10:29 UTCMay 26, 10:39 UTC10m
2026-05-26 PBD6961 SVO → SVO May 26, 04:10 UTCMay 26, 04:35 UTC25m
2026-05-24 PBD595 - May 24, 20:10 UTCMay 24, 20:30 UTC20m
2026-05-24 PBD588 KGD → LED May 24, 18:45 UTCMay 24, 18:55 UTC10m
2026-05-24 PBD587 LED → KGD May 24, 15:00 UTCMay 24, 16:20 UTC1h 20m
2026-05-23 PBD338 - May 23, 13:25 UTCMay 23, 13:45 UTC20m
2026-05-22 PBD565 LED → LED May 22, 11:45 UTCMay 22, 12:15 UTC30m
2026-05-22 PBD1569 - May 22, 05:45 UTCMay 22, 06:05 UTC20m
2026-05-22 PBD516 - May 22, 02:30 UTCMay 22, 03:00 UTC30m
2026-05-21 PBD515 - May 21, 12:50 UTCMay 22, 00:25 UTC11h 35m
2026-05-20 PBD894 - May 20, 18:50 UTCMay 20, 19:55 UTC1h 5m
2026-05-19 PBD436 SVO → VKO May 19, 02:20 UTCMay 19, 02:55 UTC35m
2026-05-16 PBD588 KGD → LED May 16, 16:20 UTCMay 16, 17:25 UTC1h 5m
2026-05-16 PBD587 LED → KGD May 16, 14:11 UTCMay 16, 15:01 UTC50m
2026-05-15 PBD535 LED → KGD May 15, 20:20 UTCMay 15, 21:05 UTC45m
2026-05-15 PBD506 LED → LED May 15, 07:15 UTCMay 15, 08:20 UTC1h 5m
2026-05-12 PBD529 LED → KGD May 12, 06:00 UTCMay 12, 07:15 UTC1h 15m
2026-05-11 PBD578 GSV → GSV May 11, 18:15 UTCMay 11, 18:25 UTC10m
2026-05-08 PBD565 LED → LED May 8, 09:44 UTCMay 8, 10:04 UTC20m
2026-05-07 PBD619 LED → LED May 7, 14:55 UTCMay 7, 15:15 UTC20m
2026-05-06 PBD592 - May 6, 17:55 UTCMay 7, 02:35 UTC8h 40m
2026-05-05 PBD617 LED → LED May 5, 11:00 UTCMay 5, 11:30 UTC30m
2026-05-04 PBD535 LED → KGD May 4, 16:05 UTCMay 4, 17:30 UTC1h 25m
2026-05-04 PBD506 LED → LED May 4, 07:50 UTCMay 4, 08:25 UTC35m
2026-05-03 PBD587 LED → KGD May 3, 17:35 UTCMay 3, 18:20 UTC45m
2026-04-30 PBD332 - Apr 30, 08:35 UTCApr 30, 17:00 UTC8h 25m
2026-04-27 PBD530 KGD → LED Apr 27, 10:20 UTCApr 27, 11:40 UTC1h 20m
2026-04-26 PBD529 LED → KGD Apr 26, 23:45 UTCApr 27, 08:50 UTC9h 5m
2026-04-26 PBD536 KGD → LED Apr 26, 19:20 UTCApr 26, 20:45 UTC1h 25m
2026-04-26 PBD535 LED → KGD Apr 26, 17:05 UTCApr 26, 18:00 UTC55m
2026-04-26 PBD505 - Apr 26, 15:00 UTCApr 26, 15:10 UTC10m
2026-04-24 PBD6963 SVO → SVO Apr 24, 16:30 UTCApr 24, 16:55 UTC25m
2026-04-23 PBD6834 - Apr 23, 17:00 UTCApr 23, 19:05 UTC2h 4m
2026-04-23 PBD6833 SVO → SVO Apr 23, 13:55 UTCApr 23, 15:55 UTC2h 0m
2026-04-22 PBD509 LED → LED Apr 22, 08:10 UTCApr 22, 09:10 UTC1h 0m
2026-04-20 PBD6863 SVO → SVO Apr 20, 04:30 UTCApr 20, 04:55 UTC25m
2026-04-19 PBD6821 SVO → SVO Apr 19, 06:00 UTCApr 19, 07:00 UTC1h 0m
2026-04-17 PBD894 - Apr 17, 17:25 UTCApr 17, 18:10 UTC45m
2026-04-17 PBD894 - Apr 17, 17:05 UTCApr 17, 17:15 UTC10m
2026-04-16 PBD536 - Apr 16, 19:55 UTCApr 16, 21:10 UTC1h 15m

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

Mode-S 151E0B frequently asked

What is Mode-S code 151E0B?
151E0B is an ICAO 24-bit transponder address. Allocated to Russia. Assigned to RA-73227.
Where is Mode-S 151E0B registered?
Mode-S code 151E0B is allocated to Russia (RU). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 151E0B broadcasting right now?
No active broadcast right now. Last signal was 1d ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 151E0B, octal 05217013, decimal 1,383,947.
What flights does 151E0B operate?
Mode-S 151E0B has broadcast 20 distinct callsigns, including PBD535, PBD894, PBD6845, PBD587, PBD6961.