sensors Mode-S transponder

151D46

ICAO 24-bit transponder address · allocated to Russia

Currently assigned to RA-73030 · BOEING 767-300

Hex
151D46
Octal
05216506
Decimal
1,383,750
Country
RU
Tail
RA-73030
Type
B763
No current signal · last broadcast Apr 30, 08:10 UTC
Flights observed
55
Distinct callsigns
20
Country
RU
Last broadcast
Apr 30, 08:10 UTC

Last known position

Most recent position reported by Mode-S 151D46.

Country allocation

The ICAO 24-bit address 151D46 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-04-29 AZV2902 HKT → VKO Apr 29, 17:50 UTCApr 30, 08:10 UTC14h 19m
2026-04-29 AZV2959 TJM → HKT Apr 29, 07:35 UTCApr 30, 07:30 UTC23h 55m
2026-04-29 AZV2959 TJM → HKT Apr 29, 06:39 UTCApr 30, 05:30 UTC22h 50m
2026-04-28 AZV2959 TJM → HKT Apr 28, 23:35 UTCApr 29, 23:25 UTC23h 50m
2026-04-28 AZV2923 KUF → HKT Apr 28, 22:10 UTCApr 29, 21:30 UTC23h 21m
2026-04-28 AZV2923 KUF → HKT Apr 28, 18:20 UTCApr 29, 09:00 UTC14h 40m
2026-04-27 AZV2924 HKT → KUF Apr 27, 21:30 UTCApr 28, 12:05 UTC14h 35m
2026-04-27 AZV2924 HKT → KUF Apr 27, 13:35 UTCApr 28, 12:05 UTC22h 30m
2026-04-27 AZV2985 SGC → HKT Apr 27, 13:05 UTCApr 28, 11:30 UTC22h 25m
2026-04-27 AZV2985 SGC → HKT Apr 27, 07:35 UTCApr 28, 04:45 UTC21h 10m
2026-04-27 AZV2986 HKT → SGC Apr 27, 06:50 UTCApr 28, 04:45 UTC21h 55m
2026-04-27 AZV2986 HKT → SGC Apr 27, 03:35 UTCApr 27, 22:15 UTC18h 40m
2026-04-27 AZV2986 HKT → SGC Apr 27, 02:50 UTCApr 27, 22:15 UTC19h 25m
2026-04-26 AZV2986 HKT → SGC Apr 26, 20:55 UTCApr 27, 14:00 UTC17h 5m
2026-04-26 AZV2919 KZN → HKT Apr 26, 00:25 UTCApr 26, 17:15 UTC16h 50m
2026-04-25 AZV2920 HKT → KZN Apr 25, 02:40 UTCApr 25, 13:30 UTC10h 50m
2026-04-24 AZV2920 HKT → KZN Apr 24, 15:35 UTCApr 25, 13:30 UTC21h 55m
2026-04-24 AZV2920 HKT → KZN Apr 24, 13:35 UTCApr 25, 13:30 UTC23h 55m
2026-04-24 AZV2956 HKT → MRV Apr 24, 13:10 UTCApr 25, 11:30 UTC22h 20m
2026-04-24 AZV2956 HKT → MRV Apr 24, 05:35 UTCApr 25, 04:55 UTC23h 20m
2026-04-24 AZV2956 HKT → MRV Apr 24, 03:35 UTCApr 25, 03:30 UTC23h 55m
2026-04-24 AZV2956 HKT → MRV Apr 24, 03:25 UTCApr 24, 16:00 UTC12h 35m
2026-04-23 AZV2937 SVX → HKT Apr 23, 15:35 UTCApr 24, 15:30 UTC23h 54m
2026-04-23 AZV2938 HKT → SVX Apr 23, 14:05 UTCApr 24, 13:30 UTC23h 25m
2026-04-23 AZV2938 HKT → SVX Apr 23, 09:35 UTCApr 24, 05:45 UTC20h 10m
2026-04-23 AZV2938 HKT → SVX Apr 23, 08:50 UTCApr 24, 05:45 UTC20h 55m
2026-04-23 AZV2938 HKT → SVX Apr 23, 03:35 UTCApr 24, 03:30 UTC23h 55m
2026-04-22 AZV2938 HKT → SVX Apr 22, 23:15 UTCApr 23, 16:50 UTC17h 35m
2026-04-22 AZV2938 HKT → SVX Apr 22, 17:35 UTCApr 23, 16:50 UTC23h 15m
2026-04-22 AZV2983 OMS → HKT Apr 22, 16:50 UTCApr 23, 15:00 UTC22h 10m
2026-04-22 AZV2984 HKT → OMS Apr 22, 06:15 UTCApr 23, 04:00 UTC21h 45m
2026-04-21 AZV2984 HKT → OMS Apr 21, 17:35 UTCApr 22, 17:30 UTC23h 55m
2026-04-21 AZV2924 HKT → KUF Apr 21, 15:15 UTCApr 22, 06:15 UTC15h 0m
2026-04-21 AZV2903 VKO → HKT Apr 21, 06:50 UTCApr 21, 09:10 UTC2h 20m
2026-04-20 AZV2903 VKO → HKT Apr 20, 08:35 UTCApr 21, 07:30 UTC22h 55m
2026-04-19 AZV2902 HKT → VKO Apr 19, 15:45 UTCApr 20, 09:10 UTC17h 25m
2026-04-19 AZV2902 HKT → VKO Apr 19, 08:10 UTCApr 20, 04:40 UTC20h 30m
2026-04-19 AZV2919 KZN → HKT Apr 19, 03:35 UTCApr 20, 03:30 UTC23h 55m
2026-04-19 AZV2920 HKT → KZN Apr 19, 01:15 UTCApr 19, 18:05 UTC16h 50m
2026-04-18 AZV2920 HKT → KZN Apr 18, 17:35 UTCApr 19, 17:30 UTC23h 55m
2026-04-18 AZV2920 HKT → KZN Apr 18, 17:25 UTCApr 19, 08:15 UTC14h 50m
2026-04-18 AZV2940 HKT → SVX Apr 18, 05:40 UTCApr 18, 06:35 UTC55m
2026-04-18 AZV2940 HKT → SVX Apr 18, 04:45 UTCApr 18, 06:35 UTC1h 50m
2026-04-18 AZV2940 HKT → SVX Apr 18, 04:20 UTCApr 18, 05:05 UTC45m
2026-04-17 AZV2971 KJA → HKT Apr 17, 22:50 UTCApr 17, 23:20 UTC30m
2026-04-16 AZV2676 - Apr 16, 10:14 UTCApr 16, 11:04 UTC50m
2026-04-16 AZV2671 KJA → PQC Apr 16, 07:09 UTCApr 16, 07:49 UTC40m
2026-04-15 AZV2972 - Apr 15, 06:10 UTCApr 15, 06:50 UTC40m
2026-04-14 AZV2927 - Apr 14, 22:55 UTCApr 14, 23:50 UTC55m
2026-04-14 AZV2927 - Apr 14, 21:25 UTCApr 14, 22:50 UTC1h 25m

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

Mode-S 151D46 frequently asked

What is Mode-S code 151D46?
151D46 is an ICAO 24-bit transponder address. Allocated to Russia. Assigned to RA-73030.
Where is Mode-S 151D46 registered?
Mode-S code 151D46 is allocated to Russia (RU). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 151D46 broadcasting right now?
No active broadcast right now. Last signal was Apr 30, 08:10 UTC.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 151D46, octal 05216506, decimal 1,383,750.
What flights does 151D46 operate?
Mode-S 151D46 has broadcast 20 distinct callsigns, including AZV2920, AZV2938, AZV2986, AZV2956, AZV2959.