sensors Mode-S transponder
151D83
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73091 · BOEING 737-800
- Hex
- 151D83
- Octal
- 05216603
- Decimal
- 1,383,811
- Country
- RU
- Tail
- RA-73091
- Type
- B738
- Flights observed
- 91
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 151D83 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 |
|---|---|---|---|
| UTA783 | UTair Aviation | 10 | 2026-05-28 |
| UTA469 | - | 9 | 2026-07-12 |
| UTA784 | UTair Aviation | 8 | 2026-05-28 |
| UTA728 | - | 7 | 2026-07-08 |
| UTA810 | UTair Aviation | 6 | 2026-05-19 |
| UTA738 | - | 4 | 2026-07-13 |
| UTA737 | - | 4 | 2026-07-12 |
| UTA882 | UTair Aviation | 3 | 2026-06-04 |
| UTA875 | UTair Aviation | 3 | 2026-04-26 |
| UTA811 | UTair Aviation | 3 | 2026-04-28 |
| UTA808 | UTair Aviation | 3 | 2026-05-25 |
| UTA806 | UTair Aviation | 3 | 2026-05-10 |
| UTA454 | UTair Aviation | 3 | 2026-04-27 |
| UTA296 | UTair Aviation | 3 | 2026-06-05 |
| UTA810B | - | 2 | 2026-05-11 |
| UTA786 | UTair Aviation | 2 | 2026-05-12 |
| UTA727 | - | 2 | 2026-07-08 |
| UTA881 | UTair Aviation | 1 | 2026-06-04 |
| UTA812 | UTair Aviation | 1 | 2026-04-28 |
| UTA809 | UTair Aviation | 1 | 2026-04-29 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | UTA738 | - | Jul 13, 11:25 UTC | Jul 13, 13:10 UTC | 1h 45m |
| 2026-07-12 | UTA737 | - | Jul 12, 22:40 UTC | Jul 13, 09:00 UTC | 10h 20m |
| 2026-07-12 | UTA469 | - | Jul 12, 04:50 UTC | Jul 12, 22:55 UTC | 18h 5m |
| 2026-07-12 | UTA469 | - | Jul 12, 03:45 UTC | Jul 12, 22:55 UTC | 19h 10m |
| 2026-07-08 | UTA728 | - | Jul 8, 09:20 UTC | Jul 8, 09:45 UTC | 25m |
| 2026-07-08 | UTA727 | - | Jul 8, 07:20 UTC | Jul 8, 07:30 UTC | 10m |
| 2026-07-06 | UTA469 | - | Jul 6, 03:45 UTC | Jul 6, 22:45 UTC | 19h 0m |
| 2026-06-29 | UTA469 | - | Jun 29, 04:20 UTC | Jun 29, 04:50 UTC | 30m |
| 2026-06-28 | UTA469 | - | Jun 28, 08:25 UTC | Jun 29, 04:50 UTC | 20h 25m |
| 2026-06-28 | UTA469 | - | Jun 28, 04:15 UTC | Jun 28, 05:04 UTC | 50m |
| 2026-06-24 | UTA6135 | - | Jun 24, 01:19 UTC | Jun 24, 12:09 UTC | 10h 50m |
| 2026-06-22 | UTA738 | AYT → SGC | Jun 22, 10:15 UTC | Jun 22, 12:05 UTC | 1h 50m |
| 2026-06-21 | UTA737 | SGC → AYT | Jun 21, 14:40 UTC | Jun 22, 08:40 UTC | 18h 0m |
| 2026-06-17 | UTA435 | SGC → KRR | Jun 17, 11:00 UTC | Jun 17, 11:35 UTC | 35m |
| 2026-06-15 | UTA738 | AYT → SGC | Jun 15, 21:50 UTC | Jun 15, 23:45 UTC | 1h 55m |
| 2026-06-15 | UTA737 | SGC → AYT | Jun 15, 01:55 UTC | Jun 15, 20:25 UTC | 18h 30m |
| 2026-06-14 | UTA737 | SGC → AYT | Jun 14, 19:20 UTC | Jun 15, 18:45 UTC | 23h 24m |
| 2026-06-14 | UTA469 | - | Jun 14, 13:10 UTC | Jun 15, 02:10 UTC | 12h 59m |
| 2026-06-13 | UTA481 | SGC → MRV | Jun 13, 04:10 UTC | Jun 13, 05:10 UTC | 1h 0m |
| 2026-06-10 | UTA513 | TJM → AER | Jun 10, 16:55 UTC | Jun 10, 18:05 UTC | 1h 10m |
| 2026-06-08 | UTA738 | AYT → SGC | Jun 8, 09:45 UTC | Jun 8, 12:30 UTC | 2h 45m |
| 2026-06-07 | UTA730 | IST → UFA | Jun 7, 14:20 UTC | Jun 8, 08:10 UTC | 17h 50m |
| 2026-06-07 | UTA729 | UFA → IST | Jun 7, 12:00 UTC | Jun 7, 12:30 UTC | 30m |
| 2026-06-05 | UTA296 | SGC → VKO | Jun 5, 03:40 UTC | Jun 5, 21:40 UTC | 18h 0m |
| 2026-06-04 | UTA296 | SGC → VKO | Jun 4, 21:50 UTC | Jun 5, 16:25 UTC | 18h 35m |
| 2026-06-04 | UTA882 | SKD → LED | Jun 4, 16:55 UTC | Jun 5, 16:25 UTC | 23h 30m |
| 2026-06-04 | UTA882 | SKD → LED | Jun 4, 10:10 UTC | Jun 5, 04:05 UTC | 17h 55m |
| 2026-06-04 | UTA881 | LED → SKD | Jun 4, 08:25 UTC | Jun 4, 08:45 UTC | 20m |
| 2026-06-04 | UTA469 | SGC → LED | Jun 4, 03:50 UTC | Jun 4, 05:10 UTC | 1h 20m |
| 2026-06-01 | UTA882 | SKD → LED | Jun 1, 17:10 UTC | Jun 2, 14:10 UTC | 21h 0m |
| 2026-06-01 | UTA469 | SGC → LED | Jun 1, 03:30 UTC | Jun 1, 17:40 UTC | 14h 10m |
| 2026-05-31 | UTA247 | VKO → SGC | May 31, 18:15 UTC | May 31, 18:35 UTC | 20m |
| 2026-05-30 | UTA464 | TJM → VKO | May 30, 18:00 UTC | May 31, 13:40 UTC | 19h 40m |
| 2026-05-30 | UTA742 | AYT → GRV | May 30, 07:40 UTC | May 30, 18:00 UTC | 10h 20m |
| 2026-05-30 | UTA741 | GRV → AYT | May 30, 05:00 UTC | May 30, 05:30 UTC | 30m |
| 2026-05-29 | UTA728 | TLV → KUF | May 29, 07:35 UTC | May 29, 08:00 UTC | 25m |
| 2026-05-29 | UTA727 | KUF → TLV | May 29, 05:45 UTC | May 29, 06:10 UTC | 25m |
| 2026-05-28 | UTA784 | AYT → VKO | May 28, 14:05 UTC | May 28, 16:00 UTC | 1h 55m |
| 2026-05-28 | UTA783 | VKO → AYT | May 28, 12:10 UTC | May 28, 12:30 UTC | 20m |
| 2026-05-27 | UTA728 | TLV → KUF | May 27, 08:30 UTC | May 27, 17:50 UTC | 9h 20m |
| 2026-05-26 | UTA784 | AYT → VKO | May 26, 16:50 UTC | May 26, 18:55 UTC | 2h 5m |
| 2026-05-26 | UTA783 | VKO → AYT | May 26, 11:44 UTC | May 26, 12:00 UTC | 15m |
| 2026-05-25 | UTA808 | BHK → VKO | May 25, 21:30 UTC | May 26, 11:05 UTC | 13h 35m |
| 2026-05-25 | UTA808 | BHK → VKO | May 25, 10:35 UTC | May 26, 04:15 UTC | 17h 40m |
| 2026-05-24 | UTA784 | AYT → VKO | May 24, 15:20 UTC | May 25, 10:40 UTC | 19h 20m |
| 2026-05-24 | UTA784 | AYT → VKO | May 24, 14:20 UTC | May 25, 10:40 UTC | 20h 20m |
| 2026-05-24 | UTA783 | VKO → AYT | May 24, 11:50 UTC | May 24, 12:05 UTC | 15m |
| 2026-05-24 | UTA783 | VKO → AYT | May 24, 10:40 UTC | May 24, 11:10 UTC | 30m |
| 2026-05-23 | UTA784 | AYT → VKO | May 23, 14:55 UTC | May 24, 11:10 UTC | 20h 15m |
| 2026-05-23 | UTA783 | VKO → AYT | May 23, 12:10 UTC | May 23, 12:40 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-73091 page for operator, model, and routing details .