sensors Mode-S transponder
151D55
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73045 · BOEING 737-500
- Hex
- 151D55
- Octal
- 05216525
- Decimal
- 1,383,765
- Country
- RU
- Tail
- RA-73045
- Type
- B735
- Flights observed
- 36
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 151D55 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 |
|---|---|---|---|
| UTA414 | UTair Aviation | 3 | 2026-05-28 |
| UTA478 | UTair Aviation | 2 | 2026-04-28 |
| UTA418 | UTair Aviation | 2 | 2026-04-19 |
| UTA413 | UTair Aviation | 2 | 2026-04-30 |
| UTA183 | UTair Aviation | 2 | 2026-04-26 |
| UTA6494 | UTair Aviation | 1 | 2026-04-27 |
| UTA6490 | UTair Aviation | 1 | 2026-04-25 |
| UTA6489 | UTair Aviation | 1 | 2026-04-24 |
| UTA6474 | - | 1 | 2026-04-24 |
| UTA6473 | UTair Aviation | 1 | 2026-04-24 |
| UTA6436 | UTair Aviation | 1 | 2026-04-27 |
| UTA6433 | UTair Aviation | 1 | 2026-04-26 |
| UTA6316 | - | 1 | 2026-05-18 |
| UTA6303 | - | 1 | 2026-05-22 |
| UTA6302 | - | 1 | 2026-05-22 |
| UTA6126 | UTair Aviation | 1 | 2026-04-13 |
| UTA454 | UTair Aviation | 1 | 2026-05-06 |
| UTA453 | UTair Aviation | 1 | 2026-05-06 |
| UTA419 | UTair Aviation | 1 | 2026-04-19 |
| UTA412 | - | 1 | 2026-04-15 |
Recent flights last 36
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | UTA195 | SVX → NUX | May 29, 06:05 UTC | May 29, 06:15 UTC | 10m |
| 2026-05-28 | UTA414 | KUF → SGC | May 28, 19:10 UTC | May 28, 23:05 UTC | 3h 55m |
| 2026-05-22 | UTA6303 | - | May 22, 21:05 UTC | May 22, 22:55 UTC | 1h 50m |
| 2026-05-22 | UTA6302 | - | May 22, 16:45 UTC | May 22, 18:50 UTC | 2h 5m |
| 2026-05-18 | UTA1453 | VKO → TJM | May 18, 20:20 UTC | May 18, 22:25 UTC | 2h 5m |
| 2026-05-18 | UTA6316 | - | May 18, 04:51 UTC | May 18, 19:05 UTC | 14h 14m |
| 2026-05-17 | UTA1464 | TJM → VKO | May 17, 16:01 UTC | May 17, 18:25 UTC | 2h 25m |
| 2026-05-06 | UTA453 | VKO → TJM | May 6, 17:50 UTC | May 6, 19:45 UTC | 1h 55m |
| 2026-05-06 | UTA334 | NNM → VKO | May 6, 10:10 UTC | May 6, 12:25 UTC | 2h 15m |
| 2026-05-06 | UTA333 | VKO → NNM | May 6, 06:35 UTC | May 6, 08:20 UTC | 1h 45m |
| 2026-05-06 | UTA454 | TJM → VKO | May 6, 02:50 UTC | May 6, 05:10 UTC | 2h 20m |
| 2026-04-30 | UTA414 | KUF → SGC | Apr 30, 22:20 UTC | May 1, 16:50 UTC | 18h 30m |
| 2026-04-30 | UTA413 | SGC → KUF | Apr 30, 20:05 UTC | May 1, 16:50 UTC | 20h 45m |
| 2026-04-29 | UTA282 | KUF → SVX | Apr 29, 12:40 UTC | Apr 29, 14:45 UTC | 2h 5m |
| 2026-04-28 | UTA478 | KUF → SGC | Apr 28, 18:20 UTC | Apr 28, 22:35 UTC | 4h 15m |
| 2026-04-27 | UTA6436 | KZN → SGC | Apr 27, 08:05 UTC | Apr 27, 09:00 UTC | 55m |
| 2026-04-27 | UTA6494 | GSV → KZN | Apr 27, 05:25 UTC | Apr 27, 05:50 UTC | 25m |
| 2026-04-26 | UTA6433 | SGC → GSV | Apr 26, 20:50 UTC | Apr 27, 04:15 UTC | 7h 25m |
| 2026-04-26 | UTA183 | SGC → KZN | Apr 26, 18:30 UTC | Apr 26, 19:00 UTC | 30m |
| 2026-04-25 | UTA183 | SGC → KZN | Apr 25, 22:20 UTC | Apr 26, 19:00 UTC | 20h 40m |
| 2026-04-25 | UTA6490 | KUF → VKO | Apr 25, 07:40 UTC | Apr 25, 22:20 UTC | 14h 40m |
| 2026-04-24 | UTA6489 | VKO → KUF | Apr 24, 17:55 UTC | Apr 25, 06:30 UTC | 12h 35m |
| 2026-04-24 | UTA6473 | TLK → SGC | Apr 24, 06:25 UTC | Apr 24, 18:00 UTC | 11h 35m |
| 2026-04-24 | UTA6474 | - | Apr 24, 03:50 UTC | Apr 24, 04:30 UTC | 40m |
| 2026-04-21 | UTA196 | NUX → SVX | Apr 21, 11:05 UTC | Apr 21, 11:15 UTC | 10m |
| 2026-04-21 | UTA111 | SGC → SVX | Apr 21, 03:35 UTC | Apr 21, 03:50 UTC | 15m |
| 2026-04-20 | UTA478 | KUF → SGC | Apr 20, 18:15 UTC | Apr 20, 22:35 UTC | 4h 20m |
| 2026-04-19 | UTA419 | SGC → KUF | Apr 19, 19:35 UTC | Apr 19, 23:05 UTC | 3h 30m |
| 2026-04-19 | UTA418 | KUF → SGC | Apr 19, 01:50 UTC | Apr 19, 23:05 UTC | 21h 15m |
| 2026-04-18 | UTA418 | KUF → SGC | Apr 18, 22:25 UTC | Apr 19, 19:40 UTC | 21h 15m |
| 2026-04-18 | UTA1407 | SGC → UFA | Apr 18, 08:50 UTC | Apr 19, 01:55 UTC | 17h 5m |
| 2026-04-16 | UTA414 | - | Apr 16, 22:15 UTC | Apr 16, 23:00 UTC | 45m |
| 2026-04-16 | UTA413 | - | Apr 16, 19:45 UTC | Apr 16, 19:55 UTC | 10m |
| 2026-04-15 | UTA412 | - | Apr 15, 21:45 UTC | Apr 15, 22:35 UTC | 50m |
| 2026-04-15 | UTA411 | - | Apr 15, 19:25 UTC | Apr 15, 19:35 UTC | 10m |
| 2026-04-13 | UTA6126 | NNM → UFA | Apr 13, 17:40 UTC | Apr 13, 19:10 UTC | 1h 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-73045 page for operator, model, and routing details .