sensors Mode-S transponder
151E8D
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73357
- Hex
- 151E8D
- Octal
- 05217215
- Decimal
- 1,384,077
- Country
- RU
- Tail
- RA-73357
- Type
- B752
- Flights observed
- 176
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- Jul 26, 12:40 UTC
Current position
Country allocation
The ICAO 24-bit address 151E8D 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 |
|---|---|---|---|
| AZV3009 | - | 12 | 2026-07-13 |
| AZV3010 | - | 9 | 2026-07-15 |
| AZV3008 | Azov Avia Airlines | 9 | 2026-07-24 |
| AZV3034 | - | 8 | 2026-07-20 |
| AZV3072 | - | 7 | 2026-07-21 |
| AZV3035 | Azov Avia Airlines | 7 | 2026-07-26 |
| AZV3014 | - | 7 | 2026-06-16 |
| AZV485 | Azov Avia Airlines | 6 | 2026-06-11 |
| AZV3036 | Azov Avia Airlines | 6 | 2026-07-25 |
| AZV3017 | Azov Avia Airlines | 6 | 2026-06-01 |
| AZV486 | Azov Avia Airlines | 5 | 2026-07-26 |
| AZV3018 | - | 5 | 2026-06-14 |
| AZV3007 | Azov Avia Airlines | 5 | 2026-06-11 |
| AZV3001 | Azov Avia Airlines | 5 | 2026-05-18 |
| AZV412 | Azov Avia Airlines | 4 | 2026-07-25 |
| AZV411 | Azov Avia Airlines | 4 | 2026-07-24 |
| AZV3071 | Azov Avia Airlines | 4 | 2026-06-13 |
| AZV3016 | Azov Avia Airlines | 4 | 2026-07-20 |
| AZV3013 | Azov Avia Airlines | 4 | 2026-05-30 |
| AZV3004 | Azov Avia Airlines | 4 | 2026-05-18 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | AZV486 | AYT → SGC | Jul 26, 10:55 UTC | Jul 26, 12:40 UTC | 1h 45m |
| 2026-07-26 | AZV3035 | SCW → AYT | Jul 26, 04:00 UTC | Jul 26, 09:05 UTC | 5h 6m |
| 2026-07-25 | AZV3036 | AYT → SCW | Jul 25, 18:10 UTC | Jul 25, 19:50 UTC | 1h 40m |
| 2026-07-25 | AZV412 | DLM → VKO | Jul 25, 04:25 UTC | Jul 25, 16:40 UTC | 12h 15m |
| 2026-07-24 | AZV411 | VKO → DLM | Jul 24, 07:20 UTC | Jul 25, 02:30 UTC | 19h 10m |
| 2026-07-24 | AZV3008 | AYT → VKO | Jul 24, 05:50 UTC | Jul 25, 02:30 UTC | 20h 40m |
| 2026-07-24 | AZV3033 | REN → AYT | Jul 24, 02:10 UTC | Jul 24, 04:00 UTC | 1h 50m |
| 2026-07-21 | AZV3072 | AYT → AYT | Jul 21, 13:30 UTC | Jul 22, 03:50 UTC | 14h 20m |
| 2026-07-20 | AZV3034 | - | Jul 20, 17:50 UTC | Jul 20, 19:35 UTC | 1h 45m |
| 2026-07-20 | AZV3015 | LED → AYT | Jul 20, 15:10 UTC | Jul 20, 15:25 UTC | 15m |
| 2026-07-20 | AZV3016 | AYT → KZN | Jul 20, 04:40 UTC | Jul 20, 14:25 UTC | 9h 45m |
| 2026-07-19 | AZV486 | AYT → SGC | Jul 19, 10:50 UTC | Jul 20, 03:05 UTC | 16h 15m |
| 2026-07-19 | AZV3035 | - | Jul 19, 08:25 UTC | Jul 19, 08:55 UTC | 30m |
| 2026-07-19 | AZV3035 | - | Jul 19, 03:50 UTC | Jul 19, 04:30 UTC | 40m |
| 2026-07-18 | AZV3036 | - | Jul 18, 17:45 UTC | Jul 18, 21:50 UTC | 4h 5m |
| 2026-07-18 | AZV412 | - | Jul 18, 04:10 UTC | Jul 18, 16:00 UTC | 11h 50m |
| 2026-07-18 | AZV411 | - | Jul 18, 00:15 UTC | Jul 18, 02:14 UTC | 2h 0m |
| 2026-07-15 | AZV3010 | - | Jul 15, 08:10 UTC | Jul 15, 09:50 UTC | 1h 40m |
| 2026-07-14 | AZV3072 | AYT → AYT | Jul 14, 19:30 UTC | Jul 15, 06:40 UTC | 11h 9m |
| 2026-07-13 | AZV3034 | - | Jul 13, 23:20 UTC | Jul 14, 18:00 UTC | 18h 40m |
| 2026-07-13 | AZV3034 | AYT → AYT | Jul 13, 22:55 UTC | Jul 14, 18:00 UTC | 19h 5m |
| 2026-07-13 | AZV3016 | - | Jul 13, 04:25 UTC | Jul 13, 06:05 UTC | 1h 40m |
| 2026-07-13 | AZV3009 | - | Jul 13, 02:05 UTC | Jul 13, 02:20 UTC | 15m |
| 2026-07-11 | AZV412 | - | Jul 11, 04:20 UTC | Jul 11, 06:10 UTC | 1h 50m |
| 2026-07-11 | AZV411 | - | Jul 11, 01:40 UTC | Jul 11, 02:15 UTC | 35m |
| 2026-07-10 | AZV6691 | - | Jul 10, 10:20 UTC | Jul 10, 10:35 UTC | 15m |
| 2026-06-17 | AZV3010 | BJV → VKO | Jun 17, 15:35 UTC | Jun 17, 17:10 UTC | 1h 35m |
| 2026-06-17 | AZV3072 | AYT → ULV | Jun 17, 02:55 UTC | Jun 17, 13:25 UTC | 10h 30m |
| 2026-06-16 | AZV3014 | - | Jun 16, 08:00 UTC | Jun 17, 01:15 UTC | 17h 16m |
| 2026-06-15 | AZV3034 | AYT → REN | Jun 15, 20:40 UTC | Jun 16, 06:15 UTC | 9h 35m |
| 2026-06-15 | AZV3015 | LED → AYT | Jun 15, 18:29 UTC | Jun 15, 18:55 UTC | 25m |
| 2026-06-15 | AZV3016 | AYT → KZN | Jun 15, 07:45 UTC | Jun 15, 09:40 UTC | 1h 55m |
| 2026-06-14 | AZV3018 | - | Jun 14, 16:15 UTC | Jun 14, 18:05 UTC | 1h 50m |
| 2026-06-13 | AZV3010 | BJV → VKO | Jun 13, 07:50 UTC | Jun 13, 22:50 UTC | 15h 0m |
| 2026-06-13 | AZV3071 | ULV → AYT | Jun 13, 05:30 UTC | Jun 13, 05:55 UTC | 25m |
| 2026-06-12 | AZV3072 | AYT → ULV | Jun 12, 20:05 UTC | Jun 13, 02:50 UTC | 6h 45m |
| 2026-06-12 | AZV3009 | VKO → BJV | Jun 12, 16:40 UTC | Jun 12, 17:00 UTC | 20m |
| 2026-06-12 | AZV3009 | VKO → BJV | Jun 12, 14:40 UTC | Jun 12, 15:55 UTC | 1h 15m |
| 2026-06-12 | AZV3008 | AYT → VKO | Jun 12, 10:05 UTC | Jun 12, 10:20 UTC | 15m |
| 2026-06-12 | AZV3008 | AYT → VKO | Jun 12, 05:55 UTC | Jun 12, 08:15 UTC | 2h 20m |
| 2026-06-11 | AZV3034 | AYT → REN | Jun 11, 17:45 UTC | Jun 12, 03:45 UTC | 10h 1m |
| 2026-06-11 | AZV3007 | VKO → AYT | Jun 11, 05:00 UTC | Jun 11, 16:00 UTC | 11h 0m |
| 2026-06-11 | AZV485 | SGC → AYT | Jun 11, 02:55 UTC | Jun 11, 03:15 UTC | 20m |
| 2026-06-10 | AZV485 | SGC → AYT | Jun 10, 23:55 UTC | Jun 11, 02:05 UTC | 2h 10m |
| 2026-06-10 | AZV485 | SGC → AYT | Jun 10, 04:30 UTC | Jun 11, 02:05 UTC | 21h 35m |
| 2026-06-09 | AZV3036 | AYT → SCW | Jun 9, 18:30 UTC | Jun 9, 20:10 UTC | 1h 40m |
| 2026-06-09 | AZV3012 | BJV → VKO | Jun 9, 03:55 UTC | Jun 9, 06:25 UTC | 2h 30m |
| 2026-06-09 | AZV3011 | VKO → BJV | Jun 9, 00:25 UTC | Jun 9, 02:15 UTC | 1h 50m |
| 2026-06-08 | AZV3011 | VKO → BJV | Jun 8, 21:40 UTC | Jun 8, 21:55 UTC | 15m |
| 2026-06-08 | AZV3014 | AYT → VKO | Jun 8, 06:25 UTC | Jun 8, 07:50 UTC | 1h 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-73357 page for operator, model, and routing details .