sensors Mode-S transponder

151D4A

ICAO 24-bit transponder address · allocated to Russia

Currently assigned to RA-73034 · BOEING 767-300

Hex
151D4A
Octal
05216512
Decimal
1,383,754
Country
RU
Tail
RA-73034
Type
B763
No current signal · last broadcast 21h ago
Flights observed
109
Distinct callsigns
20
Country
RU
Last broadcast
21h ago

Last known position

Most recent position reported by Mode-S 151D4A.

Country allocation

The ICAO 24-bit address 151D4A 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-28 AZV2504 CXR → VKO May 28, 13:40 UTCMay 29, 03:50 UTC14h 10m
2026-05-28 AZV2504 CXR → VKO May 28, 06:35 UTCMay 29, 03:50 UTC21h 15m
2026-05-28 AZV2504 CXR → VKO May 28, 06:25 UTCMay 29, 03:50 UTC21h 25m
2026-05-28 AZV2559 TJM → CXR May 28, 01:20 UTCMay 29, 00:30 UTC23h 10m
2026-05-27 AZV2559 TJM → CXR May 27, 20:35 UTCMay 28, 19:00 UTC22h 25m
2026-05-27 AZV2503 - May 27, 18:35 UTCMay 28, 18:30 UTC23h 55m
2026-05-27 AZV2503 - May 27, 16:35 UTCMay 28, 14:00 UTC21h 25m
2026-05-24 AZV2502 CXR → VKO May 24, 19:10 UTCMay 24, 23:15 UTC4h 5m
2026-05-24 AZV2502 CXR → VKO May 24, 02:35 UTCMay 24, 23:15 UTC20h 40m
2026-05-24 AZV2502 CXR → VKO May 24, 02:20 UTCMay 24, 23:15 UTC20h 55m
2026-05-22 AZV2563 PEE → CXR May 22, 22:50 UTCMay 23, 16:40 UTC17h 49m
2026-05-22 AZV2563 PEE → CXR May 22, 18:35 UTCMay 23, 16:40 UTC22h 4m
2026-05-22 AZV2563 PEE → CXR May 22, 16:35 UTCMay 23, 16:30 UTC23h 54m
2026-05-22 AZV2564 CXR → PEE May 22, 16:15 UTCMay 23, 01:05 UTC8h 50m
2026-05-20 AZV2551 CEK → CXR May 20, 16:40 UTCMay 21, 06:45 UTC14h 5m
2026-05-19 AZV2583 OMS → CXR May 19, 23:40 UTCMay 20, 17:00 UTC17h 21m
2026-05-19 AZV2584 CXR → OMS May 19, 19:05 UTCMay 20, 17:00 UTC21h 56m
2026-05-18 AZV2584 CXR → OMS May 18, 21:15 UTCMay 19, 19:30 UTC22h 15m
2026-05-18 AZV2501 VKO → CXR May 18, 02:35 UTCMay 18, 21:35 UTC18h 59m
2026-05-18 AZV2501 VKO → CXR May 18, 01:30 UTCMay 18, 21:35 UTC20h 4m
2026-05-17 AZV2501 VKO → CXR May 17, 04:50 UTCMay 18, 04:30 UTC23h 40m
2026-05-16 AZV2904 HKT → VKO May 16, 11:11 UTCMay 17, 05:05 UTC17h 55m
2026-05-16 AZV2904 HKT → VKO May 16, 07:01 UTCMay 17, 05:05 UTC22h 4m
2026-05-16 AZV2938 HKT → SVX May 16, 02:55 UTCMay 17, 00:50 UTC21h 55m
2026-05-16 AZV2938 HKT → SVX May 16, 02:25 UTCMay 17, 00:30 UTC22h 5m
2026-05-15 AZV2938 HKT → SVX May 15, 17:30 UTCMay 16, 15:25 UTC21h 56m
2026-05-15 AZV6691 SVO → SVO May 15, 07:40 UTCMay 15, 08:20 UTC40m
2026-05-14 AZV2504 CXR → VKO May 14, 20:10 UTCMay 14, 20:45 UTC35m
2026-05-14 AZV2503 VKO → CXR May 14, 02:35 UTCMay 14, 19:35 UTC17h 0m
2026-05-11 AZV2902 HKT → VKO May 11, 19:25 UTCMay 12, 09:30 UTC14h 5m
2026-05-11 AZV2902 HKT → VKO May 11, 11:05 UTCMay 12, 09:30 UTC22h 26m
2026-05-11 AZV2960 HKT → TJM May 11, 09:40 UTCMay 12, 08:30 UTC22h 51m
2026-05-11 AZV2960 HKT → TJM May 11, 00:34 UTCMay 11, 22:35 UTC22h 0m
2026-05-11 AZV2960 HKT → TJM May 11, 00:15 UTCMay 11, 19:30 UTC19h 16m
2026-05-10 AZV2923 KUF → HKT May 10, 11:05 UTCMay 11, 10:15 UTC23h 10m
2026-05-10 AZV2924 HKT → KUF May 10, 09:35 UTCMay 11, 02:25 UTC16h 50m
2026-05-10 AZV2924 HKT → KUF May 10, 04:34 UTCMay 11, 02:25 UTC21h 50m
2026-05-10 AZV2924 HKT → KUF May 10, 03:50 UTCMay 11, 02:25 UTC22h 35m
2026-05-09 AZV2924 HKT → KUF May 9, 13:05 UTCMay 10, 12:10 UTC23h 5m
2026-05-09 AZV2986 HKT → SGC May 9, 06:40 UTCMay 10, 05:04 UTC22h 25m
2026-05-09 AZV2986 HKT → SGC May 9, 02:45 UTCMay 9, 14:00 UTC11h 15m
2026-05-07 AZV2948 HKT → OVB May 7, 23:14 UTCMay 8, 13:15 UTC14h 0m
2026-05-07 AZV2948 HKT → OVB May 7, 08:35 UTCMay 8, 07:34 UTC23h 0m
2026-05-07 AZV2920 HKT → KZN May 7, 06:35 UTCMay 8, 06:30 UTC23h 55m
2026-05-06 AZV2955 MRV → HKT May 6, 22:15 UTCMay 7, 08:55 UTC10h 40m
2026-05-06 AZV2955 MRV → HKT May 6, 08:40 UTCMay 7, 08:30 UTC23h 50m
2026-05-06 AZV2955 MRV → HKT May 6, 07:15 UTCMay 7, 06:30 UTC23h 14m
2026-05-06 AZV2955 MRV → HKT May 6, 00:35 UTCMay 7, 00:25 UTC23h 49m
2026-05-05 AZV2937 SVX → HKT May 5, 22:35 UTCMay 6, 22:30 UTC23h 54m
2026-05-05 AZV2937 SVX → HKT May 5, 15:20 UTCMay 6, 09:40 UTC18h 20m

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

Mode-S 151D4A frequently asked

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