sensors Mode-S transponder
151D4D
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73037 · BOEING 737-500
- Hex
- 151D4D
- Octal
- 05216515
- Decimal
- 1,383,757
- Country
- RU
- Tail
- RA-73037
- Type
- B735
- Flights observed
- 99
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 6d ago
Last known position
Country allocation
The ICAO 24-bit address 151D4D 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 | UTair Aviation | 13 | 2026-06-03 |
| UTA445 | UTair Aviation | 9 | 2026-06-01 |
| UTA334 | UTair Aviation | 5 | 2026-06-05 |
| UTA333 | UTair Aviation | 5 | 2026-06-05 |
| UTA6126 | UTair Aviation | 4 | 2026-06-05 |
| UTA6125 | UTair Aviation | 4 | 2026-06-04 |
| UTA352 | UTair Aviation | 4 | 2026-05-13 |
| UTA180 | UTair Aviation | 4 | 2026-05-11 |
| UTA596 | UTair Aviation | 3 | 2026-05-12 |
| UTA595 | UTair Aviation | 3 | 2026-05-12 |
| UTA351 | UTair Aviation | 3 | 2026-05-06 |
| UTA9045 | - | 2 | 2026-07-17 |
| UTA6578 | UTair Aviation | 2 | 2026-05-29 |
| UTA574 | UTair Aviation | 2 | 2026-05-08 |
| UTA464 | UTair Aviation | 2 | 2026-05-14 |
| UTA417 | UTair Aviation | 2 | 2026-07-25 |
| UTA403 | UTair Aviation | 2 | 2026-05-22 |
| UTA376 | UTair Aviation | 2 | 2026-05-09 |
| UTA375 | UTair Aviation | 2 | 2026-05-09 |
| UTA151 | UTair Aviation | 2 | 2026-06-20 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-25 | UTA417 | SGC → KUF | Jul 25, 22:20 UTC | Jul 26, 20:15 UTC | 21h 56m |
| 2026-07-25 | UTA417 | SGC → KUF | Jul 25, 09:40 UTC | Jul 26, 01:55 UTC | 16h 15m |
| 2026-07-22 | UTA411 | SGC → KUF | Jul 22, 18:45 UTC | Jul 23, 08:30 UTC | 13h 45m |
| 2026-07-17 | UTA9045 | - | Jul 17, 18:10 UTC | Jul 17, 21:05 UTC | 2h 55m |
| 2026-07-16 | UTA9045 | - | Jul 16, 10:04 UTC | Jul 16, 10:45 UTC | 40m |
| 2026-06-26 | RA73037 | - | Jun 26, 07:20 UTC | Jun 26, 07:55 UTC | 35m |
| 2026-06-25 | UTA521 | SGC → AER | Jun 25, 15:29 UTC | Jun 25, 18:45 UTC | 3h 15m |
| 2026-06-24 | UTA1405 | SGC → UFA | Jun 24, 00:15 UTC | Jun 24, 16:34 UTC | 16h 20m |
| 2026-06-23 | UTA1404 | - | Jun 23, 02:24 UTC | Jun 24, 00:20 UTC | 21h 55m |
| 2026-06-22 | UTA104 | UFA → SGC | Jun 22, 16:24 UTC | Jun 23, 02:24 UTC | 10h 0m |
| 2026-06-21 | UTA185B | - | Jun 21, 04:20 UTC | Jun 21, 22:44 UTC | 18h 25m |
| 2026-06-21 | UTA152 | NJC → UFA | Jun 21, 01:25 UTC | Jun 21, 22:44 UTC | 21h 20m |
| 2026-06-20 | UTA151 | UFA → NJC | Jun 20, 21:19 UTC | Jun 21, 08:54 UTC | 11h 35m |
| 2026-06-17 | UTA436B | - | Jun 17, 14:20 UTC | Jun 17, 14:40 UTC | 20m |
| 2026-06-17 | UTA435B | - | Jun 17, 08:25 UTC | Jun 17, 11:50 UTC | 3h 25m |
| 2026-06-11 | UTA413 | - | Jun 11, 21:30 UTC | Jun 12, 07:10 UTC | 9h 40m |
| 2026-06-08 | UTA372 | MRV → DME | Jun 8, 11:00 UTC | Jun 8, 23:50 UTC | 12h 50m |
| 2026-06-07 | UTA184 | KZN → SGC | Jun 7, 21:00 UTC | Jun 8, 09:00 UTC | 12h 0m |
| 2026-06-07 | UTA183 | SGC → KZN | Jun 7, 18:40 UTC | Jun 7, 19:05 UTC | 25m |
| 2026-06-05 | UTA6126 | NNM → UFA | Jun 5, 19:20 UTC | Jun 6, 16:50 UTC | 21h 30m |
| 2026-06-05 | UTA6126 | NNM → UFA | Jun 5, 19:05 UTC | Jun 6, 16:50 UTC | 21h 45m |
| 2026-06-05 | UTA333 | VKO → NNM | Jun 5, 15:30 UTC | Jun 5, 17:30 UTC | 2h 0m |
| 2026-06-05 | UTA334 | NNM → VKO | Jun 5, 09:35 UTC | Jun 5, 11:20 UTC | 1h 45m |
| 2026-06-04 | UTA6125 | UFA → NNM | Jun 4, 11:30 UTC | Jun 5, 05:35 UTC | 18h 5m |
| 2026-06-04 | UTA6125 | UFA → NNM | Jun 4, 10:25 UTC | Jun 5, 05:35 UTC | 19h 10m |
| 2026-06-03 | UTA446 | KGP → VKO | Jun 3, 11:40 UTC | Jun 4, 07:15 UTC | 19h 35m |
| 2026-06-03 | UTA446 | KGP → VKO | Jun 3, 10:40 UTC | Jun 4, 07:15 UTC | 20h 35m |
| 2026-06-02 | UTA446 | KGP → VKO | Jun 2, 13:15 UTC | Jun 3, 07:15 UTC | 18h 0m |
| 2026-06-01 | UTA6562 | KGP → UFA | Jun 1, 16:30 UTC | Jun 2, 13:15 UTC | 20h 45m |
| 2026-06-01 | UTA445 | VKO → KGP | Jun 1, 10:30 UTC | Jun 1, 16:35 UTC | 6h 5m |
| 2026-05-31 | UTA446 | KGP → VKO | May 31, 12:45 UTC | Jun 1, 07:05 UTC | 18h 20m |
| 2026-05-30 | UTA151 | UFA → NJC | May 30, 16:55 UTC | May 31, 12:50 UTC | 19h 55m |
| 2026-05-30 | UTA6151 | - | May 30, 12:25 UTC | May 30, 17:00 UTC | 4h 35m |
| 2026-05-29 | UTA6578 | KGP → UFA | May 29, 16:20 UTC | May 30, 12:25 UTC | 20h 5m |
| 2026-05-29 | UTA445 | VKO → KGP | May 29, 10:25 UTC | May 29, 16:30 UTC | 6h 5m |
| 2026-05-28 | UTA446 | KGP → VKO | May 28, 11:20 UTC | May 29, 07:05 UTC | 19h 45m |
| 2026-05-28 | UTA445 | VKO → KGP | May 28, 10:20 UTC | May 29, 07:05 UTC | 20h 45m |
| 2026-05-27 | UTA446 | KGP → VKO | May 27, 11:35 UTC | May 28, 07:10 UTC | 19h 35m |
| 2026-05-27 | UTA446 | KGP → VKO | May 27, 10:35 UTC | May 28, 07:10 UTC | 20h 35m |
| 2026-05-26 | UTA446 | KGP → VKO | May 26, 16:30 UTC | May 27, 07:20 UTC | 14h 51m |
| 2026-05-25 | UTA445 | VKO → KGP | May 25, 10:30 UTC | May 25, 11:45 UTC | 1h 15m |
| 2026-05-24 | UTA446 | KGP → VKO | May 24, 13:20 UTC | May 25, 07:35 UTC | 18h 15m |
| 2026-05-24 | UTA446 | KGP → VKO | May 24, 08:25 UTC | May 25, 07:15 UTC | 22h 50m |
| 2026-05-23 | UTA406 | UFA → SGC | May 23, 20:00 UTC | May 24, 13:20 UTC | 17h 20m |
| 2026-05-23 | UTA405 | SGC → UFA | May 23, 15:25 UTC | May 24, 13:20 UTC | 21h 55m |
| 2026-05-22 | UTA403 | SGC → UFA | May 22, 08:20 UTC | May 22, 16:40 UTC | 8h 20m |
| 2026-05-21 | UTA403 | SGC → UFA | May 21, 11:40 UTC | May 22, 08:30 UTC | 20h 50m |
| 2026-05-21 | UTA445 | VKO → KGP | May 21, 10:35 UTC | May 22, 08:30 UTC | 21h 55m |
| 2026-05-21 | UTA445 | VKO → KGP | May 21, 05:55 UTC | May 21, 07:20 UTC | 1h 25m |
| 2026-05-20 | UTA445 | VKO → KGP | May 20, 11:40 UTC | May 21, 07:20 UTC | 19h 40m |
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-73037 page for operator, model, and routing details .