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
- 56
- Distinct callsigns
- 18
- Country
- RU
- Last broadcast
- 21h 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 18 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| UTA783 | UTair Aviation | 10 | 2026-05-28 |
| UTA784 | UTair Aviation | 8 | 2026-05-28 |
| UTA810 | UTair Aviation | 6 | 2026-05-19 |
| UTA728 | UTair Aviation | 6 | 2026-05-29 |
| 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 |
| UTA810B | - | 2 | 2026-05-11 |
| UTA786 | UTair Aviation | 2 | 2026-05-12 |
| UTA812 | UTair Aviation | 1 | 2026-04-28 |
| UTA809 | UTair Aviation | 1 | 2026-04-29 |
| UTA785 | UTair Aviation | 1 | 2026-05-12 |
| UTA727 | UTair Aviation | 1 | 2026-05-29 |
| UTA400 | UTair Aviation | 1 | 2026-04-21 |
| UTA374 | UTair Aviation | 1 | 2026-05-17 |
| UTA296 | - | 1 | 2026-04-14 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 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 |
| 2026-05-23 | UTA783 | VKO → AYT | May 23, 10:35 UTC | May 23, 11:25 UTC | 50m |
| 2026-05-22 | UTA784 | AYT → VKO | May 22, 14:50 UTC | May 23, 11:25 UTC | 20h 34m |
| 2026-05-22 | UTA783 | VKO → AYT | May 22, 12:50 UTC | May 22, 13:10 UTC | 20m |
| 2026-05-22 | UTA783 | VKO → AYT | May 22, 11:35 UTC | May 22, 12:00 UTC | 25m |
| 2026-05-19 | UTA810 | SKD → VKO | May 19, 21:00 UTC | May 19, 21:10 UTC | 10m |
| 2026-05-18 | UTA728 | TLV → KUF | May 18, 08:01 UTC | May 18, 08:10 UTC | 10m |
| 2026-05-17 | UTA374 | MRV → VKO | May 17, 15:45 UTC | May 17, 16:01 UTC | 15m |
| 2026-05-16 | UTA810 | SKD → VKO | May 16, 20:00 UTC | May 16, 20:15 UTC | 15m |
| 2026-05-16 | UTA808 | BHK → VKO | May 16, 08:01 UTC | May 16, 08:20 UTC | 20m |
| 2026-05-14 | UTA784 | AYT → VKO | May 14, 18:00 UTC | May 14, 18:25 UTC | 25m |
| 2026-05-14 | UTA784 | AYT → VKO | May 14, 14:15 UTC | May 14, 16:30 UTC | 2h 15m |
| 2026-05-14 | UTA783 | VKO → AYT | May 14, 12:25 UTC | May 14, 12:45 UTC | 20m |
| 2026-05-14 | UTA783 | VKO → AYT | May 14, 02:45 UTC | May 14, 11:35 UTC | 8h 50m |
| 2026-05-12 | UTA786 | EVN → VKO | May 12, 23:10 UTC | May 12, 23:40 UTC | 30m |
| 2026-05-12 | UTA785 | VKO → EVN | May 12, 20:55 UTC | May 12, 21:10 UTC | 15m |
| 2026-05-11 | UTA810 | SKD → VKO | May 11, 07:55 UTC | May 11, 20:55 UTC | 13h 1m |
| 2026-05-11 | UTA810B | - | May 11, 01:15 UTC | May 11, 20:55 UTC | 19h 41m |
| 2026-05-10 | UTA810B | - | May 10, 18:49 UTC | May 11, 14:55 UTC | 20h 5m |
| 2026-05-10 | UTA810 | SKD → VKO | May 10, 14:54 UTC | May 11, 14:45 UTC | 23h 50m |
| 2026-05-10 | UTA806 | TAS → VKO | May 10, 01:14 UTC | May 10, 18:55 UTC | 17h 40m |
| 2026-05-09 | UTA806 | TAS → VKO | May 9, 18:25 UTC | May 10, 15:35 UTC | 21h 10m |
| 2026-05-09 | UTA806 | TAS → VKO | May 9, 04:00 UTC | May 10, 01:55 UTC | 21h 55m |
| 2026-05-02 | UTA728 | TLV → KUF | May 2, 07:40 UTC | May 3, 04:05 UTC | 20h 24m |
| 2026-05-01 | UTA810 | SKD → VKO | May 1, 14:40 UTC | May 2, 07:45 UTC | 17h 6m |
| 2026-05-01 | UTA810 | SKD → VKO | May 1, 08:00 UTC | May 1, 15:15 UTC | 7h 15m |
| 2026-04-29 | UTA809 | VKO → SKD | Apr 29, 08:05 UTC | Apr 29, 08:15 UTC | 10m |
| 2026-04-28 | UTA812 | AYT → TJM | Apr 28, 10:50 UTC | Apr 29, 08:15 UTC | 21h 25m |
| 2026-04-28 | UTA811 | TJM → AYT | Apr 28, 09:05 UTC | Apr 28, 09:15 UTC | 10m |
| 2026-04-27 | UTA811 | TJM → AYT | Apr 27, 23:00 UTC | Apr 28, 08:15 UTC | 9h 15m |
| 2026-04-27 | UTA811 | TJM → AYT | Apr 27, 09:35 UTC | Apr 28, 08:15 UTC | 22h 40m |
| 2026-04-27 | UTA454 | TJM → VKO | Apr 27, 03:00 UTC | Apr 27, 23:05 UTC | 20h 5m |
| 2026-04-26 | UTA454 | TJM → VKO | Apr 26, 07:40 UTC | Apr 27, 04:10 UTC | 20h 30m |
| 2026-04-26 | UTA875 | TJM → EVN | Apr 26, 04:30 UTC | Apr 26, 05:55 UTC | 1h 25m |
| 2026-04-25 | UTA875 | TJM → EVN | Apr 25, 08:05 UTC | Apr 26, 05:55 UTC | 21h 50m |
| 2026-04-25 | UTA875 | TJM → EVN | Apr 25, 04:50 UTC | Apr 26, 04:45 UTC | 23h 55m |
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 .