sensors Mode-S transponder

151D77

ICAO 24-bit transponder address · allocated to Russia

Currently assigned to RA-73079 · BOEING 767-300

Hex
151D77
Octal
05216567
Decimal
1,383,799
Country
RU
Tail
RA-73079
Type
B763
No current signal · last broadcast 16d ago
Flights observed
54
Distinct callsigns
20
Country
RU
Last broadcast
16d ago

Last known position

Most recent position reported by Mode-S 151D77.

Country allocation

The ICAO 24-bit address 151D77 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-13 AZV2502 CXR → VKO May 13, 21:25 UTCMay 13, 21:35 UTC10m
2026-05-13 AZV2502 CXR → VKO May 13, 02:20 UTCMay 13, 20:55 UTC18h 35m
2026-05-12 AZV2527 UFA → CXR May 12, 11:50 UTCMay 13, 11:45 UTC23h 55m
2026-05-11 AZV2528 CXR → UFA May 11, 22:35 UTCMay 12, 12:10 UTC13h 36m
2026-05-11 AZV2564 CXR → PEE May 11, 12:30 UTCMay 12, 11:45 UTC23h 16m
2026-05-10 AZV2564 CXR → PEE May 10, 21:00 UTCMay 11, 13:05 UTC16h 5m
2026-05-10 AZV2538 CXR → SVX May 10, 12:59 UTCMay 10, 21:19 UTC8h 20m
2026-05-09 AZV2577 IKT → CXR May 9, 22:05 UTCMay 9, 22:20 UTC15m
2026-05-09 AZV2551 CEK → CXR May 9, 01:50 UTCMay 9, 18:25 UTC16h 35m
2026-05-08 AZV2552 CXR → CEK May 8, 17:00 UTCMay 9, 02:15 UTC9h 15m
2026-05-07 AZV2552 CXR → CEK May 7, 23:14 UTCMay 8, 17:30 UTC18h 15m
2026-05-07 AZV2584 CXR → OMS May 7, 18:25 UTCMay 8, 17:30 UTC23h 5m
2026-05-06 AZV2584 CXR → OMS May 6, 22:50 UTCMay 7, 19:00 UTC20h 10m
2026-05-06 AZV2501 VKO → CXR May 6, 03:50 UTCMay 6, 23:10 UTC19h 19m
2026-05-06 AZV2501 VKO → CXR May 6, 02:45 UTCMay 6, 23:10 UTC20h 24m
2026-05-03 AZV2903 VKO → HKT May 3, 02:15 UTCMay 3, 12:55 UTC10h 39m
2026-05-02 AZV2504 CXR → VKO May 2, 18:55 UTCMay 2, 19:10 UTC15m
2026-05-02 AZV2504 CXR → VKO May 2, 01:00 UTCMay 2, 18:15 UTC17h 15m
2026-04-24 AZV2504 CXR → VKO Apr 24, 05:40 UTCApr 24, 10:45 UTC5h 5m
2026-04-23 AZV2504 CXR → VKO Apr 23, 07:50 UTCApr 24, 07:35 UTC23h 45m
2026-04-23 AZV2528 CXR → UFA Apr 23, 06:45 UTCApr 24, 05:45 UTC23h 0m
2026-04-22 AZV2528 CXR → UFA Apr 22, 14:20 UTCApr 23, 08:40 UTC18h 20m
2026-04-22 AZV2501 VKO → CXR Apr 22, 03:50 UTCApr 22, 22:00 UTC18h 10m
2026-04-22 AZV2501 VKO → CXR Apr 22, 01:55 UTCApr 22, 22:00 UTC20h 5m
2026-04-22 AZV2501 VKO → CXR Apr 22, 00:35 UTCApr 22, 22:00 UTC21h 25m
2026-04-21 AZV2501 VKO → CXR Apr 21, 09:50 UTCApr 22, 05:20 UTC19h 30m
2026-04-21 AZV2501 VKO → CXR Apr 21, 07:50 UTCApr 22, 05:20 UTC21h 30m
2026-04-21 AZV2501 VKO → CXR Apr 21, 05:50 UTCApr 22, 05:20 UTC23h 30m
2026-04-21 AZV2602 PQC → VKO Apr 21, 05:40 UTCApr 22, 03:45 UTC22h 5m
2026-04-20 AZV2637 SVX → PQC Apr 20, 22:20 UTCApr 21, 02:40 UTC4h 20m
2026-04-19 AZV2638 PQC → SVX Apr 19, 22:10 UTCApr 20, 14:25 UTC16h 15m
2026-04-19 AZV2601 VKO → PQC Apr 19, 07:50 UTCApr 20, 07:45 UTC23h 55m
2026-04-19 AZV2601 VKO → PQC Apr 19, 06:55 UTCApr 20, 02:20 UTC19h 25m
2026-04-19 AZV2904 - Apr 19, 00:00 UTCApr 19, 23:45 UTC23h 45m
2026-04-18 AZV2904 - Apr 18, 22:25 UTCApr 19, 09:25 UTC11h 0m
2026-04-17 AZV2902 HKT → VKO Apr 17, 12:05 UTCApr 17, 12:40 UTC35m
2026-04-17 AZV2902 HKT → VKO Apr 17, 07:20 UTCApr 17, 08:05 UTC45m
2026-04-17 AZV2902 HKT → VKO Apr 17, 05:35 UTCApr 17, 07:15 UTC1h 40m
2026-04-16 AZV2923 - Apr 16, 21:14 UTCApr 16, 21:30 UTC15m
2026-04-16 AZV2923 - Apr 16, 20:40 UTCApr 16, 21:10 UTC30m
2026-04-16 AZV2924 HKT → KUF Apr 16, 09:35 UTCApr 16, 10:45 UTC1h 10m
2026-04-16 AZV2924 HKT → KUF Apr 16, 08:04 UTCApr 16, 08:50 UTC45m
2026-04-16 AZV2985 SGC → HKT Apr 16, 02:24 UTCApr 16, 03:04 UTC40m
2026-04-15 AZV2985 SGC → HKT Apr 15, 20:15 UTCApr 15, 21:00 UTC45m
2026-04-15 AZV2986 HKT → SGC Apr 15, 11:05 UTCApr 15, 12:01 UTC55m
2026-04-15 AZV2986 HKT → SGC Apr 15, 05:00 UTCApr 15, 05:35 UTC35m
2026-04-14 AZV2901 VKO → HKT Apr 14, 22:55 UTCApr 15, 00:35 UTC1h 40m
2026-04-14 AZV2901 VKO → HKT Apr 14, 22:10 UTCApr 14, 22:50 UTC40m
2026-04-14 AZV2502 - Apr 14, 07:10 UTCApr 14, 07:40 UTC30m
2026-04-14 AZV2502 - Apr 14, 05:15 UTCApr 14, 07:10 UTC1h 55m

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

Mode-S 151D77 frequently asked

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