sensors Mode-S transponder
151D44
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73028 · AIRBUS A-321neo
- Hex
- 151D44
- Octal
- 05216504
- Decimal
- 1,383,748
- Country
- RU
- Tail
- RA-73028
- Type
- A21N
- Flights observed
- 91
- Distinct callsigns
- 5
- Country
- RU
- Last broadcast
- 13d ago
Last known position
Country allocation
The ICAO 24-bit address 151D44 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 5 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-01 | NWC9158 | - | Jul 1, 01:50 UTC | Jul 1, 08:10 UTC | 6h 20m |
| 2026-06-27 | NWC9152 | - | Jun 27, 10:25 UTC | Jun 27, 11:00 UTC | 35m |
| 2026-06-24 | NWC9152 | - | Jun 24, 03:40 UTC | Jun 24, 09:39 UTC | 6h 0m |
| 2026-06-23 | NWC9152 | - | Jun 23, 11:04 UTC | Jun 24, 09:39 UTC | 22h 35m |
| 2026-06-23 | NWC9152 | - | Jun 23, 06:04 UTC | Jun 23, 12:40 UTC | 6h 35m |
| 2026-06-18 | NWC9152 | - | Jun 18, 07:20 UTC | Jun 18, 12:25 UTC | 5h 5m |
| 2026-06-17 | NWC9152 | - | Jun 17, 09:05 UTC | Jun 18, 07:25 UTC | 22h 20m |
| 2026-06-17 | NWC9152 | - | Jun 17, 03:50 UTC | Jun 17, 09:25 UTC | 5h 35m |
| 2026-06-13 | NWC9152 | - | Jun 13, 04:10 UTC | Jun 13, 11:15 UTC | 7h 5m |
| 2026-06-12 | NWC9152 | - | Jun 12, 09:30 UTC | Jun 13, 04:45 UTC | 19h 14m |
| 2026-06-12 | NWC9152 | - | Jun 12, 05:05 UTC | Jun 13, 04:45 UTC | 23h 39m |
| 2026-06-12 | NWC9152 | - | Jun 12, 02:40 UTC | Jun 12, 10:55 UTC | 8h 15m |
| 2026-06-09 | NWC9158 | - | Jun 9, 13:05 UTC | Jun 10, 08:15 UTC | 19h 10m |
| 2026-06-09 | NWC9152 | - | Jun 9, 12:05 UTC | Jun 10, 08:15 UTC | 20h 10m |
| 2026-06-09 | NWC9152 | - | Jun 9, 04:25 UTC | Jun 9, 13:35 UTC | 9h 10m |
| 2026-06-08 | NWC9151 | - | Jun 8, 09:20 UTC | Jun 9, 06:25 UTC | 21h 5m |
| 2026-06-08 | NWC9151 | - | Jun 8, 02:45 UTC | Jun 8, 09:55 UTC | 7h 10m |
| 2026-06-04 | NWC9152 | - | Jun 4, 03:25 UTC | Jun 4, 11:20 UTC | 7h 55m |
| 2026-06-03 | NWC9151 | - | Jun 3, 09:05 UTC | Jun 4, 05:35 UTC | 20h 30m |
| 2026-06-03 | NWC9152 | - | Jun 3, 07:55 UTC | Jun 4, 05:35 UTC | 21h 40m |
| 2026-06-03 | NWC9152 | - | Jun 3, 04:25 UTC | Jun 3, 09:25 UTC | 5h 0m |
| 2026-05-29 | NWC9152 | - | May 29, 04:00 UTC | May 29, 12:00 UTC | 8h 0m |
| 2026-05-27 | NWC9152 | - | May 27, 08:00 UTC | May 27, 09:40 UTC | 1h 40m |
| 2026-05-25 | NWC9152 | - | May 25, 06:40 UTC | May 25, 16:15 UTC | 9h 35m |
| 2026-05-21 | NWC9152 | - | May 21, 04:20 UTC | May 21, 10:45 UTC | 6h 25m |
| 2026-05-20 | NWC9152 | - | May 20, 07:40 UTC | May 21, 04:25 UTC | 20h 45m |
| 2026-05-20 | NWC9152 | - | May 20, 04:15 UTC | May 20, 08:15 UTC | 4h 1m |
| 2026-05-16 | NWC9152 | - | May 16, 05:40 UTC | May 16, 12:40 UTC | 7h 1m |
| 2026-05-15 | NWC9152 | - | May 15, 11:05 UTC | May 16, 05:46 UTC | 18h 40m |
| 2026-05-15 | NWC9152 | - | May 15, 05:20 UTC | May 15, 12:30 UTC | 7h 10m |
| 2026-05-15 | NWC9151 | - | May 15, 04:05 UTC | May 15, 04:30 UTC | 25m |
| 2026-05-12 | NWC9152 | - | May 12, 03:00 UTC | May 12, 18:05 UTC | 15h 5m |
| 2026-05-11 | NWC9152 | - | May 11, 11:40 UTC | May 12, 04:10 UTC | 16h 30m |
| 2026-05-11 | NWC9152 | - | May 11, 05:20 UTC | May 12, 04:10 UTC | 22h 51m |
| 2026-05-11 | NWC9152 | - | May 11, 04:35 UTC | May 12, 03:00 UTC | 22h 25m |
| 2026-05-08 | NWC9152 | - | May 8, 03:30 UTC | May 8, 10:59 UTC | 7h 30m |
| 2026-05-06 | NWC9152 | - | May 6, 10:25 UTC | May 6, 10:35 UTC | 10m |
| 2026-05-06 | NWC9152 | - | May 6, 03:05 UTC | May 6, 09:25 UTC | 6h 20m |
| 2026-05-02 | NWN9152 | - | May 2, 04:20 UTC | May 2, 10:45 UTC | 6h 25m |
| 2026-05-01 | NWC9152 | - | May 1, 09:25 UTC | May 2, 05:20 UTC | 19h 55m |
| 2026-05-01 | NWC9152 | - | May 1, 03:05 UTC | May 1, 10:55 UTC | 7h 50m |
| 2026-04-30 | NWC9152 | - | Apr 30, 11:05 UTC | May 1, 10:55 UTC | 23h 50m |
| 2026-04-30 | NWC9152 | - | Apr 30, 10:55 UTC | May 1, 05:00 UTC | 18h 5m |
| 2026-04-30 | NWC9151 | - | Apr 30, 06:05 UTC | May 1, 05:00 UTC | 22h 55m |
| 2026-04-29 | NWC9152 | - | Apr 29, 18:40 UTC | Apr 30, 12:25 UTC | 17h 45m |
| 2026-04-29 | NWC9152 | - | Apr 29, 14:25 UTC | Apr 30, 12:25 UTC | 22h 0m |
| 2026-04-29 | NWC9158 | - | Apr 29, 12:45 UTC | Apr 30, 11:00 UTC | 22h 14m |
| 2026-04-29 | NWC9158 | - | Apr 29, 07:45 UTC | Apr 30, 06:45 UTC | 23h 0m |
| 2026-04-29 | NWC9158 | - | Apr 29, 02:15 UTC | Apr 29, 20:10 UTC | 17h 56m |
| 2026-04-28 | NWC9152 | - | Apr 28, 13:05 UTC | Apr 29, 12:45 UTC | 23h 40m |
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-73028 page for operator, model, and routing details .