sensors Mode-S transponder
151F0E
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73486 · BOEING 737-800
- Hex
- 151F0E
- Octal
- 05217416
- Decimal
- 1,384,206
- Country
- RU
- Tail
- RA-73486
- Type
- B738
- Flights observed
- 49
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 16h ago
Last known position
Country allocation
The ICAO 24-bit address 151F0E 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 |
|---|---|---|---|
| UTA521 | UTair Aviation | 7 | 2026-06-23 |
| UTA435 | - | 5 | 2026-06-24 |
| UTA481 | UTair Aviation | 4 | 2026-05-19 |
| UTA296 | UTair Aviation | 4 | 2026-06-01 |
| UTA248 | - | 4 | 2026-07-19 |
| UTA543 | - | 3 | 2026-07-11 |
| UTA6136 | UTair Aviation | 2 | 2026-06-10 |
| UTA517 | UTair Aviation | 2 | 2026-06-05 |
| UTA511 | UTair Aviation | 2 | 2026-06-04 |
| UTA509 | UTair Aviation | 2 | 2026-06-03 |
| UTA464 | UTair Aviation | 2 | 2026-04-26 |
| UTA593 | UTair Aviation | 1 | 2026-05-09 |
| UTA572 | - | 1 | 2026-06-29 |
| UTA507 | - | 1 | 2026-07-11 |
| UTA482 | UTair Aviation | 1 | 2026-04-19 |
| UTA477 | - | 1 | 2026-04-12 |
| UTA434 | UTair Aviation | 1 | 2026-04-29 |
| UTA374 | UTair Aviation | 1 | 2026-04-23 |
| UTA373 | UTair Aviation | 1 | 2026-06-15 |
| UTA364 | UTair Aviation | 1 | 2026-06-08 |
Recent flights last 49
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-19 | UTA248 | - | Jul 19, 03:40 UTC | Jul 19, 04:00 UTC | 20m |
| 2026-07-11 | UTA507 | - | Jul 11, 07:50 UTC | Jul 11, 08:15 UTC | 25m |
| 2026-07-11 | UTA543 | - | Jul 11, 05:40 UTC | Jul 11, 05:55 UTC | 15m |
| 2026-07-11 | UTA543 | - | Jul 11, 04:35 UTC | Jul 11, 04:55 UTC | 20m |
| 2026-07-10 | UTA543 | - | Jul 10, 04:30 UTC | Jul 10, 05:05 UTC | 35m |
| 2026-06-29 | UTA572 | - | Jun 29, 22:24 UTC | Jun 30, 01:35 UTC | 3h 11m |
| 2026-06-25 | UTA248 | - | Jun 25, 03:40 UTC | Jun 25, 18:45 UTC | 15h 5m |
| 2026-06-24 | UTA435 | - | Jun 24, 09:34 UTC | Jun 25, 03:59 UTC | 18h 25m |
| 2026-06-24 | UTA435 | - | Jun 24, 09:00 UTC | Jun 25, 03:59 UTC | 19h 0m |
| 2026-06-23 | UTA435 | - | Jun 23, 09:34 UTC | Jun 24, 09:29 UTC | 23h 55m |
| 2026-06-23 | UTA521 | SGC → AER | Jun 23, 08:50 UTC | Jun 23, 09:54 UTC | 1h 5m |
| 2026-06-15 | UTA373 | VKO → MRV | Jun 15, 08:49 UTC | Jun 15, 09:10 UTC | 20m |
| 2026-06-10 | UTA6136 | IAA → VKO | Jun 10, 13:45 UTC | Jun 10, 15:10 UTC | 1h 25m |
| 2026-06-08 | UTA364 | UFA → VKO | Jun 8, 07:30 UTC | Jun 8, 20:35 UTC | 13h 5m |
| 2026-06-05 | UTA517 | NJC → AER | Jun 5, 17:50 UTC | Jun 6, 10:39 UTC | 16h 50m |
| 2026-06-05 | UTA517 | NJC → AER | Jun 5, 04:10 UTC | Jun 5, 18:55 UTC | 14h 45m |
| 2026-06-04 | UTA511 | SGC → AER | Jun 4, 18:50 UTC | Jun 5, 05:10 UTC | 10h 20m |
| 2026-06-04 | UTA511 | SGC → AER | Jun 4, 07:35 UTC | Jun 5, 05:10 UTC | 21h 35m |
| 2026-06-04 | UTA435 | SGC → KRR | Jun 4, 06:40 UTC | Jun 5, 05:10 UTC | 22h 30m |
| 2026-06-03 | UTA509 | TJM → MRV | Jun 3, 14:30 UTC | Jun 4, 07:45 UTC | 17h 15m |
| 2026-06-02 | UTA509 | TJM → MRV | Jun 2, 19:35 UTC | Jun 3, 15:40 UTC | 20h 5m |
| 2026-06-02 | UTA247 | VKO → SGC | Jun 2, 07:35 UTC | Jun 2, 20:05 UTC | 12h 30m |
| 2026-06-01 | UTA1453 | VKO → TJM | Jun 1, 20:05 UTC | Jun 2, 19:30 UTC | 23h 25m |
| 2026-06-01 | UTA296 | SGC → VKO | Jun 1, 14:50 UTC | Jun 2, 07:35 UTC | 16h 45m |
| 2026-06-01 | UTA296 | SGC → VKO | Jun 1, 10:05 UTC | Jun 2, 07:35 UTC | 21h 30m |
| 2026-06-01 | UTA295 | VKO → SGC | Jun 1, 09:15 UTC | Jun 1, 21:20 UTC | 12h 5m |
| 2026-05-27 | UTA6136 | IAA → VKO | May 27, 14:35 UTC | May 27, 16:05 UTC | 1h 30m |
| 2026-05-24 | UTA296 | SGC → VKO | May 24, 10:05 UTC | May 24, 23:46 UTC | 13h 41m |
| 2026-05-19 | UTA481 | SGC → MRV | May 19, 03:50 UTC | May 19, 04:50 UTC | 1h 0m |
| 2026-05-18 | UTA481 | SGC → MRV | May 18, 07:35 UTC | May 19, 04:50 UTC | 21h 14m |
| 2026-05-18 | UTA481 | SGC → MRV | May 18, 06:45 UTC | May 19, 04:50 UTC | 22h 4m |
| 2026-05-17 | UTA521 | SGC → AER | May 17, 23:50 UTC | May 18, 07:40 UTC | 7h 50m |
| 2026-05-15 | UTA248 | SGC → VKO | May 15, 03:30 UTC | May 15, 04:20 UTC | 50m |
| 2026-05-14 | UTA248 | SGC → VKO | May 14, 07:35 UTC | May 15, 04:20 UTC | 20h 45m |
| 2026-05-14 | UTA521 | SGC → AER | May 14, 06:45 UTC | May 15, 03:30 UTC | 20h 45m |
| 2026-05-13 | UTA521 | SGC → AER | May 13, 18:45 UTC | May 14, 07:45 UTC | 13h 0m |
| 2026-05-13 | UTA521 | SGC → AER | May 13, 07:35 UTC | May 14, 07:30 UTC | 23h 55m |
| 2026-05-13 | UTA521 | SGC → AER | May 13, 07:00 UTC | May 13, 18:50 UTC | 11h 50m |
| 2026-05-11 | UTA521 | SGC → AER | May 11, 11:45 UTC | May 12, 04:20 UTC | 16h 35m |
| 2026-05-09 | UTA481 | SGC → MRV | May 9, 20:00 UTC | May 10, 08:25 UTC | 12h 25m |
| 2026-05-09 | UTA593 | SGC → GRV | May 9, 07:35 UTC | May 10, 07:30 UTC | 23h 55m |
| 2026-05-09 | UTA435 | SGC → KRR | May 9, 06:25 UTC | May 9, 20:49 UTC | 14h 25m |
| 2026-05-03 | UTA296 | SGC → VKO | May 3, 18:20 UTC | May 3, 18:45 UTC | 25m |
| 2026-04-29 | UTA434 | KRR → TJM | Apr 29, 16:00 UTC | Apr 30, 14:40 UTC | 22h 39m |
| 2026-04-26 | UTA464 | TJM → VKO | Apr 26, 14:05 UTC | Apr 26, 14:40 UTC | 35m |
| 2026-04-23 | UTA374 | MRV → VKO | Apr 23, 12:01 UTC | Apr 23, 12:10 UTC | 10m |
| 2026-04-19 | UTA482 | MRV → SGC | Apr 19, 10:00 UTC | Apr 19, 10:10 UTC | 10m |
| 2026-04-16 | UTA464 | TJM → VKO | Apr 16, 13:35 UTC | Apr 16, 14:40 UTC | 1h 5m |
| 2026-04-12 | UTA477 | - | Apr 12, 18:15 UTC | Apr 12, 19:05 UTC | 50m |
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-73486 page for operator, model, and routing details .