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
- Flights observed
- 225
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- Jul 26, 13:35 UTC
Last known position
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
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| AZV2502 | - | 13 | 2026-07-11 |
| AZV2938 | Azov Avia Airlines | 12 | 2026-05-16 |
| AZV2555 | - | 11 | 2026-07-11 |
| AZV3002 | - | 8 | 2026-07-16 |
| AZV3003 | - | 7 | 2026-07-22 |
| AZV447 | - | 6 | 2026-07-03 |
| AZV444 | - | 6 | 2026-07-13 |
| AZV3062 | Azov Avia Airlines | 6 | 2026-07-26 |
| AZV3001 | - | 6 | 2026-07-17 |
| AZV2960 | Azov Avia Airlines | 6 | 2026-05-11 |
| AZV2937 | Azov Avia Airlines | 6 | 2026-05-05 |
| AZV3026 | - | 5 | 2026-07-02 |
| AZV3006 | Azov Avia Airlines | 5 | 2026-07-24 |
| AZV2602 | - | 5 | 2026-04-13 |
| AZV2556 | - | 5 | 2026-07-10 |
| AZV2501 | Azov Avia Airlines | 5 | 2026-05-18 |
| AZV438 | Azov Avia Airlines | 4 | 2026-07-25 |
| AZV4068 | Azov Avia Airlines | 4 | 2026-04-22 |
| AZV3022 | - | 4 | 2026-07-15 |
| AZV3005 | Azov Avia Airlines | 4 | 2026-07-25 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | AZV3062 | AYT → TJM | Jul 26, 11:55 UTC | Jul 26, 13:35 UTC | 1h 40m |
| 2026-07-25 | AZV438 | AYT → SVX | Jul 25, 20:55 UTC | Jul 26, 09:40 UTC | 12h 46m |
| 2026-07-25 | AZV3024 | - | Jul 25, 09:05 UTC | Jul 25, 18:50 UTC | 9h 45m |
| 2026-07-25 | AZV3005 | VKO → AYT | Jul 25, 06:05 UTC | Jul 25, 07:20 UTC | 1h 15m |
| 2026-07-24 | AZV3005 | VKO → AYT | Jul 24, 10:35 UTC | Jul 25, 07:20 UTC | 20h 45m |
| 2026-07-24 | AZV3006 | AYT → VKO | Jul 24, 09:15 UTC | Jul 25, 07:20 UTC | 22h 5m |
| 2026-07-23 | AZV3062 | AYT → TJM | Jul 23, 20:00 UTC | Jul 24, 07:20 UTC | 11h 20m |
| 2026-07-23 | AZV3025 | KUF → AYT | Jul 23, 16:25 UTC | Jul 23, 17:55 UTC | 1h 30m |
| 2026-07-22 | AZV3025 | KUF → AYT | Jul 22, 18:55 UTC | Jul 23, 17:55 UTC | 23h 0m |
| 2026-07-22 | AZV440 | - | Jul 22, 18:10 UTC | Jul 23, 16:30 UTC | 22h 20m |
| 2026-07-22 | AZV3003 | - | Jul 22, 14:35 UTC | Jul 22, 16:15 UTC | 1h 40m |
| 2026-07-21 | AZV3003 | - | Jul 21, 16:40 UTC | Jul 22, 16:15 UTC | 23h 35m |
| 2026-07-21 | AZV438 | AYT → SVX | Jul 21, 15:50 UTC | Jul 21, 17:35 UTC | 1h 45m |
| 2026-07-21 | AZV3003 | - | Jul 21, 13:15 UTC | Jul 21, 13:50 UTC | 35m |
| 2026-07-17 | AZV448 | AYT → OVB | Jul 17, 20:55 UTC | Jul 17, 22:40 UTC | 1h 45m |
| 2026-07-17 | AZV3001 | - | Jul 17, 18:29 UTC | Jul 17, 19:05 UTC | 35m |
| 2026-07-16 | AZV3002 | - | Jul 16, 05:00 UTC | Jul 16, 06:40 UTC | 1h 40m |
| 2026-07-15 | AZV3022 | - | Jul 15, 16:05 UTC | Jul 16, 03:10 UTC | 11h 5m |
| 2026-07-14 | AZV448 | AYT → AYT | Jul 14, 20:10 UTC | Jul 15, 11:30 UTC | 15h 19m |
| 2026-07-14 | AZV3001 | - | Jul 14, 06:45 UTC | Jul 14, 18:25 UTC | 11h 40m |
| 2026-07-13 | AZV444 | AYT → AYT | Jul 13, 17:30 UTC | Jul 14, 04:55 UTC | 11h 25m |
| 2026-07-13 | AZV3003 | - | Jul 13, 14:50 UTC | Jul 13, 15:20 UTC | 30m |
| 2026-07-11 | AZV2502 | - | Jul 11, 19:20 UTC | Jul 12, 09:35 UTC | 14h 15m |
| 2026-07-11 | AZV2502 | - | Jul 11, 13:00 UTC | Jul 12, 09:35 UTC | 20h 35m |
| 2026-07-11 | AZV2560 | - | Jul 11, 08:05 UTC | Jul 12, 06:30 UTC | 22h 25m |
| 2026-07-11 | AZV2560 | - | Jul 11, 02:35 UTC | Jul 12, 00:25 UTC | 21h 50m |
| 2026-07-11 | AZV2555 | - | Jul 11, 00:35 UTC | Jul 12, 00:25 UTC | 23h 50m |
| 2026-07-10 | AZV2555 | - | Jul 10, 22:55 UTC | Jul 11, 19:40 UTC | 20h 45m |
| 2026-07-10 | AZV2555 | - | Jul 10, 10:35 UTC | Jul 11, 08:30 UTC | 21h 56m |
| 2026-07-10 | AZV2555 | - | Jul 10, 08:35 UTC | Jul 11, 08:30 UTC | 23h 55m |
| 2026-07-10 | AZV2555 | - | Jul 10, 07:55 UTC | Jul 11, 03:20 UTC | 19h 25m |
| 2026-07-10 | AZV2556 | - | Jul 10, 03:25 UTC | Jul 11, 02:30 UTC | 23h 5m |
| 2026-07-09 | AZV2556 | - | Jul 9, 22:30 UTC | Jul 10, 12:15 UTC | 13h 45m |
| 2026-07-08 | AZV3004 | - | Jul 8, 04:30 UTC | Jul 8, 06:10 UTC | 1h 40m |
| 2026-07-07 | AZV438 | - | Jul 7, 15:30 UTC | Jul 8, 02:30 UTC | 11h 0m |
| 2026-07-07 | AZV3010 | - | Jul 7, 01:20 UTC | Jul 7, 13:15 UTC | 11h 55m |
| 2026-07-06 | AZV3007 | - | Jul 6, 23:10 UTC | Jul 6, 23:50 UTC | 40m |
| 2026-07-06 | AZV3007 | - | Jul 6, 02:35 UTC | Jul 6, 23:50 UTC | 21h 15m |
| 2026-07-06 | AZV3004 | - | Jul 6, 01:20 UTC | Jul 6, 23:50 UTC | 22h 30m |
| 2026-07-05 | AZV3020 | - | Jul 5, 12:45 UTC | Jul 5, 14:30 UTC | 1h 45m |
| 2026-07-04 | AZV3024 | - | Jul 4, 17:45 UTC | Jul 5, 10:05 UTC | 16h 20m |
| 2026-07-03 | AZV447 | - | Jul 3, 23:10 UTC | Jul 4, 12:10 UTC | 13h 0m |
| 2026-07-03 | AZV3006 | - | Jul 3, 08:55 UTC | Jul 3, 20:55 UTC | 12h 0m |
| 2026-07-02 | AZV3062 | - | Jul 2, 18:55 UTC | Jul 3, 06:40 UTC | 11h 45m |
| 2026-07-02 | AZV3026 | - | Jul 2, 05:20 UTC | Jul 2, 17:10 UTC | 11h 50m |
| 2026-07-01 | AZV486 | AYT → SGC | Jul 1, 10:40 UTC | Jul 2, 03:10 UTC | 16h 30m |
| 2026-07-01 | AZV3009 | - | Jul 1, 06:20 UTC | Jul 1, 08:10 UTC | 1h 50m |
| 2026-06-30 | AZV2502 | - | Jun 30, 09:50 UTC | Jul 1, 06:30 UTC | 20h 40m |
| 2026-06-29 | AZV2502 | - | Jun 29, 16:25 UTC | Jun 30, 10:25 UTC | 18h 1m |
| 2026-06-29 | AZV2502 | - | Jun 29, 09:44 UTC | Jun 30, 06:05 UTC | 20h 21m |
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 .