sensors Mode-S transponder
151F15
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73493 · BOEING 737-800
- Hex
- 151F15
- Octal
- 05217425
- Decimal
- 1,384,213
- Country
- RU
- Tail
- RA-73493
- Type
- B738
- Flights observed
- 36
- Distinct callsigns
- 19
- Country
- RU
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address 151F15 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 19 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| UTA572 | UTair Aviation | 7 | 2026-06-03 |
| UTA571 | UTair Aviation | 3 | 2026-06-02 |
| UTA296 | UTair Aviation | 3 | 2026-05-23 |
| UTA248 | UTair Aviation | 3 | 2026-06-15 |
| UTA511 | UTair Aviation | 2 | 2026-06-08 |
| UTA464 | UTair Aviation | 2 | 2026-06-01 |
| UTA463 | UTair Aviation | 2 | 2026-05-26 |
| UTA435 | UTair Aviation | 2 | 2026-06-10 |
| UTA291 | UTair Aviation | 2 | 2026-05-24 |
| UTA6136 | UTair Aviation | 1 | 2026-05-11 |
| UTA6134 | UTair Aviation | 1 | 2026-05-19 |
| UTA6132 | UTair Aviation | 1 | 2026-06-20 |
| UTA521 | UTair Aviation | 1 | 2026-06-11 |
| UTA513 | UTair Aviation | 1 | 2026-06-04 |
| UTA477 | UTair Aviation | 1 | 2026-05-29 |
| UTA469 | UTair Aviation | 1 | 2026-05-03 |
| UTA416 | UTair Aviation | 1 | 2026-05-01 |
| UTA364 | UTair Aviation | 1 | 2026-05-17 |
| UTA295 | UTair Aviation | 1 | 2026-06-02 |
Recent flights last 36
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-20 | UTA6132 | SGC → VKO | Jun 20, 17:19 UTC | Jun 20, 17:44 UTC | 25m |
| 2026-06-15 | UTA248 | SGC → VKO | Jun 15, 03:40 UTC | Jun 15, 04:00 UTC | 20m |
| 2026-06-11 | UTA521 | SGC → AER | Jun 11, 13:30 UTC | Jun 11, 14:35 UTC | 1h 5m |
| 2026-06-10 | UTA435 | SGC → KRR | Jun 10, 06:35 UTC | Jun 10, 07:40 UTC | 1h 5m |
| 2026-06-08 | UTA511 | SGC → AER | Jun 8, 23:35 UTC | Jun 9, 11:20 UTC | 11h 45m |
| 2026-06-07 | UTA435 | SGC → KRR | Jun 7, 06:25 UTC | Jun 7, 19:55 UTC | 13h 30m |
| 2026-06-04 | UTA513 | TJM → AER | Jun 4, 07:30 UTC | Jun 4, 16:30 UTC | 9h 0m |
| 2026-06-03 | UTA511 | SGC → AER | Jun 3, 14:50 UTC | Jun 4, 05:15 UTC | 14h 25m |
| 2026-06-03 | UTA572 | KJA → VKO | Jun 3, 01:50 UTC | Jun 3, 19:50 UTC | 18h 0m |
| 2026-06-02 | UTA572 | KJA → VKO | Jun 2, 23:20 UTC | Jun 3, 19:50 UTC | 20h 30m |
| 2026-06-02 | UTA571 | VKO → KJA | Jun 2, 23:05 UTC | Jun 3, 19:50 UTC | 20h 45m |
| 2026-06-02 | UTA571 | VKO → KJA | Jun 2, 14:45 UTC | Jun 3, 02:25 UTC | 11h 40m |
| 2026-06-02 | UTA295 | VKO → SGC | Jun 2, 09:00 UTC | Jun 2, 09:25 UTC | 25m |
| 2026-06-01 | UTA464 | TJM → VKO | Jun 1, 15:05 UTC | Jun 1, 15:30 UTC | 25m |
| 2026-05-31 | UTA248 | SGC → VKO | May 31, 18:45 UTC | Jun 1, 04:05 UTC | 9h 20m |
| 2026-05-29 | UTA477 | SGC → KUF | May 29, 19:10 UTC | May 29, 22:00 UTC | 2h 50m |
| 2026-05-26 | UTA463 | VKO → TJM | May 26, 04:20 UTC | May 26, 08:54 UTC | 4h 35m |
| 2026-05-25 | UTA463 | VKO → TJM | May 25, 13:05 UTC | May 26, 08:54 UTC | 19h 49m |
| 2026-05-24 | UTA291 | LED → GDZ | May 24, 08:20 UTC | May 24, 09:30 UTC | 1h 10m |
| 2026-05-23 | UTA296 | SGC → VKO | May 23, 14:40 UTC | May 24, 04:15 UTC | 13h 36m |
| 2026-05-22 | UTA296 | SGC → VKO | May 22, 15:20 UTC | May 23, 15:15 UTC | 23h 54m |
| 2026-05-22 | UTA296 | SGC → VKO | May 22, 15:05 UTC | May 22, 15:40 UTC | 35m |
| 2026-05-20 | UTA572 | KJA → VKO | May 20, 20:15 UTC | May 21, 04:15 UTC | 8h 0m |
| 2026-05-19 | UTA6134 | MRV → VKO | May 19, 08:20 UTC | May 19, 09:20 UTC | 1h 0m |
| 2026-05-17 | UTA364 | UFA → VKO | May 17, 06:55 UTC | May 17, 07:25 UTC | 30m |
| 2026-05-12 | UTA572 | KJA → VKO | May 12, 22:05 UTC | May 13, 01:50 UTC | 3h 45m |
| 2026-05-12 | UTA571 | VKO → KJA | May 12, 19:00 UTC | May 12, 19:10 UTC | 10m |
| 2026-05-11 | UTA6136 | IAA → VKO | May 11, 12:10 UTC | May 11, 12:45 UTC | 35m |
| 2026-05-10 | UTA572 | KJA → VKO | May 10, 00:34 UTC | May 10, 17:34 UTC | 17h 0m |
| 2026-05-09 | UTA572 | KJA → VKO | May 9, 21:55 UTC | May 10, 17:34 UTC | 19h 40m |
| 2026-05-09 | UTA572 | KJA → VKO | May 9, 14:00 UTC | May 10, 03:55 UTC | 13h 55m |
| 2026-05-08 | UTA464 | TJM → VKO | May 8, 14:05 UTC | May 8, 14:50 UTC | 45m |
| 2026-05-07 | UTA248 | SGC → VKO | May 7, 13:55 UTC | May 7, 15:10 UTC | 1h 15m |
| 2026-05-03 | UTA291 | LED → GDZ | May 3, 11:15 UTC | May 3, 11:45 UTC | 30m |
| 2026-05-03 | UTA469 | SGC → LED | May 3, 07:40 UTC | May 3, 09:10 UTC | 1h 30m |
| 2026-05-01 | UTA416 | KUF → SGC | May 1, 20:40 UTC | May 1, 23:10 UTC | 2h 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-73493 page for operator, model, and routing details .