sensors Mode-S transponder
151D7E
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-730896 · BOEING 737-800
- Hex
- 151D7E
- Octal
- 05216576
- Decimal
- 1,383,806
- Country
- RU
- Tail
- RA-730896
- Type
- B738
- Flights observed
- 62
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address 151D7E 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 |
|---|---|---|---|
| UTA469 | - | 17 | 2026-07-11 |
| UTA731 | - | 5 | 2026-07-11 |
| UTA786 | - | 4 | 2026-07-06 |
| UTA810 | - | 3 | 2026-06-16 |
| UTA785 | - | 3 | 2026-07-05 |
| UTA742 | UTair Aviation | 3 | 2026-06-28 |
| UTA732 | UTair Aviation | 3 | 2026-07-03 |
| UTA806 | - | 2 | 2026-04-13 |
| UTA783 | UTair Aviation | 2 | 2026-06-25 |
| UTA741 | UTair Aviation | 2 | 2026-06-28 |
| UTA727 | - | 2 | 2026-07-10 |
| UTA572 | - | 2 | 2026-06-14 |
| UTA470 | - | 2 | 2026-07-03 |
| UTA358 | UTair Aviation | 2 | 2026-04-14 |
| UTA881 | UTair Aviation | 1 | 2026-06-07 |
| UTA805 | - | 1 | 2026-04-12 |
| UTA784 | UTair Aviation | 1 | 2026-06-25 |
| UTA745 | - | 1 | 2026-04-14 |
| UTA730 | - | 1 | 2026-07-12 |
| UTA729 | UTair Aviation | 1 | 2026-07-12 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-12 | UTA730 | - | Jul 12, 20:25 UTC | Jul 12, 20:55 UTC | 30m |
| 2026-07-12 | UTA729 | UFA → IST | Jul 12, 18:15 UTC | Jul 12, 18:35 UTC | 20m |
| 2026-07-11 | UTA731 | - | Jul 11, 08:30 UTC | Jul 11, 08:50 UTC | 20m |
| 2026-07-11 | UTA469 | - | Jul 11, 04:35 UTC | Jul 11, 05:40 UTC | 1h 5m |
| 2026-07-10 | UTA469 | - | Jul 10, 07:50 UTC | Jul 11, 05:40 UTC | 21h 50m |
| 2026-07-10 | UTA727 | - | Jul 10, 05:35 UTC | Jul 10, 05:55 UTC | 20m |
| 2026-07-08 | UTA571 | - | Jul 8, 21:55 UTC | Jul 9, 01:10 UTC | 3h 15m |
| 2026-07-06 | UTA786 | - | Jul 6, 23:50 UTC | Jul 7, 00:20 UTC | 30m |
| 2026-07-05 | UTA786 | - | Jul 5, 23:15 UTC | Jul 5, 23:45 UTC | 30m |
| 2026-07-05 | UTA785 | - | Jul 5, 20:45 UTC | Jul 5, 21:00 UTC | 15m |
| 2026-07-03 | UTA470 | - | Jul 3, 21:00 UTC | Jul 3, 21:10 UTC | 10m |
| 2026-07-03 | UTA732 | GYD → LED | Jul 3, 17:25 UTC | Jul 3, 17:35 UTC | 10m |
| 2026-07-03 | UTA731 | - | Jul 3, 08:35 UTC | Jul 3, 08:55 UTC | 20m |
| 2026-07-03 | UTA469 | - | Jul 3, 03:40 UTC | Jul 3, 05:15 UTC | 1h 35m |
| 2026-07-02 | UTA469 | - | Jul 2, 03:40 UTC | Jul 2, 04:00 UTC | 20m |
| 2026-07-01 | UTA469 | - | Jul 1, 03:50 UTC | Jul 1, 06:05 UTC | 2h 15m |
| 2026-06-30 | UTA732 | GYD → LED | Jun 30, 16:45 UTC | Jun 30, 16:55 UTC | 10m |
| 2026-06-29 | UTA469 | - | Jun 29, 19:29 UTC | Jun 30, 05:05 UTC | 9h 36m |
| 2026-06-28 | UTA742 | AYT → GRV | Jun 28, 08:19 UTC | Jun 28, 10:04 UTC | 1h 45m |
| 2026-06-28 | UTA741 | GRV → AYT | Jun 28, 05:34 UTC | Jun 28, 06:10 UTC | 35m |
| 2026-06-25 | UTA784 | AYT → VKO | Jun 25, 14:14 UTC | Jun 25, 15:59 UTC | 1h 45m |
| 2026-06-25 | UTA783 | VKO → AYT | Jun 25, 12:04 UTC | Jun 25, 12:35 UTC | 30m |
| 2026-06-24 | UTA783 | VKO → AYT | Jun 24, 14:45 UTC | Jun 25, 12:35 UTC | 21h 50m |
| 2026-06-20 | UTA728 | - | Jun 20, 02:24 UTC | Jun 20, 02:54 UTC | 30m |
| 2026-06-19 | UTA727 | KUF → TLV | Jun 19, 07:29 UTC | Jun 19, 07:45 UTC | 15m |
| 2026-06-18 | UTA786 | - | Jun 18, 06:10 UTC | Jun 18, 06:40 UTC | 30m |
| 2026-06-18 | UTA785 | - | Jun 18, 03:45 UTC | Jun 18, 04:00 UTC | 15m |
| 2026-06-16 | UTA786 | EVN → VKO | Jun 16, 23:00 UTC | Jun 16, 23:25 UTC | 25m |
| 2026-06-16 | UTA785 | - | Jun 16, 20:35 UTC | Jun 16, 21:00 UTC | 25m |
| 2026-06-16 | UTA810 | - | Jun 16, 00:45 UTC | Jun 16, 21:00 UTC | 20h 16m |
| 2026-06-15 | UTA810 | - | Jun 15, 08:40 UTC | Jun 16, 01:30 UTC | 16h 50m |
| 2026-06-15 | UTA810 | - | Jun 15, 01:35 UTC | Jun 16, 01:30 UTC | 23h 55m |
| 2026-06-14 | UTA572 | - | Jun 14, 22:20 UTC | Jun 15, 09:00 UTC | 10h 40m |
| 2026-06-14 | UTA742 | AYT → GRV | Jun 14, 09:35 UTC | Jun 15, 09:00 UTC | 23h 25m |
| 2026-06-14 | UTA742 | AYT → GRV | Jun 14, 08:35 UTC | Jun 15, 01:35 UTC | 16h 59m |
| 2026-06-14 | UTA741 | GRV → AYT | Jun 14, 06:00 UTC | Jun 14, 06:30 UTC | 30m |
| 2026-06-13 | UTA572 | - | Jun 13, 01:20 UTC | Jun 13, 01:55 UTC | 35m |
| 2026-06-11 | UTA469 | SGC → LED | Jun 11, 03:35 UTC | Jun 11, 22:30 UTC | 18h 55m |
| 2026-06-10 | UTA469 | SGC → LED | Jun 10, 14:10 UTC | Jun 11, 05:00 UTC | 14h 50m |
| 2026-06-10 | UTA731 | LED → GYD | Jun 10, 08:30 UTC | Jun 10, 08:45 UTC | 15m |
| 2026-06-10 | UTA469 | SGC → LED | Jun 10, 05:35 UTC | Jun 10, 05:50 UTC | 15m |
| 2026-06-08 | UTA469 | SGC → LED | Jun 8, 21:45 UTC | Jun 9, 05:10 UTC | 7h 25m |
| 2026-06-08 | UTA469 | SGC → LED | Jun 8, 03:35 UTC | Jun 8, 10:30 UTC | 6h 55m |
| 2026-06-07 | UTA881 | LED → SKD | Jun 7, 09:35 UTC | Jun 7, 10:00 UTC | 25m |
| 2026-06-06 | UTA469 | SGC → LED | Jun 6, 14:30 UTC | Jun 7, 06:40 UTC | 16h 10m |
| 2026-06-06 | UTA731 | LED → GYD | Jun 6, 12:35 UTC | Jun 6, 12:54 UTC | 20m |
| 2026-06-06 | UTA469 | SGC → LED | Jun 6, 10:25 UTC | Jun 6, 10:45 UTC | 20m |
| 2026-06-06 | UTA469 | SGC → LED | Jun 6, 08:35 UTC | Jun 6, 09:55 UTC | 1h 20m |
| 2026-06-04 | UTA470 | LED → SGC | Jun 4, 00:45 UTC | Jun 4, 00:55 UTC | 10m |
| 2026-06-03 | UTA732 | GYD → LED | Jun 3, 19:50 UTC | Jun 3, 20:45 UTC | 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-730896 page for operator, model, and routing details .