sensors Mode-S transponder
151D6C
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73068 · BOEING 737-400
- Hex
- 151D6C
- Octal
- 05216554
- Decimal
- 1,383,788
- Country
- RU
- Tail
- RA-73068
- Type
- B734
- Flights observed
- 192
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 24d ago
Last known position
Country allocation
The ICAO 24-bit address 151D6C 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 |
|---|---|---|---|
| UTA576 | - | 17 | 2026-07-25 |
| UTA575 | UTair Aviation | 14 | 2026-07-25 |
| UTA398 | - | 13 | 2026-07-24 |
| UTA397 | UTair Aviation | 13 | 2026-07-24 |
| UTA250 | UTair Aviation | 9 | 2026-07-22 |
| UTA399 | UTair Aviation | 8 | 2026-07-19 |
| UTA185 | - | 7 | 2026-07-08 |
| UTA363 | UTair Aviation | 6 | 2026-07-25 |
| UTA356 | UTair Aviation | 6 | 2026-07-20 |
| UTA249 | - | 6 | 2026-07-19 |
| UTA744 | UTair Aviation | 4 | 2026-06-16 |
| UTA743 | - | 4 | 2026-06-16 |
| UTA492 | UTair Aviation | 4 | 2026-06-10 |
| UTA491 | UTair Aviation | 4 | 2026-06-10 |
| UTA400 | UTair Aviation | 4 | 2026-07-22 |
| UTA375 | UTair Aviation | 4 | 2026-06-16 |
| UTA373 | - | 4 | 2026-07-02 |
| UTA364 | UTair Aviation | 4 | 2026-07-19 |
| UTA6108 | UTair Aviation | 3 | 2026-07-10 |
| UTA374 | - | 3 | 2026-07-02 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-25 | UTA363 | VKO → UFA | Jul 25, 18:00 UTC | Jul 25, 19:25 UTC | 1h 25m |
| 2026-07-25 | UTA576 | - | Jul 25, 12:50 UTC | Jul 25, 15:45 UTC | 2h 55m |
| 2026-07-25 | UTA575 | VKO → KRR | Jul 25, 07:45 UTC | Jul 25, 10:55 UTC | 3h 10m |
| 2026-07-24 | UTA355 | VKO → GRV | Jul 24, 22:35 UTC | Jul 25, 05:55 UTC | 7h 20m |
| 2026-07-24 | UTA398 | - | Jul 24, 13:10 UTC | Jul 24, 16:10 UTC | 3h 0m |
| 2026-07-24 | UTA397 | VKO → GDZ | Jul 24, 07:45 UTC | Jul 24, 11:30 UTC | 3h 45m |
| 2026-07-23 | UTA398 | - | Jul 23, 19:25 UTC | Jul 23, 20:00 UTC | 35m |
| 2026-07-23 | UTA398 | - | Jul 23, 16:50 UTC | Jul 23, 18:45 UTC | 1h 55m |
| 2026-07-23 | UTA397 | VKO → GDZ | Jul 23, 12:55 UTC | Jul 23, 15:30 UTC | 2h 35m |
| 2026-07-23 | UTA397 | VKO → GDZ | Jul 23, 08:55 UTC | Jul 23, 09:20 UTC | 25m |
| 2026-07-22 | UTA400 | GRV → VKO | Jul 22, 18:35 UTC | Jul 23, 06:35 UTC | 12h 0m |
| 2026-07-22 | UTA250 | AER → VKO | Jul 22, 15:25 UTC | Jul 22, 15:40 UTC | 15m |
| 2026-07-22 | UTA250 | AER → VKO | Jul 22, 12:50 UTC | Jul 22, 13:15 UTC | 25m |
| 2026-07-21 | UTA363 | VKO → UFA | Jul 21, 17:55 UTC | Jul 22, 04:55 UTC | 11h 0m |
| 2026-07-21 | UTA576 | - | Jul 21, 16:00 UTC | Jul 21, 16:20 UTC | 20m |
| 2026-07-21 | UTA576 | - | Jul 21, 13:25 UTC | Jul 21, 13:50 UTC | 25m |
| 2026-07-21 | UTA575 | VKO → KRR | Jul 21, 07:45 UTC | Jul 21, 10:45 UTC | 3h 0m |
| 2026-07-21 | UTA248 | SGC → VKO | Jul 21, 04:50 UTC | Jul 21, 05:40 UTC | 50m |
| 2026-07-20 | UTA247 | - | Jul 20, 18:15 UTC | Jul 21, 04:15 UTC | 9h 59m |
| 2026-07-20 | UTA398 | - | Jul 20, 15:55 UTC | Jul 20, 16:35 UTC | 40m |
| 2026-07-20 | UTA398 | - | Jul 20, 13:05 UTC | Jul 20, 15:20 UTC | 2h 15m |
| 2026-07-20 | UTA397 | VKO → GDZ | Jul 20, 08:00 UTC | Jul 20, 11:30 UTC | 3h 30m |
| 2026-07-20 | UTA356 | GRV → VKO | Jul 20, 05:45 UTC | Jul 20, 06:05 UTC | 20m |
| 2026-07-19 | UTA399 | VKO → GRV | Jul 19, 17:40 UTC | Jul 20, 04:45 UTC | 11h 5m |
| 2026-07-19 | UTA250 | AER → VKO | Jul 19, 12:50 UTC | Jul 19, 16:05 UTC | 3h 15m |
| 2026-07-19 | UTA249 | - | Jul 19, 07:25 UTC | Jul 19, 10:35 UTC | 3h 10m |
| 2026-07-19 | UTA364 | UFA → VKO | Jul 19, 03:35 UTC | Jul 19, 05:00 UTC | 1h 25m |
| 2026-07-17 | UTA363 | - | Jul 17, 18:15 UTC | Jul 18, 04:40 UTC | 10h 26m |
| 2026-07-17 | UTA576 | - | Jul 17, 15:15 UTC | Jul 17, 15:55 UTC | 40m |
| 2026-07-17 | UTA576 | - | Jul 17, 12:40 UTC | Jul 17, 14:35 UTC | 1h 55m |
| 2026-07-17 | UTA575 | VKO → KRR | Jul 17, 07:05 UTC | Jul 17, 09:55 UTC | 2h 50m |
| 2026-07-16 | UTA576 | - | Jul 16, 13:20 UTC | Jul 16, 16:15 UTC | 2h 55m |
| 2026-07-16 | UTA575 | - | Jul 16, 07:10 UTC | Jul 16, 10:55 UTC | 3h 45m |
| 2026-07-15 | UTA1363 | - | Jul 15, 18:30 UTC | Jul 16, 05:05 UTC | 10h 35m |
| 2026-07-15 | UTA250 | - | Jul 15, 15:30 UTC | Jul 15, 15:55 UTC | 25m |
| 2026-07-15 | UTA250 | - | Jul 15, 13:00 UTC | Jul 15, 13:30 UTC | 30m |
| 2026-07-15 | UTA249 | - | Jul 15, 07:30 UTC | Jul 15, 11:15 UTC | 3h 45m |
| 2026-07-14 | UTA398 | - | Jul 14, 12:55 UTC | Jul 14, 16:15 UTC | 3h 20m |
| 2026-07-14 | UTA397 | - | Jul 14, 07:45 UTC | Jul 14, 11:00 UTC | 3h 15m |
| 2026-07-13 | UTA398 | - | Jul 13, 19:25 UTC | Jul 13, 19:40 UTC | 15m |
| 2026-07-13 | UTA398 | - | Jul 13, 16:10 UTC | Jul 13, 18:30 UTC | 2h 20m |
| 2026-07-13 | UTA397 | - | Jul 13, 07:35 UTC | Jul 13, 14:35 UTC | 7h 0m |
| 2026-07-13 | UTA1250 | - | Jul 13, 03:05 UTC | Jul 13, 03:30 UTC | 25m |
| 2026-07-13 | UTA1250 | - | Jul 13, 00:01 UTC | Jul 13, 01:55 UTC | 1h 55m |
| 2026-07-12 | UTA1249 | - | Jul 12, 17:55 UTC | Jul 12, 21:50 UTC | 3h 55m |
| 2026-07-12 | UTA576 | - | Jul 12, 16:05 UTC | Jul 12, 16:25 UTC | 20m |
| 2026-07-12 | UTA576 | - | Jul 12, 12:50 UTC | Jul 12, 15:10 UTC | 2h 20m |
| 2026-07-12 | UTA575 | - | Jul 12, 10:20 UTC | Jul 12, 10:50 UTC | 30m |
| 2026-07-12 | UTA575 | - | Jul 12, 07:01 UTC | Jul 12, 08:25 UTC | 1h 25m |
| 2026-07-12 | UTA364 | - | Jul 12, 04:45 UTC | Jul 12, 05:01 UTC | 15m |
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-73068 page for operator, model, and routing details .