sensors Mode-S transponder

151DB2

ICAO 24-bit transponder address · allocated to Russia

Currently assigned to RA-73138 · BOEING 777-300ER

Hex
151DB2
Octal
05216662
Decimal
1,383,858
Country
RU
Tail
RA-73138
Type
B77W
No current signal · last broadcast 4h ago
Flights observed
80
Distinct callsigns
20
Country
RU
Last broadcast
4h ago

Last known position

Most recent position reported by Mode-S 151DB2.

Country allocation

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

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-05-29 AFL209 PVG → SVO May 29, 20:15 UTCMay 30, 12:50 UTC16h 35m
2026-05-27 AFL1735 PKC → SVO May 27, 19:10 UTCMay 28, 11:10 UTC16h 0m
2026-05-25 AFL209 PVG → SVO May 25, 18:35 UTCMay 26, 13:04 UTC18h 29m
2026-05-25 AFL209 PVG → SVO May 25, 18:15 UTCMay 26, 13:04 UTC18h 50m
2026-05-23 AFL1731 PKC → SVO May 23, 15:15 UTCMay 24, 09:15 UTC18h 0m
2026-05-23 AFL1730 SVO → PKC May 23, 13:55 UTCMay 23, 14:10 UTC15m
2026-05-23 AFL1731 PKC → SVO May 23, 06:40 UTCMay 23, 08:10 UTC1h 30m
2026-05-21 AFL1731 PKC → SVO May 21, 15:25 UTCMay 22, 08:20 UTC16h 55m
2026-05-17 AFL209 PVG → SVO May 17, 20:55 UTCMay 18, 11:55 UTC15h 0m
2026-05-15 AFL1723 KHV → SVO May 15, 04:45 UTCMay 15, 06:00 UTC1h 15m
2026-05-14 AFL233 DEL → SVO May 14, 02:35 UTCMay 14, 07:15 UTC4h 40m
2026-05-13 AFL221 CAN → SVO May 13, 08:55 UTCMay 14, 00:05 UTC15h 10m
2026-05-12 AFL221 CAN → SVO May 12, 19:45 UTCMay 13, 12:15 UTC16h 30m
2026-05-12 AFL221 CAN → SVO May 12, 08:35 UTCMay 12, 20:20 UTC11h 45m
2026-05-11 AFL220 SVO → CAN May 11, 17:30 UTCMay 12, 09:25 UTC15h 55m
2026-05-11 AFL220 SVO → CAN May 11, 11:55 UTCMay 12, 09:25 UTC21h 31m
2026-05-11 AFL209 PVG → SVO May 11, 09:15 UTCMay 11, 20:15 UTC11h 1m
2026-05-10 AFL209 PVG → SVO May 10, 20:35 UTCMay 11, 20:15 UTC23h 41m
2026-05-10 AFL209 PVG → SVO May 10, 20:14 UTCMay 11, 18:00 UTC21h 46m
2026-05-10 AFL209 PVG → SVO May 10, 18:09 UTCMay 11, 12:30 UTC18h 20m
2026-05-10 AFL205 PKX → SVO May 10, 07:19 UTCMay 10, 11:35 UTC4h 15m
2026-05-10 AFL204 SVO → PKX May 10, 00:34 UTCMay 10, 00:45 UTC10m
2026-05-09 AFL209 PVG → SVO May 9, 08:50 UTCMay 9, 22:00 UTC13h 10m
2026-05-08 AFL209 PVG → SVO May 8, 20:35 UTCMay 9, 19:40 UTC23h 5m
2026-05-08 AFL209 PVG → SVO May 8, 20:15 UTCMay 9, 13:15 UTC17h 0m
2026-05-08 AFL205 PKX → SVO May 8, 04:04 UTCMay 8, 21:00 UTC16h 55m
2026-05-08 AFL204 SVO → PKX May 8, 00:44 UTCMay 8, 00:54 UTC10m
2026-05-07 AFL221 CAN → SVO May 7, 09:05 UTCMay 7, 22:10 UTC13h 5m
2026-05-06 AFL220 SVO → CAN May 6, 16:50 UTCMay 7, 09:55 UTC17h 5m
2026-05-04 AFL221 CAN → SVO May 4, 19:35 UTCMay 5, 11:15 UTC15h 40m
2026-05-03 AFL220 SVO → CAN May 3, 17:45 UTCMay 4, 09:35 UTC15h 50m
2026-05-03 AFL220 SVO → CAN May 3, 10:40 UTCMay 4, 09:35 UTC22h 55m
2026-05-03 AFL205 PKX → SVO May 3, 04:35 UTCMay 3, 20:35 UTC16h 0m
2026-05-03 AFL204 SVO → PKX May 3, 00:35 UTCMay 3, 00:50 UTC15m
2026-05-02 AFL204 SVO → PKX May 2, 08:45 UTCMay 2, 22:10 UTC13h 25m
2026-05-01 AFL209 PVG → SVO May 1, 20:35 UTCMay 2, 19:55 UTC23h 21m
2026-05-01 AFL209 PVG → SVO May 1, 20:25 UTCMay 2, 09:40 UTC13h 16m
2026-05-01 AFL209 PVG → SVO May 1, 13:30 UTCMay 2, 09:40 UTC20h 10m
2026-04-30 AFL209 PVG → SVO Apr 30, 20:35 UTCMay 1, 09:50 UTC13h 15m
2026-04-30 AFL1731 PKC → SVO Apr 30, 06:30 UTCApr 30, 21:10 UTC14h 40m
2026-04-29 AFL1731 PKC → SVO Apr 29, 15:20 UTCApr 30, 07:50 UTC16h 29m
2026-04-28 AFL1705 VVO → SVO Apr 28, 17:05 UTCApr 29, 10:55 UTC17h 50m
2026-04-27 AFL1715 KHV → SVO Apr 27, 20:20 UTCApr 28, 12:35 UTC16h 15m
2026-04-27 AFL321 MLE → SVO Apr 27, 15:35 UTCApr 27, 15:55 UTC20m
2026-04-27 AFL321 MLE → SVO Apr 27, 03:10 UTCApr 27, 14:40 UTC11h 30m
2026-04-26 AFL320 SVO → MLE Apr 26, 20:35 UTCApr 26, 20:50 UTC15m
2026-04-25 AFL225 SVO → ATH Apr 25, 14:40 UTCApr 26, 08:30 UTC17h 50m
2026-04-25 AFL1755 VVO → SVO Apr 25, 01:30 UTCApr 25, 15:00 UTC13h 30m
2026-04-24 AFL639 HKT → VVO Apr 24, 10:10 UTCApr 25, 02:45 UTC16h 35m
2026-04-24 AFL639 HKT → VVO Apr 24, 06:35 UTCApr 25, 02:45 UTC20h 10m

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

Mode-S 151DB2 frequently asked

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