sensors Mode-S transponder
151D4C
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73036 · BOEING 737-500
- Hex
- 151D4C
- Octal
- 05216514
- Decimal
- 1,383,756
- Country
- RU
- Tail
- RA-73036
- Type
- B735
- Flights observed
- 37
- Distinct callsigns
- 18
- Country
- RU
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 151D4C 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 18 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| UTA446 | UTair Aviation | 9 | 2026-06-10 |
| UTA445 | UTair Aviation | 7 | 2026-06-11 |
| UTA9901 | - | 2 | 2026-04-16 |
| UTA9801 | - | 2 | 2026-04-16 |
| UTA478 | UTair Aviation | 2 | 2026-05-06 |
| UTA411 | UTair Aviation | 2 | 2026-04-29 |
| UTA282 | UTair Aviation | 2 | 2026-06-03 |
| UTA6578 | UTair Aviation | 1 | 2026-06-08 |
| UTA6577 | UTair Aviation | 1 | 2026-06-08 |
| UTA6490 | UTair Aviation | 1 | 2026-05-11 |
| UTA6472 | UTair Aviation | 1 | 2026-06-06 |
| UTA6429 | UTair Aviation | 1 | 2026-05-11 |
| UTA6126 | UTair Aviation | 1 | 2026-06-12 |
| UTA477 | UTair Aviation | 1 | 2026-04-30 |
| UTA427 | UTair Aviation | 1 | 2026-05-07 |
| UTA419 | UTair Aviation | 1 | 2026-05-03 |
| UTA406 | UTair Aviation | 1 | 2026-05-09 |
| UTA372 | UTair Aviation | 1 | 2026-06-04 |
Recent flights last 37
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-12 | UTA6126 | NNM → UFA | Jun 12, 14:45 UTC | Jun 12, 15:10 UTC | 25m |
| 2026-06-11 | UTA445 | VKO → KGP | Jun 11, 11:05 UTC | Jun 12, 05:30 UTC | 18h 26m |
| 2026-06-11 | UTA445 | VKO → KGP | Jun 11, 10:40 UTC | Jun 12, 05:30 UTC | 18h 51m |
| 2026-06-10 | UTA446 | KGP → VKO | Jun 10, 16:30 UTC | Jun 11, 07:20 UTC | 14h 50m |
| 2026-06-10 | UTA446 | KGP → VKO | Jun 10, 11:05 UTC | Jun 11, 07:20 UTC | 20h 15m |
| 2026-06-10 | UTA446 | KGP → VKO | Jun 10, 10:55 UTC | Jun 11, 07:20 UTC | 20h 25m |
| 2026-06-10 | UTA446 | KGP → VKO | Jun 10, 06:50 UTC | Jun 10, 07:20 UTC | 30m |
| 2026-06-09 | UTA446 | KGP → VKO | Jun 9, 13:10 UTC | Jun 10, 06:05 UTC | 16h 55m |
| 2026-06-09 | UTA446 | KGP → VKO | Jun 9, 08:20 UTC | Jun 10, 06:05 UTC | 21h 45m |
| 2026-06-08 | UTA6578 | KGP → UFA | Jun 8, 16:25 UTC | Jun 9, 13:10 UTC | 20h 45m |
| 2026-06-08 | UTA445 | VKO → KGP | Jun 8, 11:30 UTC | Jun 9, 08:20 UTC | 20h 50m |
| 2026-06-08 | UTA445 | VKO → KGP | Jun 8, 10:30 UTC | Jun 9, 08:20 UTC | 21h 50m |
| 2026-06-08 | UTA6577 | UFA → KGP | Jun 8, 06:55 UTC | Jun 8, 07:10 UTC | 15m |
| 2026-06-07 | UTA445 | VKO → KGP | Jun 7, 11:05 UTC | Jun 8, 06:10 UTC | 19h 5m |
| 2026-06-07 | UTA445 | VKO → KGP | Jun 7, 10:40 UTC | Jun 8, 06:10 UTC | 19h 30m |
| 2026-06-06 | UTA446 | KGP → VKO | Jun 6, 15:34 UTC | Jun 7, 07:05 UTC | 15h 30m |
| 2026-06-06 | UTA446 | KGP → VKO | Jun 6, 07:05 UTC | Jun 7, 07:00 UTC | 23h 55m |
| 2026-06-06 | UTA6472 | TLK → OMS | Jun 6, 06:30 UTC | Jun 6, 15:34 UTC | 9h 5m |
| 2026-06-04 | UTA372 | MRV → DME | Jun 4, 18:20 UTC | Jun 5, 00:00 UTC | 5h 40m |
| 2026-06-03 | UTA282 | KUF → SVX | Jun 3, 07:35 UTC | Jun 3, 10:30 UTC | 2h 55m |
| 2026-05-11 | UTA6490 | KUF → VKO | May 11, 18:45 UTC | May 12, 04:05 UTC | 9h 20m |
| 2026-05-11 | UTA6429 | SGC → GSV | May 11, 15:50 UTC | May 11, 17:25 UTC | 1h 35m |
| 2026-05-09 | UTA406 | UFA → SGC | May 9, 01:05 UTC | May 9, 20:05 UTC | 19h 0m |
| 2026-05-08 | UTA445 | VKO → KGP | May 8, 10:29 UTC | May 9, 01:05 UTC | 14h 35m |
| 2026-05-08 | UTA446 | KGP → VKO | May 8, 01:00 UTC | May 8, 07:39 UTC | 6h 40m |
| 2026-05-07 | UTA427 | SGC → UFA | May 7, 02:30 UTC | May 8, 01:00 UTC | 22h 30m |
| 2026-05-06 | UTA478 | KUF → SGC | May 6, 18:20 UTC | May 7, 02:35 UTC | 8h 15m |
| 2026-05-05 | UTA478 | KUF → SGC | May 5, 20:20 UTC | May 6, 10:30 UTC | 14h 10m |
| 2026-05-03 | UTA419 | SGC → KUF | May 3, 19:34 UTC | May 4, 06:40 UTC | 11h 5m |
| 2026-05-03 | UTA282 | KUF → SVX | May 3, 07:30 UTC | May 3, 10:25 UTC | 2h 55m |
| 2026-04-30 | UTA477 | SGC → KUF | Apr 30, 07:25 UTC | Apr 30, 22:35 UTC | 15h 10m |
| 2026-04-29 | UTA411 | SGC → KUF | Apr 29, 19:40 UTC | Apr 30, 18:35 UTC | 22h 55m |
| 2026-04-29 | UTA411 | SGC → KUF | Apr 29, 18:55 UTC | Apr 30, 08:00 UTC | 13h 4m |
| 2026-04-16 | UTA9801 | - | Apr 16, 19:25 UTC | Apr 16, 20:10 UTC | 45m |
| 2026-04-16 | UTA9801 | - | Apr 16, 18:40 UTC | Apr 16, 19:05 UTC | 26m |
| 2026-04-16 | UTA9901 | - | Apr 16, 11:09 UTC | Apr 16, 11:35 UTC | 25m |
| 2026-04-16 | UTA9901 | - | Apr 16, 09:29 UTC | Apr 16, 11:04 UTC | 1h 35m |
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-73036 page for operator, model, and routing details .