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
- Flights observed
- 179
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 3d ago
Last known position
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
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| AZV3014 | Azov Avia Airlines | 14 | 2026-07-25 |
| AZV3035 | - | 13 | 2026-07-15 |
| AZV3072 | Azov Avia Airlines | 11 | 2026-07-24 |
| AZV3036 | - | 11 | 2026-07-14 |
| AZV3007 | - | 11 | 2026-07-09 |
| AZV486 | Azov Avia Airlines | 10 | 2026-07-22 |
| AZV3013 | - | 9 | 2026-07-14 |
| AZV3010 | Azov Avia Airlines | 9 | 2026-07-25 |
| AZV3008 | Azov Avia Airlines | 9 | 2026-07-23 |
| AZV3071 | Azov Avia Airlines | 7 | 2026-07-25 |
| AZV3034 | - | 7 | 2026-07-16 |
| AZV411 | Azov Avia Airlines | 6 | 2026-07-21 |
| AZV3033 | Azov Avia Airlines | 6 | 2026-07-17 |
| AZV3009 | Azov Avia Airlines | 6 | 2026-07-26 |
| AZV3016 | Azov Avia Airlines | 5 | 2026-07-06 |
| AZV3002 | Azov Avia Airlines | 5 | 2026-05-18 |
| AZV412 | Azov Avia Airlines | 4 | 2026-07-21 |
| AZV3019 | - | 4 | 2026-05-15 |
| AZV3018 | Azov Avia Airlines | 4 | 2026-06-11 |
| AZV463 | Azov Avia Airlines | 3 | 2026-05-17 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | AZV440 | AYT → SVX | Jul 26, 21:20 UTC | Jul 26, 21:45 UTC | 25m |
| 2026-07-26 | AZV3009 | VKO → BJV | Jul 26, 14:55 UTC | Jul 26, 19:30 UTC | 4h 35m |
| 2026-07-25 | AZV3014 | AYT → VKO | Jul 25, 18:50 UTC | Jul 25, 20:35 UTC | 1h 45m |
| 2026-07-25 | AZV3010 | BJV → VKO | Jul 25, 05:35 UTC | Jul 25, 17:05 UTC | 11h 30m |
| 2026-07-25 | AZV3071 | ULV → AYT | Jul 25, 03:30 UTC | Jul 25, 04:00 UTC | 30m |
| 2026-07-24 | AZV3072 | AYT → ULV | Jul 24, 17:45 UTC | Jul 24, 19:30 UTC | 1h 45m |
| 2026-07-24 | AZV3009 | - | Jul 24, 14:40 UTC | Jul 24, 15:55 UTC | 1h 15m |
| 2026-07-23 | AZV3008 | AYT → VKO | Jul 23, 04:45 UTC | Jul 23, 06:30 UTC | 1h 45m |
| 2026-07-22 | AZV486 | AYT → SGC | Jul 22, 11:20 UTC | Jul 23, 03:05 UTC | 15h 45m |
| 2026-07-21 | AZV412 | DLM → VKO | Jul 21, 04:40 UTC | Jul 21, 18:30 UTC | 13h 50m |
| 2026-07-21 | AZV411 | VKO → DLM | Jul 21, 01:45 UTC | Jul 21, 02:25 UTC | 40m |
| 2026-07-18 | AZV3014 | - | Jul 18, 17:55 UTC | Jul 18, 19:40 UTC | 1h 45m |
| 2026-07-18 | AZV3010 | - | Jul 18, 03:50 UTC | Jul 18, 05:35 UTC | 1h 45m |
| 2026-07-17 | AZV3072 | - | Jul 17, 06:10 UTC | Jul 18, 00:55 UTC | 18h 45m |
| 2026-07-17 | AZV3033 | REN → AYT | Jul 17, 02:50 UTC | Jul 17, 04:29 UTC | 1h 40m |
| 2026-07-16 | AZV3034 | - | Jul 16, 05:50 UTC | Jul 17, 04:29 UTC | 22h 40m |
| 2026-07-15 | AZV486 | - | Jul 15, 12:00 UTC | Jul 16, 03:35 UTC | 15h 35m |
| 2026-07-15 | AZV3035 | - | Jul 15, 04:30 UTC | Jul 15, 10:00 UTC | 5h 30m |
| 2026-07-14 | AZV3036 | - | Jul 14, 18:40 UTC | Jul 14, 22:55 UTC | 4h 14m |
| 2026-07-14 | AZV3013 | - | Jul 14, 16:10 UTC | Jul 14, 16:45 UTC | 35m |
| 2026-07-14 | AZV412 | - | Jul 14, 08:25 UTC | Jul 14, 08:45 UTC | 20m |
| 2026-07-14 | AZV412 | - | Jul 14, 04:30 UTC | Jul 14, 05:00 UTC | 30m |
| 2026-07-13 | AZV411 | - | Jul 13, 22:25 UTC | Jul 14, 02:45 UTC | 4h 20m |
| 2026-07-13 | AZV3014 | - | Jul 13, 10:30 UTC | Jul 13, 10:50 UTC | 20m |
| 2026-07-13 | AZV3014 | - | Jul 13, 06:40 UTC | Jul 13, 08:25 UTC | 1h 45m |
| 2026-07-12 | AZV486 | AYT → AYT | Jul 12, 12:35 UTC | Jul 13, 04:45 UTC | 16h 10m |
| 2026-07-12 | AZV3035 | - | Jul 12, 06:40 UTC | Jul 12, 11:01 UTC | 4h 20m |
| 2026-07-12 | AZV3035 | - | Jul 12, 05:35 UTC | Jul 12, 05:50 UTC | 15m |
| 2026-07-11 | AZV3036 | - | Jul 11, 19:20 UTC | Jul 11, 21:00 UTC | 1h 40m |
| 2026-07-11 | AZV3013 | - | Jul 11, 17:20 UTC | Jul 11, 17:55 UTC | 35m |
| 2026-07-10 | AZV3072 | AYT → ULV | Jul 10, 19:10 UTC | Jul 10, 20:50 UTC | 1h 40m |
| 2026-07-10 | AZV3008 | - | Jul 10, 09:35 UTC | Jul 10, 09:55 UTC | 20m |
| 2026-07-10 | AZV3008 | - | Jul 10, 06:00 UTC | Jul 10, 07:40 UTC | 1h 40m |
| 2026-07-09 | AZV3034 | - | Jul 9, 17:40 UTC | Jul 9, 19:20 UTC | 1h 40m |
| 2026-07-09 | AZV3007 | - | Jul 9, 14:10 UTC | Jul 9, 16:15 UTC | 2h 5m |
| 2026-07-08 | AZV485 | - | Jul 8, 11:20 UTC | Jul 9, 03:15 UTC | 15h 55m |
| 2026-07-08 | AZV3035 | - | Jul 8, 08:45 UTC | Jul 8, 09:25 UTC | 40m |
| 2026-07-08 | AZV3035 | - | Jul 8, 04:05 UTC | Jul 8, 04:20 UTC | 15m |
| 2026-07-07 | AZV3036 | - | Jul 7, 10:45 UTC | Jul 7, 12:25 UTC | 1h 40m |
| 2026-07-07 | AZV3033 | - | Jul 7, 08:25 UTC | Jul 7, 09:10 UTC | 45m |
| 2026-07-06 | AZV3033 | - | Jul 6, 09:50 UTC | Jul 7, 09:10 UTC | 23h 20m |
| 2026-07-06 | AZV3016 | AYT → KZN | Jul 6, 08:25 UTC | Jul 6, 10:10 UTC | 1h 45m |
| 2026-07-05 | AZV3035 | - | Jul 5, 21:15 UTC | Jul 5, 22:15 UTC | 1h 0m |
| 2026-07-05 | AZV3036 | - | Jul 5, 10:55 UTC | Jul 5, 12:40 UTC | 1h 45m |
| 2026-07-05 | AZV3013 | - | Jul 5, 07:15 UTC | Jul 5, 09:00 UTC | 1h 45m |
| 2026-07-04 | AZV3013 | - | Jul 4, 10:20 UTC | Jul 5, 09:00 UTC | 22h 40m |
| 2026-07-04 | AZV3072 | AYT → ULV | Jul 4, 01:00 UTC | Jul 4, 01:10 UTC | 10m |
| 2026-07-03 | AZV3072 | AYT → ULV | Jul 3, 21:50 UTC | Jul 3, 22:15 UTC | 25m |
| 2026-07-03 | AZV3008 | AYT → VKO | Jul 3, 08:15 UTC | Jul 3, 20:15 UTC | 12h 0m |
| 2026-07-02 | AZV3034 | - | Jul 2, 20:35 UTC | Jul 3, 06:40 UTC | 10h 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 .