sensors Mode-S transponder

151D6F

ICAO 24-bit transponder address · allocated to Russia

Currently assigned to RA-73071 · BOEING 757-200

Hex
151D6F
Octal
05216557
Decimal
1,383,791
Country
RU
Tail
RA-73071
Type
B752
No current signal · last broadcast 2h ago
Flights observed
97
Distinct callsigns
20
Country
RU
Last broadcast
2h ago

Last known position

Most recent position reported by Mode-S 151D6F.

Country allocation

The ICAO 24-bit address 151D6F 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-06-15 AZV3014 - Jun 15, 05:25 UTCJun 15, 07:15 UTC1h 50m
2026-06-14 AZV486 AYT → SGC Jun 14, 12:05 UTCJun 15, 03:30 UTC15h 25m
2026-06-14 AZV3035 SCW → AYT Jun 14, 04:45 UTCJun 14, 09:50 UTC5h 5m
2026-06-13 AZV3036 AYT → SCW Jun 13, 04:20 UTCJun 13, 20:40 UTC16h 20m
2026-06-12 AZV411 VKO → DLM Jun 12, 23:50 UTCJun 13, 02:05 UTC2h 15m
2026-06-12 AZV411 VKO → DLM Jun 12, 05:50 UTCJun 13, 02:05 UTC20h 15m
2026-06-12 AZV3014 - Jun 12, 04:30 UTCJun 13, 02:05 UTC21h 35m
2026-06-11 AZV3017 ARH → AYT Jun 11, 21:00 UTCJun 12, 02:20 UTC5h 21m
2026-06-11 AZV3018 AYT → ARH Jun 11, 12:50 UTCJun 11, 18:20 UTC5h 30m
2026-06-10 AZV3010 BJV → VKO Jun 10, 17:35 UTCJun 11, 10:55 UTC17h 20m
2026-06-10 AZV3071 ULV → AYT Jun 10, 14:00 UTCJun 10, 14:35 UTC35m
2026-06-10 AZV3071 ULV → AYT Jun 10, 11:35 UTCJun 10, 11:50 UTC15m
2026-06-09 AZV3072 AYT → ULV Jun 9, 23:30 UTCJun 10, 01:15 UTC1h 45m
2026-06-09 AZV3014 AYT → VKO Jun 9, 10:15 UTCJun 9, 21:50 UTC11h 35m
2026-06-08 AZV3033 REN → AYT Jun 8, 22:25 UTCJun 9, 08:00 UTC9h 35m
2026-06-08 AZV3016 AYT → KZN Jun 8, 09:25 UTCJun 8, 20:45 UTC11h 20m
2026-06-08 AZV3017 ARH → AYT Jun 8, 04:35 UTCJun 8, 06:45 UTC2h 10m
2026-06-07 AZV3018 AYT → ARH Jun 7, 22:30 UTCJun 7, 23:00 UTC30m
2026-06-07 AZV3018 AYT → ARH Jun 7, 17:20 UTCJun 7, 19:55 UTC2h 35m
2026-06-06 AZV3014 AYT → VKO Jun 6, 20:35 UTCJun 6, 23:05 UTC2h 30m
2026-06-06 AZV3007 VKO → AYT Jun 6, 14:45 UTCJun 6, 18:55 UTC4h 10m
2026-06-06 AZV3010 BJV → VKO Jun 6, 11:25 UTCJun 6, 11:35 UTC10m
2026-06-05 AZV3072 AYT → ULV Jun 5, 20:05 UTCJun 6, 09:30 UTC13h 25m
2026-06-05 AZV3009 VKO → BJV Jun 5, 14:40 UTCJun 5, 16:40 UTC2h 0m
2026-06-05 AZV3009 VKO → BJV Jun 5, 12:35 UTCJun 5, 12:50 UTC15m
2026-06-05 AZV3014 AYT → VKO Jun 5, 04:15 UTCJun 5, 06:50 UTC2h 35m
2026-06-04 AZV3018 AYT → ARH Jun 4, 13:00 UTCJun 5, 02:40 UTC13h 40m
2026-06-04 AZV3067 AER → AYT Jun 4, 09:40 UTCJun 4, 11:20 UTC1h 40m
2026-06-03 AZV486 AYT → SGC Jun 3, 10:45 UTCJun 4, 01:50 UTC15h 5m
2026-06-03 AZV3035 SCW → AYT Jun 3, 03:30 UTCJun 3, 08:05 UTC4h 35m
2026-06-02 AZV3036 AYT → SCW Jun 2, 17:15 UTCJun 2, 21:50 UTC4h 35m
2026-06-02 AZV3013 VKO → AYT Jun 2, 15:10 UTCJun 2, 15:25 UTC15m
2026-06-02 AZV3012 BJV → VKO Jun 2, 03:55 UTCJun 2, 14:30 UTC10h 35m
2026-06-01 AZV3011 VKO → BJV Jun 1, 15:20 UTCJun 2, 02:05 UTC10h 45m
2026-05-31 AZV486 AYT → SGC May 31, 21:10 UTCJun 1, 13:25 UTC16h 15m
2026-05-31 AZV3015 LED → AYT May 31, 18:15 UTCMay 31, 18:35 UTC20m
2026-05-31 AZV3016 - May 31, 08:45 UTCMay 31, 17:30 UTC8h 45m
2026-05-30 AZV3016 - May 30, 19:50 UTCMay 31, 17:30 UTC21h 40m
2026-05-30 AZV3014 AYT → VKO May 30, 18:35 UTCMay 31, 17:30 UTC22h 55m
2026-05-30 AZV3007 VKO → AYT May 30, 15:55 UTCMay 30, 16:15 UTC20m
2026-05-30 AZV412 DLM → VKO May 30, 05:35 UTCMay 30, 15:15 UTC9h 40m
2026-05-30 AZV411 VKO → DLM May 30, 01:25 UTCMay 30, 03:15 UTC1h 50m
2026-05-28 AZV3034 AYT → REN May 28, 18:20 UTCMay 28, 20:15 UTC1h 55m
2026-05-28 AZV3007 VKO → AYT May 28, 14:35 UTCMay 28, 16:25 UTC1h 50m
2026-05-28 AZV3008 AYT → VKO May 28, 05:15 UTCMay 28, 07:00 UTC1h 45m
2026-05-27 AZV486 AYT → SGC May 27, 11:55 UTCMay 28, 03:40 UTC15h 45m
2026-05-27 AZV3035 SCW → AYT May 27, 04:30 UTCMay 27, 04:45 UTC15m
2026-05-26 AZV3014 AYT → VKO May 26, 05:00 UTCMay 26, 06:54 UTC1h 55m
2026-05-26 AZV3033 REN → AYT May 26, 02:44 UTCMay 26, 03:05 UTC20m
2026-05-25 AZV3034 AYT → REN May 25, 17:00 UTCMay 26, 02:04 UTC9h 5m

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

Mode-S 151D6F frequently asked

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