sensors Mode-S transponder

151E09

ICAO 24-bit transponder address · allocated to Russia

Currently assigned to RA-73225 · BOEING 737-800

Hex
151E09
Octal
05217011
Decimal
1,383,945
Country
RU
Tail
RA-73225
Type
B738
No current signal · last broadcast 1d ago
Flights observed
51
Distinct callsigns
20
Country
RU
Last broadcast
1d ago

Last known position

Most recent position reported by Mode-S 151E09.

Country allocation

The ICAO 24-bit address 151E09 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
PBD6817 - 4 2026-05-28
PBD6961 - 2 2026-05-28
PBD6835 Pobeda 2 2026-05-11
PBD6547 - 2 2026-04-17
PBD6502 - 2 2026-05-10
PBD538 - 2 2026-05-13
PBD530 Pobeda 2 2026-05-08
PBD6963 - 1 2026-05-11
PBD6942 - 1 2026-04-14
PBD6927 - 1 2026-04-15
PBD6923 - 1 2026-04-28
PBD6921 - 1 2026-05-15
PBD6913 - 1 2026-04-21
PBD6903 - 1 2026-04-27
PBD6862 - 1 2026-05-20
PBD6855 - 1 2026-04-28
PBD6846 - 1 2026-05-24
PBD6845 - 1 2026-05-24
PBD6844 - 1 2026-04-18
PBD6843 - 1 2026-04-17

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-05-28 PBD6513 - May 28, 23:25 UTCMay 28, 23:40 UTC15m
2026-05-28 PBD6818 - May 28, 12:45 UTCMay 28, 13:00 UTC15m
2026-05-28 PBD6817 - May 28, 10:20 UTCMay 28, 10:55 UTC35m
2026-05-28 PBD6961 - May 28, 04:15 UTCMay 28, 04:35 UTC20m
2026-05-26 PBD6525 - May 26, 22:29 UTCMay 27, 04:55 UTC6h 25m
2026-05-26 PBD509 LED → LED May 26, 08:19 UTCMay 26, 09:25 UTC1h 5m
2026-05-26 PBD6526 - May 26, 00:14 UTCMay 26, 04:30 UTC4h 15m
2026-05-24 PBD6846 - May 24, 15:15 UTCMay 24, 15:35 UTC20m
2026-05-24 PBD6845 SVO → SVO May 24, 13:05 UTCMay 24, 13:25 UTC20m
2026-05-24 PBD6817 SVO → SVO May 24, 09:25 UTCMay 24, 09:50 UTC25m
2026-05-23 PBD330 GSV → GSV May 23, 06:45 UTCMay 23, 06:50 UTC5m
2026-05-20 PBD6862 GSV → GSV May 20, 12:25 UTCMay 20, 12:45 UTC20m
2026-05-15 PBD6921 SVO → SVO May 15, 07:10 UTCMay 15, 07:40 UTC30m
2026-05-13 PBD538 - May 13, 14:51 UTCMay 13, 15:00 UTC10m
2026-05-13 PBD538 STW → STW May 13, 11:20 UTCMay 13, 11:25 UTC5m
2026-05-13 PBD516 - May 13, 01:35 UTCMay 13, 02:50 UTC1h 15m
2026-05-12 PBD593 LED → LED May 12, 09:00 UTCMay 12, 10:05 UTC1h 5m
2026-05-11 PBD6963 - May 11, 18:50 UTCMay 11, 19:00 UTC10m
2026-05-11 PBD6835 SVO → KGD May 11, 12:35 UTCMay 11, 13:20 UTC45m
2026-05-11 PBD6835 SVO → KGD May 11, 11:05 UTCMay 11, 11:25 UTC20m
2026-05-10 PBD6502 - May 10, 02:55 UTCMay 10, 03:14 UTC20m
2026-05-08 PBD530 KGD → LED May 8, 10:19 UTCMay 8, 11:25 UTC1h 5m
2026-05-07 PBD530 KGD → LED May 7, 15:45 UTCMay 8, 11:25 UTC19h 39m
2026-05-06 PBD365 - May 6, 22:30 UTCMay 7, 15:55 UTC17h 25m
2026-05-06 PBD332 - May 6, 16:30 UTCMay 7, 15:55 UTC23h 25m
2026-05-04 PBD519 LED → LED May 4, 07:25 UTCMay 4, 08:30 UTC1h 5m
2026-05-02 PBD424 - May 2, 16:45 UTCMay 2, 17:20 UTC35m
2026-05-02 PBD434 - May 2, 02:25 UTCMay 2, 03:00 UTC35m
2026-05-01 PBD588 KGD → LED May 1, 10:15 UTCMay 1, 11:35 UTC1h 20m
2026-05-01 PBD587 LED → KGD May 1, 07:40 UTCMay 1, 08:55 UTC1h 15m
2026-04-30 PBD6581 SVO → SVO Apr 30, 17:35 UTCApr 30, 17:50 UTC15m
2026-04-28 PBD6923 SVO → SVO Apr 28, 21:00 UTCApr 28, 21:30 UTC30m
2026-04-28 PBD6855 SVO → SVO Apr 28, 04:00 UTCApr 28, 04:20 UTC20m
2026-04-27 PBD6903 SVO → SVO Apr 27, 08:15 UTCApr 27, 08:40 UTC25m
2026-04-26 PBD6961 SVO → SVO Apr 26, 04:15 UTCApr 26, 04:45 UTC30m
2026-04-25 PBD6832 KGD → SVO Apr 25, 14:00 UTCApr 25, 15:45 UTC1h 45m
2026-04-25 PBD612 - Apr 25, 11:50 UTCApr 25, 12:35 UTC45m
2026-04-22 PBD6831 SVO → KGD Apr 22, 06:35 UTCApr 22, 07:20 UTC45m
2026-04-21 PBD6913 SVO → SVO Apr 21, 09:05 UTCApr 21, 09:30 UTC25m
2026-04-21 PBD6502 - Apr 21, 02:25 UTCApr 21, 02:50 UTC25m
2026-04-19 PBD6817 SVO → SVO Apr 19, 09:30 UTCApr 19, 09:50 UTC20m
2026-04-19 PBD6842 - Apr 19, 07:50 UTCApr 19, 08:15 UTC25m
2026-04-19 PBD6841 SVO → SVO Apr 19, 05:00 UTCApr 19, 05:15 UTC15m
2026-04-18 PBD6844 SVO → SVO Apr 18, 23:55 UTCApr 19, 00:05 UTC10m
2026-04-17 PBD6843 SVO → SVO Apr 17, 07:55 UTCApr 17, 08:05 UTC10m
2026-04-17 PBD6548 - Apr 17, 02:15 UTCApr 17, 02:55 UTC40m
2026-04-17 PBD6547 - Apr 17, 00:05 UTCApr 17, 00:35 UTC30m
2026-04-15 PBD6927 SVO → SVO Apr 15, 06:20 UTCApr 15, 06:55 UTC35m
2026-04-14 PBD6942 SVO → SVO Apr 14, 21:15 UTCApr 14, 21:25 UTC10m
2026-04-14 PBD6817 SVO → SVO Apr 14, 09:25 UTCApr 14, 09:40 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-73225 page for operator, model, and routing details .

Mode-S 151E09 frequently asked

What is Mode-S code 151E09?
151E09 is an ICAO 24-bit transponder address. Allocated to Russia. Assigned to RA-73225.
Where is Mode-S 151E09 registered?
Mode-S code 151E09 is allocated to Russia (RU). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 151E09 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 151E09, octal 05217011, decimal 1,383,945.
What flights does 151E09 operate?
Mode-S 151E09 has broadcast 20 distinct callsigns, including PBD6817, PBD6961, PBD6835, PBD6547, PBD6502.