sensors Mode-S transponder
151D54
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73044 · BOEING 737-500
- Hex
- 151D54
- Octal
- 05216524
- Decimal
- 1,383,764
- Country
- RU
- Tail
- RA-73044
- Type
- B735
- Flights observed
- 50
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 20d ago
Last known position
Country allocation
The ICAO 24-bit address 151D54 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 |
|---|---|---|---|
| UTA6149 | UTair Aviation | 4 | 2026-05-22 |
| UTA9045 | - | 3 | 2026-07-13 |
| UTA6429 | UTair Aviation | 3 | 2026-06-08 |
| UTA590 | UTair Aviation | 3 | 2026-06-15 |
| UTA589 | - | 3 | 2026-06-14 |
| UTA9046 | - | 2 | 2026-07-14 |
| UTA6428 | UTair Aviation | 2 | 2026-07-05 |
| UTA6427 | - | 2 | 2026-07-05 |
| UTA6150 | - | 2 | 2026-05-23 |
| UTA6130 | - | 2 | 2026-05-13 |
| UTA6129 | - | 2 | 2026-05-23 |
| UTA446 | - | 2 | 2026-06-28 |
| UTA445 | - | 2 | 2026-06-28 |
| UTA411 | UTair Aviation | 2 | 2026-07-08 |
| UTA186B | - | 2 | 2026-06-28 |
| UTA1404 | UTair Aviation | 2 | 2026-07-21 |
| UTA9042 | UTair Aviation | 1 | 2026-06-30 |
| UTA6489 | UTair Aviation | 1 | 2026-07-17 |
| UTA6471 | UTair Aviation | 1 | 2026-06-05 |
| UTA6430 | - | 1 | 2026-07-17 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-22 | UTA1426 | UFA → SGC | Jul 22, 00:10 UTC | Jul 22, 03:15 UTC | 3h 5m |
| 2026-07-21 | UTA1404 | UFA → SGC | Jul 21, 02:30 UTC | Jul 22, 00:10 UTC | 21h 40m |
| 2026-07-20 | UTA1404 | UFA → SGC | Jul 20, 16:25 UTC | Jul 21, 02:35 UTC | 10h 9m |
| 2026-07-19 | UTA184 | KZN → SGC | Jul 19, 09:00 UTC | Jul 19, 21:35 UTC | 12h 35m |
| 2026-07-19 | UTA183 | SGC → KZN | Jul 19, 06:40 UTC | Jul 19, 07:00 UTC | 20m |
| 2026-07-17 | UTA6430 | - | Jul 17, 20:44 UTC | Jul 17, 21:50 UTC | 1h 5m |
| 2026-07-17 | UTA6489 | VKO → KUF | Jul 17, 03:20 UTC | Jul 17, 18:55 UTC | 15h 35m |
| 2026-07-14 | UTA9046 | - | Jul 14, 19:25 UTC | Jul 15, 00:30 UTC | 5h 4m |
| 2026-07-13 | UTA9045 | - | Jul 13, 06:15 UTC | Jul 13, 09:20 UTC | 3h 5m |
| 2026-07-08 | UTA411 | SGC → KUF | Jul 8, 18:50 UTC | Jul 9, 05:20 UTC | 10h 30m |
| 2026-07-08 | UTA411 | SGC → KUF | Jul 8, 03:05 UTC | Jul 9, 02:20 UTC | 23h 15m |
| 2026-07-06 | UTA409 | - | Jul 6, 23:25 UTC | Jul 7, 02:30 UTC | 3h 5m |
| 2026-07-05 | UTA6428 | SGC → UFA | Jul 5, 16:25 UTC | Jul 5, 21:35 UTC | 5h 10m |
| 2026-07-05 | UTA6427 | - | Jul 5, 04:10 UTC | Jul 5, 05:45 UTC | 1h 35m |
| 2026-07-03 | UTA9046 | - | Jul 3, 16:20 UTC | Jul 3, 18:45 UTC | 2h 25m |
| 2026-07-01 | UTA9045 | - | Jul 1, 16:50 UTC | Jul 2, 10:55 UTC | 18h 5m |
| 2026-07-01 | UTA9045 | - | Jul 1, 12:35 UTC | Jul 2, 10:55 UTC | 22h 20m |
| 2026-06-30 | UTA9042 | BTK → UFA | Jun 30, 18:10 UTC | Jul 1, 16:50 UTC | 22h 40m |
| 2026-06-28 | UTA186B | - | Jun 28, 16:19 UTC | Jun 29, 09:25 UTC | 17h 5m |
| 2026-06-28 | UTA186B | - | Jun 28, 11:35 UTC | Jun 29, 09:25 UTC | 21h 50m |
| 2026-06-28 | UTA445 | - | Jun 28, 10:24 UTC | Jun 29, 06:29 UTC | 20h 5m |
| 2026-06-28 | UTA446 | - | Jun 28, 05:45 UTC | Jun 28, 06:59 UTC | 1h 15m |
| 2026-06-26 | UTA445 | - | Jun 26, 10:25 UTC | Jun 27, 01:04 UTC | 14h 40m |
| 2026-06-26 | UTA446 | - | Jun 26, 01:05 UTC | Jun 26, 07:20 UTC | 6h 15m |
| 2026-06-25 | UTA103 | - | Jun 25, 04:20 UTC | Jun 26, 01:05 UTC | 20h 45m |
| 2026-06-24 | UTA436B | - | Jun 24, 11:50 UTC | Jun 25, 04:25 UTC | 16h 35m |
| 2026-06-24 | UTA435B | - | Jun 24, 07:54 UTC | Jun 24, 09:49 UTC | 1h 55m |
| 2026-06-15 | UTA590 | GDZ → TJM | Jun 15, 08:40 UTC | Jun 15, 08:49 UTC | 10m |
| 2026-06-14 | UTA589 | - | Jun 14, 13:40 UTC | Jun 14, 14:25 UTC | 45m |
| 2026-06-13 | UTA589 | - | Jun 13, 18:20 UTC | Jun 14, 14:25 UTC | 20h 5m |
| 2026-06-13 | UTA464 | TJM → VKO | Jun 13, 13:35 UTC | Jun 13, 15:30 UTC | 1h 55m |
| 2026-06-12 | UTA590 | GDZ → TJM | Jun 12, 17:05 UTC | Jun 13, 15:30 UTC | 22h 24m |
| 2026-06-12 | UTA590 | GDZ → TJM | Jun 12, 16:20 UTC | Jun 13, 15:00 UTC | 22h 39m |
| 2026-06-12 | UTA589 | - | Jun 12, 11:20 UTC | Jun 12, 14:45 UTC | 3h 25m |
| 2026-06-08 | UTA6429 | SGC → GSV | Jun 8, 16:50 UTC | Jun 8, 17:50 UTC | 1h 0m |
| 2026-06-08 | UTA6429 | SGC → GSV | Jun 8, 13:55 UTC | Jun 8, 15:20 UTC | 1h 25m |
| 2026-06-07 | UTA6429 | SGC → GSV | Jun 7, 17:15 UTC | Jun 8, 15:20 UTC | 22h 5m |
| 2026-06-07 | UTA6428 | SGC → UFA | Jun 7, 16:35 UTC | Jun 8, 15:00 UTC | 22h 25m |
| 2026-06-07 | UTA6427 | UFA → SGC | Jun 7, 04:10 UTC | Jun 7, 05:35 UTC | 1h 25m |
| 2026-06-05 | UTA6471 | OMS → TLK | Jun 5, 22:05 UTC | Jun 5, 22:35 UTC | 30m |
| 2026-05-23 | UTA6150 | - | May 23, 10:35 UTC | May 23, 11:00 UTC | 25m |
| 2026-05-23 | UTA6129 | - | May 23, 00:00 UTC | May 23, 09:45 UTC | 9h 44m |
| 2026-05-22 | UTA6149 | KJA → TOF | May 22, 22:25 UTC | May 22, 22:55 UTC | 30m |
| 2026-05-13 | UTA6150 | - | May 13, 23:20 UTC | May 13, 23:45 UTC | 25m |
| 2026-05-13 | UTA6130 | - | May 13, 09:40 UTC | May 13, 10:00 UTC | 20m |
| 2026-05-13 | UTA6129 | - | May 13, 00:00 UTC | May 13, 00:20 UTC | 20m |
| 2026-05-12 | UTA6149 | KJA → TOF | May 12, 22:15 UTC | May 12, 23:01 UTC | 45m |
| 2026-04-20 | UTA6130 | - | Apr 20, 10:35 UTC | Apr 20, 11:00 UTC | 25m |
| 2026-04-20 | UTA6149 | KJA → TOF | Apr 20, 00:30 UTC | Apr 20, 09:45 UTC | 9h 15m |
| 2026-04-19 | UTA6149 | KJA → TOF | Apr 19, 22:55 UTC | Apr 19, 23:30 UTC | 35m |
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-73044 page for operator, model, and routing details .