sensors Mode-S transponder
151D4F
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73039 · BOEING 737-500
- Hex
- 151D4F
- Octal
- 05216517
- Decimal
- 1,383,759
- Country
- RU
- Tail
- RA-73039
- Type
- B735
- Flights observed
- 62
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 7h ago
Last known position
Country allocation
The ICAO 24-bit address 151D4F 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 |
|---|---|---|---|
| UTA446 | - | 10 | 2026-07-16 |
| UTA445 | UTair Aviation | 9 | 2026-07-17 |
| UTA371 | - | 3 | 2026-07-12 |
| UTA6421 | UTair Aviation | 2 | 2026-06-30 |
| UTA456 | UTair Aviation | 2 | 2026-06-29 |
| UTA356 | UTair Aviation | 2 | 2026-06-27 |
| UTA351 | - | 2 | 2026-06-28 |
| UTA9240 | - | 1 | 2026-06-17 |
| UTA73039 | - | 1 | 2026-06-07 |
| UTA6580 | UTair Aviation | 1 | 2026-04-23 |
| UTA6578 | - | 1 | 2026-04-17 |
| UTA6577 | - | 1 | 2026-07-16 |
| UTA6422 | UTair Aviation | 1 | 2026-07-01 |
| UTA6126 | UTair Aviation | 1 | 2026-04-19 |
| UTA6125 | UTair Aviation | 1 | 2026-04-18 |
| UTA596 | UTair Aviation | 1 | 2026-04-25 |
| UTA595 | UTair Aviation | 1 | 2026-04-25 |
| UTA576 | - | 1 | 2026-06-19 |
| UTA575 | UTair Aviation | 1 | 2026-06-19 |
| UTA463 | UTair Aviation | 1 | 2026-06-07 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | UTA445 | VKO → KGP | Jul 17, 10:35 UTC | Jul 17, 19:35 UTC | 9h 0m |
| 2026-07-16 | UTA446 | - | Jul 16, 16:19 UTC | Jul 17, 07:14 UTC | 14h 55m |
| 2026-07-16 | UTA6577 | - | Jul 16, 01:05 UTC | Jul 16, 16:19 UTC | 15h 15m |
| 2026-07-15 | UTA445 | - | Jul 15, 10:30 UTC | Jul 16, 01:10 UTC | 14h 40m |
| 2026-07-15 | UTA446 | - | Jul 15, 06:35 UTC | Jul 15, 07:05 UTC | 30m |
| 2026-07-14 | UTA446 | - | Jul 14, 17:30 UTC | Jul 15, 06:00 UTC | 12h 29m |
| 2026-07-12 | UTA371 | - | Jul 12, 20:15 UTC | Jul 13, 12:00 UTC | 15h 45m |
| 2026-07-10 | UTA1403 | - | Jul 10, 03:50 UTC | Jul 10, 19:20 UTC | 15h 30m |
| 2026-07-09 | UTA414 | - | Jul 9, 22:55 UTC | Jul 10, 19:20 UTC | 20h 25m |
| 2026-07-09 | UTA413 | - | Jul 9, 19:30 UTC | Jul 10, 03:55 UTC | 8h 25m |
| 2026-07-06 | UTA371 | - | Jul 6, 07:55 UTC | Jul 6, 11:30 UTC | 3h 35m |
| 2026-07-04 | UTA406 | - | Jul 4, 16:15 UTC | Jul 4, 20:10 UTC | 3h 55m |
| 2026-07-03 | UTA445 | - | Jul 3, 11:40 UTC | Jul 3, 11:55 UTC | 15m |
| 2026-07-03 | UTA445 | - | Jul 3, 10:45 UTC | Jul 3, 10:55 UTC | 10m |
| 2026-07-03 | UTA446 | - | Jul 3, 01:15 UTC | Jul 3, 07:35 UTC | 6h 20m |
| 2026-07-02 | UTA427 | SGC → UFA | Jul 2, 02:00 UTC | Jul 3, 01:20 UTC | 23h 20m |
| 2026-07-01 | UTA6422 | SGC → IJK | Jul 1, 17:35 UTC | Jul 2, 02:05 UTC | 8h 30m |
| 2026-06-30 | UTA6421 | SGC → GSV | Jun 30, 19:50 UTC | Jul 1, 16:20 UTC | 20h 30m |
| 2026-06-30 | UTA6421 | SGC → GSV | Jun 30, 19:35 UTC | Jul 1, 16:20 UTC | 20h 45m |
| 2026-06-29 | UTA352 | - | Jun 29, 17:59 UTC | Jun 30, 05:35 UTC | 11h 36m |
| 2026-06-29 | UTA456 | NOJ → VKO | Jun 29, 13:34 UTC | Jun 29, 15:04 UTC | 1h 30m |
| 2026-06-29 | UTA455 | - | Jun 29, 07:34 UTC | Jun 29, 07:44 UTC | 10m |
| 2026-06-28 | UTA351 | - | Jun 28, 17:55 UTC | Jun 29, 05:40 UTC | 11h 45m |
| 2026-06-27 | UTA356 | GRV → VKO | Jun 27, 21:34 UTC | Jun 28, 05:24 UTC | 7h 50m |
| 2026-06-26 | UTA356 | GRV → VKO | Jun 26, 20:34 UTC | Jun 27, 06:05 UTC | 9h 30m |
| 2026-06-20 | UTA250F | - | Jun 20, 06:35 UTC | Jun 20, 09:44 UTC | 3h 10m |
| 2026-06-20 | UTA249B | - | Jun 20, 01:05 UTC | Jun 20, 04:14 UTC | 3h 10m |
| 2026-06-19 | UTA576 | - | Jun 19, 12:44 UTC | Jun 19, 15:34 UTC | 2h 50m |
| 2026-06-19 | UTA575 | VKO → KRR | Jun 19, 07:25 UTC | Jun 19, 10:50 UTC | 3h 25m |
| 2026-06-18 | UTA364 | - | Jun 18, 17:21 UTC | Jun 19, 05:34 UTC | 12h 13m |
| 2026-06-17 | UTA9240 | - | Jun 17, 19:35 UTC | Jun 18, 17:21 UTC | 21h 46m |
| 2026-06-15 | UTA372 | MRV → DME | Jun 15, 22:05 UTC | Jun 16, 17:45 UTC | 19h 40m |
| 2026-06-15 | UTA371 | DME → MRV | Jun 15, 17:59 UTC | Jun 16, 17:45 UTC | 23h 45m |
| 2026-06-13 | UTA417 | SGC → KUF | Jun 13, 08:35 UTC | Jun 14, 02:05 UTC | 17h 30m |
| 2026-06-12 | UTA415 | - | Jun 12, 21:25 UTC | Jun 13, 11:15 UTC | 13h 49m |
| 2026-06-07 | UTA463 | VKO → TJM | Jun 7, 08:50 UTC | Jun 7, 10:25 UTC | 1h 35m |
| 2026-06-07 | UTA73039 | - | Jun 7, 05:40 UTC | Jun 7, 06:50 UTC | 1h 10m |
| 2026-04-26 | UTA398 | GDZ → VKO | Apr 26, 13:00 UTC | Apr 26, 15:55 UTC | 2h 55m |
| 2026-04-26 | UTA397 | VKO → GDZ | Apr 26, 08:00 UTC | Apr 26, 11:25 UTC | 3h 25m |
| 2026-04-25 | UTA376 | SCW → VKO | Apr 25, 23:55 UTC | Apr 26, 01:20 UTC | 1h 25m |
| 2026-04-25 | UTA375 | VKO → SCW | Apr 25, 17:05 UTC | Apr 25, 18:25 UTC | 1h 20m |
| 2026-04-25 | UTA596 | USK → VKO | Apr 25, 12:25 UTC | Apr 25, 14:45 UTC | 2h 20m |
| 2026-04-25 | UTA595 | VKO → USK | Apr 25, 08:15 UTC | Apr 25, 10:25 UTC | 2h 10m |
| 2026-04-24 | UTA445 | VKO → KGP | Apr 24, 10:30 UTC | Apr 25, 05:05 UTC | 18h 35m |
| 2026-04-23 | UTA446 | KGP → VKO | Apr 23, 16:45 UTC | Apr 24, 07:40 UTC | 14h 55m |
| 2026-04-23 | UTA6580 | KGP → KUF | Apr 23, 01:05 UTC | Apr 23, 17:10 UTC | 16h 5m |
| 2026-04-22 | UTA152 | NJC → UFA | Apr 22, 12:40 UTC | Apr 23, 01:10 UTC | 12h 30m |
| 2026-04-21 | UTA363 | VKO → UFA | Apr 21, 23:00 UTC | Apr 22, 17:05 UTC | 18h 5m |
| 2026-04-21 | UTA456 | - | Apr 21, 07:25 UTC | Apr 21, 15:10 UTC | 7h 45m |
| 2026-04-20 | UTA351 | VKO → HMA | Apr 20, 17:55 UTC | Apr 21, 05:40 UTC | 11h 45m |
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-73039 page for operator, model, and routing details .