sensors Mode-S transponder
151D56
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73046 · BOEING 737-500
- Hex
- 151D56
- Octal
- 05216526
- Decimal
- 1,383,766
- Country
- RU
- Tail
- RA-73046
- Type
- B735
- Flights observed
- 192
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 14h ago
Last known position
Country allocation
The ICAO 24-bit address 151D56 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 |
|---|---|---|---|
| UTA180 | UTair Aviation | 13 | 2026-06-05 |
| UTA743 | UTair Aviation | 12 | 2026-06-06 |
| UTA744 | UTair Aviation | 11 | 2026-06-06 |
| UTA375 | UTair Aviation | 11 | 2026-06-09 |
| UTA596 | UTair Aviation | 10 | 2026-06-11 |
| UTA595 | UTair Aviation | 10 | 2026-06-11 |
| UTA334 | UTair Aviation | 10 | 2026-06-10 |
| UTA333 | UTair Aviation | 9 | 2026-06-10 |
| UTA376 | UTair Aviation | 7 | 2026-06-09 |
| UTA445 | - | 6 | 2026-07-12 |
| UTA352 | - | 6 | 2026-06-12 |
| UTA179 | UTair Aviation | 6 | 2026-06-07 |
| UTA573 | UTair Aviation | 4 | 2026-05-28 |
| UTA398 | UTair Aviation | 4 | 2026-06-12 |
| UTA397 | UTair Aviation | 4 | 2026-06-12 |
| UTA6578 | - | 3 | 2026-07-12 |
| UTA6474 | - | 3 | 2026-06-19 |
| UTA456 | UTair Aviation | 3 | 2026-06-05 |
| UTA454 | - | 3 | 2026-06-14 |
| UTA446 | - | 3 | 2026-07-11 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | UTA186 | NUX → UFA | Jul 13, 08:30 UTC | Jul 13, 13:15 UTC | 4h 45m |
| 2026-07-12 | UTA6578 | - | Jul 12, 16:25 UTC | Jul 13, 13:15 UTC | 20h 50m |
| 2026-07-12 | UTA445 | - | Jul 12, 11:35 UTC | Jul 13, 08:30 UTC | 20h 55m |
| 2026-07-12 | UTA445 | - | Jul 12, 10:30 UTC | Jul 12, 10:50 UTC | 20m |
| 2026-07-11 | UTA446 | - | Jul 11, 15:05 UTC | Jul 12, 07:05 UTC | 16h 0m |
| 2026-07-10 | UTA415 | - | Jul 10, 17:55 UTC | Jul 11, 15:05 UTC | 21h 10m |
| 2026-07-10 | UTA111 | - | Jul 10, 03:45 UTC | Jul 10, 03:55 UTC | 10m |
| 2026-07-08 | UTA371 | - | Jul 8, 20:10 UTC | Jul 9, 12:00 UTC | 15h 50m |
| 2026-07-08 | UTA371 | - | Jul 8, 13:45 UTC | Jul 9, 11:00 UTC | 21h 15m |
| 2026-07-05 | UTA824 | - | Jul 5, 08:35 UTC | Jul 5, 15:15 UTC | 6h 40m |
| 2026-06-20 | UTA6432 | SGC → VKO | Jun 20, 23:34 UTC | Jun 21, 22:15 UTC | 22h 40m |
| 2026-06-20 | UTA6432 | SGC → VKO | Jun 20, 23:10 UTC | Jun 21, 00:34 UTC | 1h 25m |
| 2026-06-20 | UTA6431 | VKO → SGC | Jun 20, 20:05 UTC | Jun 20, 21:44 UTC | 1h 40m |
| 2026-06-19 | UTA6430 | - | Jun 19, 20:29 UTC | Jun 19, 21:54 UTC | 1h 25m |
| 2026-06-19 | UTA6473 | TLK → SGC | Jun 19, 06:24 UTC | Jun 19, 19:04 UTC | 12h 40m |
| 2026-06-19 | UTA6474 | - | Jun 19, 03:39 UTC | Jun 19, 04:14 UTC | 35m |
| 2026-06-18 | UTA6474 | - | Jun 18, 08:55 UTC | Jun 19, 04:14 UTC | 19h 19m |
| 2026-06-17 | UTA6578 | KGP → UFA | Jun 17, 16:20 UTC | Jun 18, 09:00 UTC | 16h 40m |
| 2026-06-17 | UTA445 | - | Jun 17, 11:00 UTC | Jun 18, 09:00 UTC | 22h 0m |
| 2026-06-15 | UTA576F | - | Jun 15, 16:30 UTC | Jun 15, 19:39 UTC | 3h 10m |
| 2026-06-14 | UTA575 | VKO → KRR | Jun 14, 11:00 UTC | Jun 14, 14:15 UTC | 3h 15m |
| 2026-06-14 | UTA575 | VKO → KRR | Jun 14, 07:30 UTC | Jun 14, 09:50 UTC | 2h 20m |
| 2026-06-14 | UTA454 | - | Jun 14, 02:45 UTC | Jun 14, 04:50 UTC | 2h 5m |
| 2026-06-13 | UTA454 | - | Jun 13, 07:35 UTC | Jun 14, 04:50 UTC | 21h 15m |
| 2026-06-13 | UTA454 | - | Jun 13, 07:20 UTC | Jun 14, 04:50 UTC | 21h 30m |
| 2026-06-12 | UTA352 | - | Jun 12, 18:10 UTC | Jun 13, 05:30 UTC | 11h 19m |
| 2026-06-12 | UTA398 | GDZ → VKO | Jun 12, 12:50 UTC | Jun 12, 16:20 UTC | 3h 30m |
| 2026-06-12 | UTA397 | VKO → GDZ | Jun 12, 08:00 UTC | Jun 12, 11:05 UTC | 3h 5m |
| 2026-06-11 | UTA352 | HMA → VKO | Jun 11, 18:10 UTC | Jun 12, 05:30 UTC | 11h 20m |
| 2026-06-11 | UTA596 | USK → VKO | Jun 11, 12:10 UTC | Jun 11, 14:35 UTC | 2h 25m |
| 2026-06-11 | UTA595 | VKO → USK | Jun 11, 08:35 UTC | Jun 11, 10:45 UTC | 2h 10m |
| 2026-06-11 | UTA1250 | AER → VKO | Jun 11, 01:15 UTC | Jun 11, 04:15 UTC | 3h 0m |
| 2026-06-10 | UTA1249 | VKO → AER | Jun 10, 20:10 UTC | Jun 10, 23:15 UTC | 3h 5m |
| 2026-06-10 | UTA18 | - | Jun 10, 13:25 UTC | Jun 10, 18:25 UTC | 5h 0m |
| 2026-06-10 | UTA334 | NNM → VKO | Jun 10, 09:15 UTC | Jun 10, 11:30 UTC | 2h 15m |
| 2026-06-10 | UTA333 | VKO → NNM | Jun 10, 05:25 UTC | Jun 10, 07:35 UTC | 2h 10m |
| 2026-06-09 | UTA376 | SCW → VKO | Jun 9, 20:55 UTC | Jun 9, 21:25 UTC | 30m |
| 2026-06-09 | UTA375 | VKO → SCW | Jun 9, 17:00 UTC | Jun 9, 19:35 UTC | 2h 35m |
| 2026-06-08 | UTA352 | HMA → VKO | Jun 8, 18:00 UTC | Jun 9, 05:45 UTC | 11h 45m |
| 2026-06-08 | UTA596 | USK → VKO | Jun 8, 12:00 UTC | Jun 8, 14:20 UTC | 2h 20m |
| 2026-06-08 | UTA595 | VKO → USK | Jun 8, 08:00 UTC | Jun 8, 10:15 UTC | 2h 15m |
| 2026-06-07 | UTA179 | VKO → UCT | Jun 7, 15:15 UTC | Jun 7, 20:05 UTC | 4h 50m |
| 2026-06-07 | UTA334 | NNM → VKO | Jun 7, 11:50 UTC | Jun 7, 13:50 UTC | 2h 0m |
| 2026-06-07 | UTA333 | VKO → NNM | Jun 7, 08:05 UTC | Jun 7, 10:15 UTC | 2h 10m |
| 2026-06-07 | UTA764 | NAJ → VKO | Jun 7, 03:30 UTC | Jun 7, 06:20 UTC | 2h 50m |
| 2026-06-07 | UTA763 | VKO → NAJ | Jun 7, 01:20 UTC | Jun 7, 01:40 UTC | 20m |
| 2026-06-06 | UTA763 | VKO → NAJ | Jun 6, 14:20 UTC | Jun 6, 18:14 UTC | 3h 55m |
| 2026-06-06 | UTA744 | KVD → VKO | Jun 6, 08:05 UTC | Jun 6, 11:09 UTC | 3h 5m |
| 2026-06-06 | UTA743 | VKO → KVD | Jun 6, 03:05 UTC | Jun 6, 05:45 UTC | 2h 40m |
| 2026-06-05 | UTA180 | UCT → VKO | Jun 5, 18:15 UTC | Jun 5, 23:45 UTC | 5h 30m |
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-73046 page for operator, model, and routing details .