sensors Mode-S transponder
151F1A
ICAO 24-bit transponder address · allocated to Russia
- Hex
- 151F1A
- Octal
- 05217432
- Decimal
- 1,384,218
- Country
- RU
- Flights observed
- 62
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 13h ago
Last known position
Country allocation
The ICAO 24-bit address 151F1A 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 |
|---|---|---|---|
| UTA507 | UTair Aviation | 6 | 2026-06-30 |
| UTA373 | UTair Aviation | 5 | 2026-07-20 |
| UTA572 | UTair Aviation | 3 | 2026-05-16 |
| UTA543 | UTair Aviation | 3 | 2026-07-17 |
| UTA454 | - | 3 | 2026-06-13 |
| UTA453 | UTair Aviation | 3 | 2026-05-25 |
| UTA355 | - | 3 | 2026-07-05 |
| UTA296 | - | 3 | 2026-07-03 |
| UTA9026 | - | 2 | 2026-07-21 |
| UTA511 | UTair Aviation | 2 | 2026-07-15 |
| UTA358 | UTair Aviation | 2 | 2026-05-31 |
| UTA270 | - | 2 | 2026-06-20 |
| UTA249 | UTair Aviation | 2 | 2026-04-23 |
| UTA247 | - | 2 | 2026-06-22 |
| UTA802G | - | 1 | 2026-05-03 |
| UTA6132 | UTair Aviation | 1 | 2026-06-06 |
| UTA590 | UTair Aviation | 1 | 2026-07-23 |
| UTA576 | UTair Aviation | 1 | 2026-05-18 |
| UTA544F | - | 1 | 2026-07-01 |
| UTA544 | UTair Aviation | 1 | 2026-06-04 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-23 | UTA590 | GDZ → TJM | Jul 23, 10:30 UTC | Jul 23, 10:50 UTC | 20m |
| 2026-07-21 | UTA9026 | - | Jul 21, 08:25 UTC | Jul 21, 14:55 UTC | 6h 30m |
| 2026-07-20 | UTA9026 | - | Jul 20, 17:15 UTC | Jul 21, 14:55 UTC | 21h 39m |
| 2026-07-20 | UTA373 | VKO → MRV | Jul 20, 10:10 UTC | Jul 20, 10:20 UTC | 10m |
| 2026-07-17 | UTA543 | TJM → LED | Jul 17, 13:55 UTC | Jul 18, 05:20 UTC | 15h 26m |
| 2026-07-17 | UTA543 | TJM → LED | Jul 17, 04:39 UTC | Jul 17, 14:15 UTC | 9h 35m |
| 2026-07-15 | UTA511 | SGC → AER | Jul 15, 11:45 UTC | Jul 15, 12:25 UTC | 40m |
| 2026-07-14 | UTA435 | - | Jul 14, 14:05 UTC | Jul 14, 14:50 UTC | 45m |
| 2026-07-13 | UTA1514 | - | Jul 13, 11:35 UTC | Jul 13, 11:50 UTC | 15m |
| 2026-07-05 | UTA355 | - | Jul 5, 17:05 UTC | Jul 5, 23:45 UTC | 6h 40m |
| 2026-07-03 | UTA296 | - | Jul 3, 16:00 UTC | Jul 3, 16:35 UTC | 35m |
| 2026-07-03 | UTA296 | - | Jul 3, 10:05 UTC | Jul 3, 15:10 UTC | 5h 5m |
| 2026-07-01 | UTA544F | LED → LED | Jul 1, 11:35 UTC | Jul 1, 12:00 UTC | 25m |
| 2026-06-30 | UTA507 | LED → KRR | Jun 30, 12:25 UTC | Jun 30, 12:45 UTC | 20m |
| 2026-06-27 | UTA507 | LED → KRR | Jun 27, 17:20 UTC | Jun 27, 17:44 UTC | 25m |
| 2026-06-26 | UTA248 | - | Jun 26, 03:34 UTC | Jun 26, 04:04 UTC | 30m |
| 2026-06-22 | UTA247 | - | Jun 22, 18:09 UTC | Jun 22, 19:19 UTC | 1h 10m |
| 2026-06-20 | UTA270 | - | Jun 20, 21:49 UTC | Jun 20, 22:14 UTC | 25m |
| 2026-06-19 | UTA517 | NJC → AER | Jun 19, 23:44 UTC | Jun 20, 00:04 UTC | 20m |
| 2026-06-14 | UTA511 | SGC → AER | Jun 14, 19:40 UTC | Jun 15, 06:30 UTC | 10h 50m |
| 2026-06-13 | UTA363 | VKO → UFA | Jun 13, 21:10 UTC | Jun 14, 19:40 UTC | 22h 30m |
| 2026-06-13 | UTA295 | VKO → SGC | Jun 13, 09:00 UTC | Jun 13, 09:25 UTC | 25m |
| 2026-06-13 | UTA454 | - | Jun 13, 04:00 UTC | Jun 13, 04:35 UTC | 35m |
| 2026-06-12 | UTA270 | - | Jun 12, 11:25 UTC | Jun 12, 12:05 UTC | 40m |
| 2026-06-11 | UTA507 | LED → KRR | Jun 11, 12:35 UTC | Jun 11, 13:00 UTC | 25m |
| 2026-06-11 | UTA507 | LED → KRR | Jun 11, 09:05 UTC | Jun 11, 10:15 UTC | 1h 10m |
| 2026-06-10 | UTA291 | LED → GDZ | Jun 10, 11:55 UTC | Jun 10, 12:20 UTC | 25m |
| 2026-06-08 | UTA507 | LED → KRR | Jun 8, 09:30 UTC | Jun 8, 09:50 UTC | 20m |
| 2026-06-06 | UTA6132 | SGC → VKO | Jun 6, 21:30 UTC | Jun 6, 22:00 UTC | 30m |
| 2026-06-05 | UTA373 | VKO → MRV | Jun 5, 11:40 UTC | Jun 5, 12:00 UTC | 20m |
| 2026-06-05 | UTA454 | TJM → VKO | Jun 5, 09:10 UTC | Jun 5, 09:20 UTC | 10m |
| 2026-06-04 | UTA544 | LED → TJM | Jun 4, 19:10 UTC | Jun 4, 21:00 UTC | 1h 50m |
| 2026-06-03 | UTA507 | LED → KRR | Jun 3, 19:05 UTC | Jun 4, 11:45 UTC | 16h 40m |
| 2026-06-03 | UTA543 | TJM → LED | Jun 3, 08:50 UTC | Jun 3, 09:05 UTC | 15m |
| 2026-05-31 | UTA358 | KUF → VKO | May 31, 19:30 UTC | May 31, 20:35 UTC | 1h 5m |
| 2026-05-31 | UTA373 | VKO → MRV | May 31, 10:00 UTC | May 31, 10:25 UTC | 25m |
| 2026-05-30 | UTA247 | VKO → SGC | May 30, 18:15 UTC | May 30, 18:40 UTC | 25m |
| 2026-05-30 | UTA364 | UFA → VKO | May 30, 04:00 UTC | May 30, 10:45 UTC | 6h 45m |
| 2026-05-26 | UTA358 | KUF → VKO | May 26, 19:25 UTC | May 26, 23:29 UTC | 4h 5m |
| 2026-05-25 | UTA453 | VKO → TJM | May 25, 18:10 UTC | May 26, 04:04 UTC | 9h 54m |
| 2026-05-24 | UTA454 | TJM → VKO | May 24, 02:40 UTC | May 24, 03:50 UTC | 1h 10m |
| 2026-05-22 | UTA453 | VKO → TJM | May 22, 19:25 UTC | May 23, 08:35 UTC | 13h 9m |
| 2026-05-21 | UTA453 | VKO → TJM | May 21, 22:15 UTC | May 22, 20:00 UTC | 21h 45m |
| 2026-05-18 | UTA576 | KRR → VKO | May 18, 15:45 UTC | May 18, 16:05 UTC | 20m |
| 2026-05-17 | UTA355 | VKO → GRV | May 17, 00:30 UTC | May 17, 00:45 UTC | 15m |
| 2026-05-16 | UTA355 | VKO → GRV | May 16, 04:35 UTC | May 17, 00:45 UTC | 20h 10m |
| 2026-05-16 | UTA572 | KJA → VKO | May 16, 03:50 UTC | May 17, 00:45 UTC | 20h 55m |
| 2026-05-13 | UTA373 | VKO → MRV | May 13, 16:15 UTC | May 13, 16:30 UTC | 15m |
| 2026-05-11 | UTA399 | VKO → GRV | May 11, 03:50 UTC | May 11, 18:50 UTC | 15h 0m |
| 2026-05-04 | UTA572 | KJA → VKO | May 4, 13:45 UTC | May 4, 14:10 UTC | 25m |
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.