sensors Mode-S transponder
151F18
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73496 · BOEING 737-800
- Hex
- 151F18
- Octal
- 05217430
- Decimal
- 1,384,216
- Country
- RU
- Tail
- RA-73496
- Type
- B738
- Flights observed
- 66
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address 151F18 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 |
|---|---|---|---|
| UTA572 | - | 20 | 2026-07-14 |
| UTA571 | - | 5 | 2026-07-03 |
| UTA469 | UTair Aviation | 5 | 2026-05-28 |
| UTA435 | UTair Aviation | 5 | 2026-05-19 |
| VTA572 | - | 4 | 2026-04-24 |
| UTA515 | - | 3 | 2026-06-23 |
| UTA296 | UTair Aviation | 3 | 2026-05-11 |
| UTA9026 | - | 2 | 2026-07-16 |
| UTA454 | UTair Aviation | 2 | 2026-05-24 |
| UTA247 | - | 2 | 2026-07-15 |
| UTA544F | - | 1 | 2026-06-17 |
| UTA544B | - | 1 | 2026-06-18 |
| UTA522 | UTair Aviation | 1 | 2026-05-04 |
| UTA513 | UTair Aviation | 1 | 2026-06-07 |
| UTA478 | UTair Aviation | 1 | 2026-05-01 |
| UTA470 | UTair Aviation | 1 | 2026-05-28 |
| UTA463 | - | 1 | 2026-07-15 |
| UTA453 | - | 1 | 2026-04-12 |
| UTA373 | - | 1 | 2026-06-24 |
| UTA364 | UTair Aviation | 1 | 2026-05-26 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-16 | UTA9026 | - | Jul 16, 13:30 UTC | Jul 16, 19:30 UTC | 6h 0m |
| 2026-07-15 | UTA9026 | - | Jul 15, 19:35 UTC | Jul 16, 14:45 UTC | 19h 10m |
| 2026-07-15 | UTA247 | - | Jul 15, 18:35 UTC | Jul 15, 18:45 UTC | 10m |
| 2026-07-15 | UTA463 | - | Jul 15, 07:45 UTC | Jul 15, 07:55 UTC | 10m |
| 2026-07-14 | UTA572 | - | Jul 14, 20:10 UTC | Jul 15, 04:20 UTC | 8h 9m |
| 2026-07-04 | UTA247 | - | Jul 4, 00:05 UTC | Jul 4, 19:15 UTC | 19h 10m |
| 2026-07-03 | UTA571 | - | Jul 3, 23:40 UTC | Jul 4, 19:15 UTC | 19h 35m |
| 2026-06-28 | UTA572 | - | Jun 28, 22:10 UTC | Jun 29, 01:20 UTC | 3h 10m |
| 2026-06-28 | UTA572 | - | Jun 28, 00:55 UTC | Jun 28, 22:45 UTC | 21h 50m |
| 2026-06-27 | UTA572 | - | Jun 27, 09:40 UTC | Jun 28, 01:29 UTC | 15h 50m |
| 2026-06-24 | UTA373 | - | Jun 24, 09:00 UTC | Jun 24, 09:24 UTC | 25m |
| 2026-06-23 | UTA515 | - | Jun 23, 05:20 UTC | Jun 23, 06:24 UTC | 1h 5m |
| 2026-06-18 | UTA544B | - | Jun 18, 01:25 UTC | Jun 18, 01:40 UTC | 15m |
| 2026-06-17 | UTA544F | - | Jun 17, 15:20 UTC | Jun 17, 15:40 UTC | 20m |
| 2026-06-13 | UTA515 | TJM → AER | Jun 13, 07:25 UTC | Jun 13, 08:30 UTC | 1h 5m |
| 2026-06-09 | UTA515 | TJM → AER | Jun 9, 08:00 UTC | Jun 9, 09:00 UTC | 1h 0m |
| 2026-06-07 | UTA513 | TJM → AER | Jun 7, 17:35 UTC | Jun 7, 18:40 UTC | 1h 5m |
| 2026-06-03 | UTA248 | SGC → VKO | Jun 3, 03:35 UTC | Jun 3, 17:50 UTC | 14h 15m |
| 2026-05-29 | UTA572 | KJA → VKO | May 29, 22:15 UTC | May 30, 14:35 UTC | 16h 20m |
| 2026-05-29 | UTA571 | VKO → KJA | May 29, 19:10 UTC | May 30, 14:35 UTC | 19h 25m |
| 2026-05-29 | UTA571 | VKO → KJA | May 29, 10:05 UTC | May 30, 07:45 UTC | 21h 40m |
| 2026-05-29 | UTA571 | VKO → KJA | May 29, 09:55 UTC | May 30, 07:45 UTC | 21h 50m |
| 2026-05-28 | UTA295 | VKO → SGC | May 28, 22:05 UTC | May 29, 19:15 UTC | 21h 10m |
| 2026-05-28 | UTA470 | LED → SGC | May 28, 20:30 UTC | May 28, 20:55 UTC | 25m |
| 2026-05-28 | UTA469 | SGC → LED | May 28, 05:30 UTC | May 28, 05:40 UTC | 10m |
| 2026-05-28 | UTA469 | SGC → LED | May 28, 03:40 UTC | May 28, 04:55 UTC | 1h 15m |
| 2026-05-26 | UTA364 | UFA → VKO | May 26, 03:19 UTC | May 26, 03:55 UTC | 35m |
| 2026-05-24 | UTA454 | TJM → VKO | May 24, 19:20 UTC | May 25, 03:50 UTC | 8h 30m |
| 2026-05-24 | UTA572 | KJA → VKO | May 24, 00:50 UTC | May 24, 19:45 UTC | 18h 55m |
| 2026-05-23 | UTA571 | VKO → KJA | May 23, 22:05 UTC | May 24, 19:45 UTC | 21h 40m |
| 2026-05-22 | UTA454 | TJM → VKO | May 22, 03:10 UTC | May 22, 03:50 UTC | 40m |
| 2026-05-19 | UTA435 | SGC → KRR | May 19, 06:35 UTC | May 19, 22:10 UTC | 15h 35m |
| 2026-05-17 | UTA469 | SGC → LED | May 17, 04:25 UTC | May 17, 05:15 UTC | 50m |
| 2026-05-16 | UTA435 | SGC → KRR | May 16, 08:05 UTC | May 17, 05:15 UTC | 21h 9m |
| 2026-05-16 | UTA435 | SGC → KRR | May 16, 07:55 UTC | May 17, 05:15 UTC | 21h 19m |
| 2026-05-15 | UTA435 | SGC → KRR | May 15, 22:10 UTC | May 16, 08:55 UTC | 10h 46m |
| 2026-05-15 | UTA435 | SGC → KRR | May 15, 06:35 UTC | May 15, 22:15 UTC | 15h 39m |
| 2026-05-14 | UTA469 | SGC → LED | May 14, 03:45 UTC | May 14, 05:10 UTC | 1h 25m |
| 2026-05-13 | UTA469 | SGC → LED | May 13, 06:25 UTC | May 14, 05:10 UTC | 22h 45m |
| 2026-05-11 | UTA296 | SGC → VKO | May 11, 00:45 UTC | May 11, 01:10 UTC | 25m |
| 2026-05-09 | UTA358 | KUF → VKO | May 9, 22:55 UTC | May 9, 23:09 UTC | 15m |
| 2026-05-08 | UTA572 | KJA → VKO | May 8, 22:20 UTC | May 9, 14:30 UTC | 16h 10m |
| 2026-05-08 | UTA572 | KJA → VKO | May 8, 10:44 UTC | May 9, 04:30 UTC | 17h 45m |
| 2026-05-06 | UTA572 | KJA → VKO | May 6, 19:55 UTC | May 7, 01:40 UTC | 5h 45m |
| 2026-05-04 | UTA522 | AER → SGC | May 4, 10:15 UTC | May 4, 10:35 UTC | 20m |
| 2026-05-01 | UTA478 | KUF → SGC | May 1, 23:00 UTC | May 1, 23:15 UTC | 15m |
| 2026-04-27 | UTA296 | SGC → VKO | Apr 27, 15:50 UTC | Apr 27, 21:30 UTC | 5h 40m |
| 2026-04-24 | UTA296 | SGC → VKO | Apr 24, 14:30 UTC | Apr 25, 01:25 UTC | 10h 55m |
| 2026-04-24 | VTA572 | - | Apr 24, 04:20 UTC | Apr 25, 01:25 UTC | 21h 5m |
| 2026-04-24 | VTA572 | - | Apr 24, 02:05 UTC | Apr 25, 01:25 UTC | 23h 20m |
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-73496 page for operator, model, and routing details .