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
- 67
- 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 |
|---|---|---|---|
| UTA750 | - | 6 | 2026-07-12 |
| UTA282 | UTair Aviation | 4 | 2026-06-08 |
| UTA183 | UTair Aviation | 4 | 2026-05-30 |
| UTA414 | UTair Aviation | 3 | 2026-05-28 |
| UTA413 | - | 3 | 2026-06-25 |
| UTA1403 | UTair Aviation | 3 | 2026-06-26 |
| UTA6490 | - | 2 | 2026-07-06 |
| UTA6422 | UTair Aviation | 2 | 2026-06-03 |
| UTA478 | UTair Aviation | 2 | 2026-04-28 |
| UTA418 | UTair Aviation | 2 | 2026-04-19 |
| UTA372 | - | 2 | 2026-07-02 |
| UTA111 | - | 2 | 2026-06-14 |
| UTA6494 | UTair Aviation | 1 | 2026-04-27 |
| 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 |
| UTA6429 | UTair Aviation | 1 | 2026-07-06 |
| UTA6424 | UTair Aviation | 1 | 2026-06-04 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-12 | UTA750 | - | Jul 12, 15:30 UTC | Jul 12, 22:30 UTC | 7h 0m |
| 2026-07-06 | UTA6490 | - | Jul 6, 17:15 UTC | Jul 6, 18:45 UTC | 1h 30m |
| 2026-07-06 | UTA6429 | SGC → GSV | Jul 6, 15:25 UTC | Jul 6, 16:05 UTC | 40m |
| 2026-07-02 | UTA372 | - | Jul 2, 06:35 UTC | Jul 2, 12:25 UTC | 5h 50m |
| 2026-07-01 | UTA372 | - | Jul 1, 14:55 UTC | Jul 2, 12:25 UTC | 21h 30m |
| 2026-07-01 | UTA750 | GYD → TJM | Jul 1, 10:15 UTC | Jul 1, 10:40 UTC | 25m |
| 2026-06-26 | UTA1403 | SGC → UFA | Jun 26, 06:25 UTC | Jun 26, 20:50 UTC | 14h 25m |
| 2026-06-25 | UTA1403 | SGC → UFA | Jun 25, 22:54 UTC | Jun 26, 20:50 UTC | 21h 55m |
| 2026-06-25 | UTA1403 | SGC → UFA | Jun 25, 19:20 UTC | Jun 26, 17:15 UTC | 21h 55m |
| 2026-06-25 | UTA413 | - | Jun 25, 11:39 UTC | Jun 26, 08:54 UTC | 21h 15m |
| 2026-06-25 | UTA1427 | SGC → UFA | Jun 25, 02:10 UTC | Jun 25, 19:20 UTC | 17h 10m |
| 2026-06-24 | UTA750 | GYD → TJM | Jun 24, 11:05 UTC | Jun 25, 02:14 UTC | 15h 10m |
| 2026-06-23 | UTA750 | GYD → TJM | Jun 23, 20:34 UTC | Jun 24, 12:44 UTC | 16h 10m |
| 2026-06-23 | UTA750 | GYD → TJM | Jun 23, 16:54 UTC | Jun 24, 12:44 UTC | 19h 50m |
| 2026-06-23 | UTA750 | GYD → TJM | Jun 23, 11:45 UTC | Jun 24, 11:14 UTC | 23h 30m |
| 2026-06-21 | UTA408 | UFA → SGC | Jun 21, 21:44 UTC | Jun 22, 00:24 UTC | 2h 40m |
| 2026-06-19 | UTA403 | SGC → UFA | Jun 19, 08:44 UTC | Jun 19, 18:30 UTC | 9h 45m |
| 2026-06-17 | UTA434 | - | Jun 17, 18:50 UTC | Jun 18, 08:00 UTC | 13h 10m |
| 2026-06-17 | UTA433 | TJM → KRR | Jun 17, 03:45 UTC | Jun 17, 16:35 UTC | 12h 50m |
| 2026-06-15 | UTA421 | - | Jun 15, 19:55 UTC | Jun 16, 00:35 UTC | 4h 40m |
| 2026-06-14 | UTA111 | - | Jun 14, 03:25 UTC | Jun 14, 03:45 UTC | 20m |
| 2026-06-08 | UTA282 | KUF → SVX | Jun 8, 17:45 UTC | Jun 8, 18:05 UTC | 20m |
| 2026-06-07 | UTA282 | KUF → SVX | Jun 7, 07:55 UTC | Jun 7, 10:40 UTC | 2h 45m |
| 2026-06-06 | UTA282 | KUF → SVX | Jun 6, 10:20 UTC | Jun 6, 10:39 UTC | 20m |
| 2026-06-04 | UTA6424 | GSV → SGC | Jun 4, 19:50 UTC | Jun 5, 08:30 UTC | 12h 40m |
| 2026-06-04 | UTA6423 | SGC → GSV | Jun 4, 16:15 UTC | Jun 4, 17:45 UTC | 1h 30m |
| 2026-06-03 | UTA6422 | SGC → IJK | Jun 3, 17:30 UTC | Jun 4, 17:15 UTC | 23h 45m |
| 2026-06-03 | UTA6422 | SGC → IJK | Jun 3, 14:00 UTC | Jun 3, 18:15 UTC | 4h 15m |
| 2026-05-31 | UTA184 | KZN → SGC | May 31, 21:00 UTC | Jun 1, 10:25 UTC | 13h 25m |
| 2026-05-30 | UTA183 | SGC → KZN | May 30, 23:20 UTC | May 31, 18:50 UTC | 19h 30m |
| 2026-05-30 | UTA183 | SGC → KZN | May 30, 22:30 UTC | May 31, 18:50 UTC | 20h 20m |
| 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 |
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 .