sensors Mode-S transponder
151F17
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73495 · BOEING 737-800
- Hex
- 151F17
- Octal
- 05217427
- Decimal
- 1,384,215
- Country
- RU
- Tail
- RA-73495
- Type
- B738
- Flights observed
- 72
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 3d ago
Last known position
Country allocation
The ICAO 24-bit address 151F17 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 |
|---|---|---|---|
| UTA248 | - | 9 | 2026-06-16 |
| UTA464 | UTair Aviation | 5 | 2026-05-11 |
| UTA453 | UTair Aviation | 5 | 2026-06-06 |
| UTA521 | UTair Aviation | 4 | 2026-06-19 |
| UTA364 | UTair Aviation | 4 | 2026-05-19 |
| UTA561 | UTair Aviation | 3 | 2026-04-22 |
| UTA454 | UTair Aviation | 3 | 2026-04-21 |
| UTA358 | UTair Aviation | 3 | 2026-06-12 |
| UTA247 | UTair Aviation | 3 | 2026-05-21 |
| UTA6131 | - | 2 | 2026-05-22 |
| UTA560 | UTair Aviation | 2 | 2026-05-13 |
| UTA513 | UTair Aviation | 2 | 2026-06-22 |
| UTA481 | UTair Aviation | 2 | 2026-04-28 |
| UTA435 | - | 2 | 2026-07-11 |
| UTA400 | UTair Aviation | 2 | 2026-04-22 |
| UTA296 | UTair Aviation | 2 | 2026-05-26 |
| UTA276 | UTair Aviation | 2 | 2026-06-25 |
| UTA554 | - | 1 | 2026-06-27 |
| UTA518 | - | 1 | 2026-06-21 |
| UTA514 | UTair Aviation | 1 | 2026-06-24 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-11 | UTA435 | - | Jul 11, 07:45 UTC | Jul 11, 08:15 UTC | 30m |
| 2026-07-05 | UTA436 | - | Jul 5, 11:25 UTC | Jul 5, 11:35 UTC | 10m |
| 2026-07-03 | UTA275 | VKO → AER | Jul 3, 16:45 UTC | Jul 3, 17:10 UTC | 25m |
| 2026-07-02 | UTA507 | LED → KRR | Jul 2, 08:50 UTC | Jul 2, 09:10 UTC | 20m |
| 2026-06-27 | UTA554 | - | Jun 27, 16:59 UTC | Jun 27, 17:09 UTC | 10m |
| 2026-06-26 | - | - | Jun 26, 08:15 UTC | Jun 26, 08:24 UTC | 10m |
| 2026-06-25 | UTA276 | AER → VKO | Jun 25, 10:15 UTC | Jun 26, 08:24 UTC | 22h 10m |
| 2026-06-24 | UTA514 | AER → TJM | Jun 24, 08:39 UTC | Jun 24, 09:09 UTC | 30m |
| 2026-06-22 | UTA513 | TJM → AER | Jun 22, 07:45 UTC | Jun 22, 18:04 UTC | 10h 20m |
| 2026-06-21 | UTA518 | - | Jun 21, 14:24 UTC | Jun 22, 08:04 UTC | 17h 40m |
| 2026-06-19 | UTA276 | AER → VKO | Jun 19, 15:49 UTC | Jun 19, 16:04 UTC | 15m |
| 2026-06-19 | UTA521 | SGC → AER | Jun 19, 08:29 UTC | Jun 19, 12:44 UTC | 4h 15m |
| 2026-06-16 | UTA248 | - | Jun 16, 08:35 UTC | Jun 16, 13:30 UTC | 4h 55m |
| 2026-06-15 | UTA397 | VKO → GDZ | Jun 15, 08:45 UTC | Jun 15, 09:05 UTC | 20m |
| 2026-06-15 | UTA356 | GRV → VKO | Jun 15, 06:49 UTC | Jun 15, 07:05 UTC | 15m |
| 2026-06-14 | UTA355 | VKO → GRV | Jun 14, 20:25 UTC | Jun 15, 00:35 UTC | 4h 10m |
| 2026-06-14 | UTA248 | SGC → VKO | Jun 14, 03:30 UTC | Jun 14, 03:55 UTC | 25m |
| 2026-06-12 | UTA358 | KUF → VKO | Jun 12, 19:35 UTC | Jun 12, 19:45 UTC | 10m |
| 2026-06-10 | UTA399 | VKO → GRV | Jun 10, 19:00 UTC | Jun 10, 19:10 UTC | 10m |
| 2026-06-06 | UTA453 | VKO → TJM | Jun 6, 19:10 UTC | Jun 7, 06:35 UTC | 11h 25m |
| 2026-06-06 | UTA248 | SGC → VKO | Jun 6, 03:40 UTC | Jun 6, 19:30 UTC | 15h 50m |
| 2026-06-05 | UTA248 | SGC → VKO | Jun 5, 21:50 UTC | Jun 6, 19:30 UTC | 21h 40m |
| 2026-06-03 | UTA513 | TJM → AER | Jun 3, 15:55 UTC | Jun 4, 07:50 UTC | 15h 55m |
| 2026-06-02 | UTA453 | VKO → TJM | Jun 2, 19:20 UTC | Jun 3, 06:50 UTC | 11h 30m |
| 2026-06-02 | UTA453 | VKO → TJM | Jun 2, 03:25 UTC | Jun 2, 19:55 UTC | 16h 30m |
| 2026-05-29 | UTA363 | VKO → UFA | May 29, 23:25 UTC | May 30, 00:30 UTC | 1h 5m |
| 2026-05-27 | UTA358 | KUF → VKO | May 27, 17:25 UTC | May 27, 19:35 UTC | 2h 10m |
| 2026-05-26 | UTA296 | SGC → VKO | May 26, 02:29 UTC | May 26, 15:09 UTC | 12h 40m |
| 2026-05-24 | UTA435 | SGC → KRR | May 24, 18:20 UTC | May 25, 08:15 UTC | 13h 55m |
| 2026-05-22 | UTA6131 | - | May 22, 04:50 UTC | May 22, 23:10 UTC | 18h 20m |
| 2026-05-22 | UTA6131 | - | May 22, 02:00 UTC | May 22, 23:10 UTC | 21h 10m |
| 2026-05-21 | UTA247 | VKO → SGC | May 21, 03:50 UTC | May 22, 02:15 UTC | 22h 25m |
| 2026-05-21 | UTA247 | VKO → SGC | May 21, 03:40 UTC | May 21, 04:20 UTC | 40m |
| 2026-05-19 | UTA364 | UFA → VKO | May 19, 03:20 UTC | May 19, 15:35 UTC | 12h 15m |
| 2026-05-18 | UTA357 | VKO → KUF | May 18, 17:05 UTC | May 18, 17:15 UTC | 10m |
| 2026-05-18 | UTA248 | SGC → VKO | May 18, 04:51 UTC | May 18, 05:10 UTC | 20m |
| 2026-05-18 | UTA248 | SGC → VKO | May 18, 03:25 UTC | May 18, 04:05 UTC | 40m |
| 2026-05-17 | UTA521 | SGC → AER | May 17, 06:55 UTC | May 18, 03:45 UTC | 20h 50m |
| 2026-05-14 | UTA358 | KUF → VKO | May 14, 19:55 UTC | May 14, 21:10 UTC | 1h 15m |
| 2026-05-14 | UTA268 | AER → VKO | May 14, 12:05 UTC | May 14, 17:35 UTC | 5h 30m |
| 2026-05-14 | UTA267 | VKO → AER | May 14, 06:55 UTC | May 14, 09:50 UTC | 2h 55m |
| 2026-05-13 | UTA560 | MCX → VKO | May 13, 08:10 UTC | May 13, 21:25 UTC | 13h 15m |
| 2026-05-12 | UTA560 | MCX → VKO | May 12, 13:35 UTC | May 13, 08:35 UTC | 19h 0m |
| 2026-05-12 | UTA248 | SGC → VKO | May 12, 03:40 UTC | May 12, 05:30 UTC | 1h 50m |
| 2026-05-11 | UTA464 | TJM → VKO | May 11, 15:25 UTC | May 11, 15:50 UTC | 25m |
| 2026-05-11 | UTA464 | TJM → VKO | May 11, 00:05 UTC | May 11, 14:40 UTC | 14h 35m |
| 2026-05-08 | UTA248 | SGC → VKO | May 8, 03:55 UTC | May 8, 04:25 UTC | 30m |
| 2026-05-06 | UTA374 | MRV → VKO | May 6, 03:45 UTC | May 6, 17:45 UTC | 13h 59m |
| 2026-05-01 | UTA464 | TJM → VKO | May 1, 15:05 UTC | May 1, 15:30 UTC | 25m |
| 2026-05-01 | UTA464 | TJM → VKO | May 1, 13:55 UTC | May 1, 14:30 UTC | 35m |
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-73495 page for operator, model, and routing details .