sensors Mode-S transponder
151D57
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73047 · BOEING 737-500
- Hex
- 151D57
- Octal
- 05216527
- Decimal
- 1,383,767
- Country
- RU
- Tail
- RA-73047
- Type
- B735
- Flights observed
- 124
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- Jul 26, 05:45 UTC
Last known position
Country allocation
The ICAO 24-bit address 151D57 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-08 |
| UTA6125 | - | 7 | 2026-07-18 |
| UTA445 | - | 7 | 2026-07-08 |
| UTA371 | - | 7 | 2026-07-20 |
| UTA744 | UTair Aviation | 5 | 2026-04-27 |
| UTA743 | UTair Aviation | 5 | 2026-04-27 |
| UTA376 | UTair Aviation | 5 | 2026-04-28 |
| UTA375 | UTair Aviation | 5 | 2026-04-28 |
| UTA749 | UTair Aviation | 4 | 2026-07-22 |
| UTA372 | - | 4 | 2026-07-20 |
| UTA824 | UTair Aviation | 3 | 2026-06-10 |
| UTA6474 | UTair Aviation | 3 | 2026-07-16 |
| UTA6126 | - | 3 | 2026-07-19 |
| UTA596 | - | 3 | 2026-04-18 |
| UTA595 | UTair Aviation | 3 | 2026-04-18 |
| UTA574 | UTair Aviation | 3 | 2026-04-19 |
| UTA573 | UTair Aviation | 3 | 2026-04-18 |
| UTA364 | UTair Aviation | 3 | 2026-04-20 |
| UTA186 | UTair Aviation | 3 | 2026-07-21 |
| UTA6316 | - | 2 | 2026-04-17 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | UTA481 | SGC → MRV | Jul 26, 05:35 UTC | Jul 26, 05:45 UTC | 10m |
| 2026-07-24 | UTA416 | KUF → SGC | Jul 24, 03:45 UTC | Jul 24, 20:30 UTC | 16h 45m |
| 2026-07-23 | UTA414 | KUF → SGC | Jul 23, 22:20 UTC | Jul 24, 20:30 UTC | 22h 10m |
| 2026-07-23 | UTA414 | KUF → SGC | Jul 23, 19:15 UTC | Jul 24, 17:25 UTC | 22h 10m |
| 2026-07-22 | UTA749 | TJM → GYD | Jul 22, 03:50 UTC | Jul 22, 13:55 UTC | 10h 5m |
| 2026-07-21 | UTA749 | TJM → GYD | Jul 21, 16:25 UTC | Jul 22, 13:55 UTC | 21h 30m |
| 2026-07-21 | UTA186 | NUX → UFA | Jul 21, 13:05 UTC | Jul 22, 03:50 UTC | 14h 45m |
| 2026-07-21 | UTA186 | NUX → UFA | Jul 21, 08:30 UTC | Jul 22, 03:50 UTC | 19h 20m |
| 2026-07-21 | UTA186 | NUX → UFA | Jul 21, 04:20 UTC | Jul 21, 16:25 UTC | 12h 5m |
| 2026-07-20 | UTA372 | - | Jul 20, 11:50 UTC | Jul 21, 08:30 UTC | 20h 39m |
| 2026-07-20 | UTA372 | - | Jul 20, 11:00 UTC | Jul 21, 08:30 UTC | 21h 30m |
| 2026-07-20 | UTA371 | - | Jul 20, 06:15 UTC | Jul 21, 04:20 UTC | 22h 4m |
| 2026-07-20 | UTA371 | - | Jul 20, 00:15 UTC | Jul 20, 12:05 UTC | 11h 50m |
| 2026-07-19 | UTA6126 | - | Jul 19, 15:05 UTC | Jul 19, 16:40 UTC | 1h 35m |
| 2026-07-18 | UTA6125 | - | Jul 18, 12:35 UTC | Jul 19, 05:40 UTC | 17h 5m |
| 2026-07-18 | UTA6125 | - | Jul 18, 06:50 UTC | Jul 19, 05:40 UTC | 22h 50m |
| 2026-07-17 | UTA6473 | TLK → SGC | Jul 17, 09:55 UTC | Jul 18, 06:55 UTC | 21h 1m |
| 2026-07-16 | UTA6474 | TLK → OVB | Jul 16, 12:09 UTC | Jul 17, 07:44 UTC | 19h 35m |
| 2026-07-16 | UTA372 | - | Jul 16, 10:50 UTC | Jul 17, 07:44 UTC | 20h 55m |
| 2026-07-16 | UTA372 | - | Jul 16, 07:50 UTC | Jul 17, 07:44 UTC | 23h 55m |
| 2026-07-16 | UTA371 | - | Jul 16, 06:35 UTC | Jul 16, 12:09 UTC | 5h 35m |
| 2026-07-13 | UTA421 | - | Jul 13, 20:00 UTC | Jul 14, 03:50 UTC | 7h 50m |
| 2026-07-11 | UTA417 | - | Jul 11, 11:25 UTC | Jul 12, 01:50 UTC | 14h 25m |
| 2026-07-10 | UTA1151 | NJC → UFA | Jul 10, 19:50 UTC | Jul 11, 11:25 UTC | 15h 35m |
| 2026-07-10 | UTA6126 | - | Jul 10, 14:15 UTC | Jul 11, 11:25 UTC | 21h 10m |
| 2026-07-09 | UTA6125 | - | Jul 9, 12:30 UTC | Jul 10, 05:30 UTC | 17h 0m |
| 2026-07-08 | UTA6578 | - | Jul 8, 18:35 UTC | Jul 9, 16:35 UTC | 22h 0m |
| 2026-07-08 | UTA445 | - | Jul 8, 13:05 UTC | Jul 8, 18:40 UTC | 5h 35m |
| 2026-07-08 | UTA446 | - | Jul 8, 07:05 UTC | Jul 8, 07:30 UTC | 25m |
| 2026-07-07 | UTA446 | - | Jul 7, 16:20 UTC | Jul 8, 06:20 UTC | 14h 0m |
| 2026-07-07 | UTA6577 | - | Jul 7, 01:30 UTC | Jul 7, 16:25 UTC | 14h 55m |
| 2026-07-06 | UTA445 | - | Jul 6, 10:25 UTC | Jul 7, 01:35 UTC | 15h 10m |
| 2026-07-06 | UTA446 | - | Jul 6, 07:00 UTC | Jul 6, 07:25 UTC | 25m |
| 2026-07-05 | UTA446 | - | Jul 5, 11:50 UTC | Jul 6, 06:30 UTC | 18h 40m |
| 2026-07-05 | UTA445 | - | Jul 5, 10:35 UTC | Jul 6, 06:30 UTC | 19h 55m |
| 2026-07-04 | UTA446 | - | Jul 4, 12:35 UTC | Jul 5, 07:30 UTC | 18h 55m |
| 2026-07-03 | UTA151 | UFA → NJC | Jul 3, 17:00 UTC | Jul 4, 12:40 UTC | 19h 40m |
| 2026-07-02 | UTA6491 | - | Jul 2, 21:55 UTC | Jul 3, 17:00 UTC | 19h 5m |
| 2026-07-02 | UTA6424 | - | Jul 2, 20:25 UTC | Jul 3, 17:00 UTC | 20h 35m |
| 2026-07-02 | UTA6423 | SGC → GSV | Jul 2, 08:45 UTC | Jul 2, 19:10 UTC | 10h 25m |
| 2026-07-01 | UTA6562 | KGP → UFA | Jul 1, 16:20 UTC | Jul 2, 08:45 UTC | 16h 25m |
| 2026-07-01 | UTA445 | - | Jul 1, 11:50 UTC | Jul 2, 08:45 UTC | 20h 55m |
| 2026-07-01 | UTA445 | - | Jul 1, 10:40 UTC | Jul 2, 08:45 UTC | 22h 5m |
| 2026-07-01 | UTA446 | - | Jul 1, 01:05 UTC | Jul 1, 07:20 UTC | 6h 15m |
| 2026-06-29 | UTA445 | - | Jun 29, 10:44 UTC | Jun 29, 10:59 UTC | 15m |
| 2026-06-28 | UTA446 | - | Jun 28, 16:29 UTC | Jun 29, 07:20 UTC | 14h 50m |
| 2026-06-28 | UTA446 | - | Jun 28, 08:34 UTC | Jun 29, 07:20 UTC | 22h 45m |
| 2026-06-27 | UTA493 | UFA → GDZ | Jun 27, 12:34 UTC | Jun 28, 06:49 UTC | 18h 15m |
| 2026-06-26 | UTA6125 | - | Jun 26, 15:25 UTC | Jun 26, 16:00 UTC | 35m |
| 2026-06-25 | UTA6125 | - | Jun 25, 16:20 UTC | Jun 26, 05:30 UTC | 13h 10m |
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-73047 page for operator, model, and routing details .