sensors Mode-S transponder
151D4B
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73035 · BOEING 737-500
- Hex
- 151D4B
- Octal
- 05216513
- Decimal
- 1,383,755
- Country
- RU
- Tail
- RA-73035
- Type
- B735
- Flights observed
- 79
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 14d ago
Last known position
Country allocation
The ICAO 24-bit address 151D4B 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 |
|---|---|---|---|
| UTA596 | UTair Aviation | 6 | 2026-04-20 |
| UTA376 | UTair Aviation | 6 | 2026-04-21 |
| UTA375 | UTair Aviation | 6 | 2026-04-21 |
| UTA352 | UTair Aviation | 5 | 2026-04-18 |
| UTA333 | UTair Aviation | 5 | 2026-04-21 |
| UTA6316 | - | 4 | 2026-04-16 |
| UTA595 | UTair Aviation | 4 | 2026-04-20 |
| UTA445 | UTair Aviation | 4 | 2026-05-06 |
| UTA6315 | - | 3 | 2026-04-22 |
| UTA446 | UTair Aviation | 3 | 2026-05-01 |
| UTA6437 | UTair Aviation | 2 | 2026-05-12 |
| UTA6180 | - | 2 | 2026-04-14 |
| UTA398 | UTair Aviation | 2 | 2026-04-23 |
| UTA363 | UTair Aviation | 2 | 2026-04-25 |
| UTA351 | - | 2 | 2026-04-17 |
| UTA334 | UTair Aviation | 2 | 2026-04-21 |
| UTA152 | UTair Aviation | 2 | 2026-05-11 |
| UTA9043 | - | 1 | 2026-05-15 |
| UTA9041 | UTair Aviation | 1 | 2026-05-14 |
| UTA7456 | - | 1 | 2026-04-25 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-15 | UTA9043 | - | May 15, 15:30 UTC | May 15, 20:15 UTC | 4h 45m |
| 2026-05-14 | UTA9041 | UFA → BTK | May 14, 04:30 UTC | May 14, 08:35 UTC | 4h 5m |
| 2026-05-12 | UTA410 | KUF → SGC | May 12, 14:20 UTC | May 13, 03:15 UTC | 12h 55m |
| 2026-05-12 | UTA6437 | UFA → IJK | May 12, 12:40 UTC | May 12, 13:10 UTC | 30m |
| 2026-05-11 | UTA6437 | UFA → IJK | May 11, 16:30 UTC | May 12, 13:10 UTC | 20h 41m |
| 2026-05-11 | UTA152 | NJC → UFA | May 11, 08:35 UTC | May 11, 16:30 UTC | 7h 55m |
| 2026-05-10 | UTA152 | NJC → UFA | May 10, 12:34 UTC | May 11, 08:45 UTC | 20h 10m |
| 2026-05-10 | UTA103 | SGC → UFA | May 10, 04:19 UTC | May 10, 12:34 UTC | 8h 15m |
| 2026-05-08 | UTA282 | KUF → SVX | May 8, 16:25 UTC | May 9, 10:30 UTC | 18h 5m |
| 2026-05-08 | UTA6438 | OVB → SGC | May 8, 03:04 UTC | May 8, 16:30 UTC | 13h 25m |
| 2026-05-07 | UTA6424 | GSV → SGC | May 7, 19:55 UTC | May 8, 01:00 UTC | 5h 5m |
| 2026-05-07 | UTA6423 | SGC → GSV | May 7, 11:55 UTC | May 7, 17:50 UTC | 5h 55m |
| 2026-05-06 | UTA6562 | KGP → UFA | May 6, 16:25 UTC | May 7, 12:00 UTC | 19h 35m |
| 2026-05-06 | UTA445 | VKO → KGP | May 6, 10:30 UTC | May 6, 16:30 UTC | 6h 0m |
| 2026-05-06 | UTA6561 | UFA → KGP | May 6, 01:10 UTC | May 6, 08:10 UTC | 7h 0m |
| 2026-05-04 | UTA104 | UFA → SGC | May 4, 16:25 UTC | May 4, 16:35 UTC | 10m |
| 2026-05-01 | UTA445 | VKO → KGP | May 1, 12:50 UTC | May 1, 18:25 UTC | 5h 35m |
| 2026-05-01 | UTA446 | KGP → VKO | May 1, 06:00 UTC | May 1, 07:25 UTC | 1h 25m |
| 2026-04-29 | UTA445 | VKO → KGP | Apr 29, 10:30 UTC | Apr 30, 02:40 UTC | 16h 9m |
| 2026-04-29 | UTA446 | KGP → VKO | Apr 29, 06:10 UTC | Apr 29, 07:40 UTC | 1h 30m |
| 2026-04-27 | UTA445 | VKO → KGP | Apr 27, 10:50 UTC | Apr 28, 01:10 UTC | 14h 20m |
| 2026-04-26 | UTA446 | KGP → VKO | Apr 26, 15:45 UTC | Apr 27, 08:10 UTC | 16h 25m |
| 2026-04-25 | UTA363 | VKO → UFA | Apr 25, 23:40 UTC | Apr 26, 05:50 UTC | 6h 10m |
| 2026-04-25 | UTA7456 | - | Apr 25, 01:20 UTC | Apr 25, 18:40 UTC | 17h 20m |
| 2026-04-23 | UTA363 | VKO → UFA | Apr 23, 22:55 UTC | Apr 24, 00:15 UTC | 1h 20m |
| 2026-04-23 | UTA398 | GDZ → VKO | Apr 23, 15:25 UTC | Apr 23, 15:55 UTC | 30m |
| 2026-04-23 | UTA398 | GDZ → VKO | Apr 23, 12:55 UTC | Apr 23, 13:55 UTC | 1h 0m |
| 2026-04-23 | UTA397 | VKO → GDZ | Apr 23, 07:35 UTC | Apr 23, 10:35 UTC | 3h 0m |
| 2026-04-23 | UTA574 | MRV → VKO | Apr 23, 02:55 UTC | Apr 23, 05:55 UTC | 3h 0m |
| 2026-04-22 | UTA573 | VKO → MRV | Apr 22, 21:50 UTC | Apr 23, 00:55 UTC | 3h 5m |
| 2026-04-22 | UTA180 | UCT → VKO | Apr 22, 12:55 UTC | Apr 22, 18:00 UTC | 5h 5m |
| 2026-04-22 | UTA6315 | - | Apr 22, 02:25 UTC | Apr 22, 11:25 UTC | 9h 0m |
| 2026-04-21 | UTA376 | SCW → VKO | Apr 21, 19:00 UTC | Apr 21, 20:20 UTC | 1h 20m |
| 2026-04-21 | UTA375 | VKO → SCW | Apr 21, 16:10 UTC | Apr 21, 17:35 UTC | 1h 25m |
| 2026-04-21 | UTA334 | NNM → VKO | Apr 21, 09:05 UTC | Apr 21, 11:20 UTC | 2h 15m |
| 2026-04-21 | UTA333 | VKO → NNM | Apr 21, 05:30 UTC | Apr 21, 07:35 UTC | 2h 5m |
| 2026-04-20 | UTA376 | SCW → VKO | Apr 20, 19:10 UTC | Apr 20, 20:35 UTC | 1h 25m |
| 2026-04-20 | UTA375 | VKO → SCW | Apr 20, 16:05 UTC | Apr 20, 17:30 UTC | 1h 25m |
| 2026-04-20 | UTA596 | USK → VKO | Apr 20, 12:00 UTC | Apr 20, 14:25 UTC | 2h 25m |
| 2026-04-20 | UTA595 | VKO → USK | Apr 20, 08:15 UTC | Apr 20, 10:30 UTC | 2h 15m |
| 2026-04-19 | UTA376 | SCW → VKO | Apr 19, 18:55 UTC | Apr 19, 20:20 UTC | 1h 25m |
| 2026-04-19 | UTA375 | VKO → SCW | Apr 19, 16:00 UTC | Apr 19, 17:20 UTC | 1h 20m |
| 2026-04-19 | UTA333 | VKO → NNM | Apr 19, 09:05 UTC | Apr 19, 10:55 UTC | 1h 50m |
| 2026-04-19 | UTA333 | VKO → NNM | Apr 19, 05:40 UTC | Apr 19, 07:35 UTC | 1h 55m |
| 2026-04-18 | UTA456 | - | Apr 18, 07:20 UTC | Apr 18, 15:30 UTC | 8h 10m |
| 2026-04-18 | UTA352 | HMA → VKO | Apr 18, 05:25 UTC | Apr 18, 05:55 UTC | 30m |
| 2026-04-18 | UTA352 | HMA → VKO | Apr 18, 05:10 UTC | Apr 18, 05:55 UTC | 45m |
| 2026-04-18 | UTA352 | HMA → VKO | Apr 18, 04:25 UTC | Apr 18, 05:20 UTC | 55m |
| 2026-04-17 | UTA351 | - | Apr 17, 18:05 UTC | Apr 17, 18:30 UTC | 25m |
| 2026-04-17 | UTA334 | NNM → VKO | Apr 17, 11:20 UTC | Apr 17, 13:15 UTC | 1h 55m |
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-73035 page for operator, model, and routing details .