sensors Mode-S transponder
151DB9
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73145 · BOEING 737-800
- Hex
- 151DB9
- Octal
- 05216671
- Decimal
- 1,383,865
- Country
- RU
- Tail
- RA-73145
- Type
- B738
- Flights observed
- 55
- Distinct callsigns
- 19
- Country
- RU
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address 151DB9 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 19 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| UTA572 | UTair Aviation | 18 | 2026-05-28 |
| UTA463 | UTair Aviation | 7 | 2026-05-29 |
| UTA571 | UTair Aviation | 4 | 2026-05-31 |
| UTA248 | UTair Aviation | 4 | 2026-05-13 |
| UTA575 | UTair Aviation | 3 | 2026-05-23 |
| UTA6136 | UTair Aviation | 2 | 2026-05-06 |
| UTA591 | UTair Aviation | 2 | 2026-05-06 |
| UTA464 | UTair Aviation | 2 | 2026-05-24 |
| UTA435 | UTair Aviation | 2 | 2026-04-21 |
| UTA295 | UTair Aviation | 2 | 2026-04-16 |
| UTA592 | UTair Aviation | 1 | 2026-05-08 |
| UTA521 | UTair Aviation | 1 | 2026-04-20 |
| UTA364 | UTair Aviation | 1 | 2026-04-29 |
| UTA358 | UTair Aviation | 1 | 2026-05-20 |
| UTA356 | UTair Aviation | 1 | 2026-04-24 |
| UTA296 | - | 1 | 2026-04-16 |
| UTA291 | UTair Aviation | 1 | 2026-04-18 |
| UTA267 | UTair Aviation | 1 | 2026-05-30 |
| 295 | - | 1 | 2026-04-17 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-31 | UTA571 | VKO → KJA | May 31, 09:00 UTC | Jun 1, 01:45 UTC | 16h 45m |
| 2026-05-30 | UTA267 | VKO → AER | May 30, 09:45 UTC | May 30, 10:05 UTC | 20m |
| 2026-05-29 | UTA463 | VKO → TJM | May 29, 07:30 UTC | May 29, 07:45 UTC | 15m |
| 2026-05-28 | UTA572 | KJA → VKO | May 28, 14:50 UTC | May 29, 04:40 UTC | 13h 50m |
| 2026-05-28 | UTA572 | KJA → VKO | May 28, 09:05 UTC | May 29, 04:40 UTC | 19h 35m |
| 2026-05-27 | UTA572 | KJA → VKO | May 27, 20:20 UTC | May 28, 15:35 UTC | 19h 15m |
| 2026-05-27 | UTA572 | KJA → VKO | May 27, 19:50 UTC | May 28, 15:35 UTC | 19h 45m |
| 2026-05-27 | UTA572 | KJA → VKO | May 27, 09:10 UTC | May 28, 01:50 UTC | 16h 40m |
| 2026-05-25 | UTA572 | KJA → VKO | May 25, 04:50 UTC | May 25, 05:15 UTC | 25m |
| 2026-05-24 | UTA464 | TJM → VKO | May 24, 09:00 UTC | May 25, 04:15 UTC | 19h 15m |
| 2026-05-24 | UTA464 | TJM → VKO | May 24, 07:45 UTC | May 25, 04:15 UTC | 20h 30m |
| 2026-05-23 | UTA575 | VKO → KRR | May 23, 12:20 UTC | May 23, 12:55 UTC | 35m |
| 2026-05-22 | UTA575 | VKO → KRR | May 22, 14:20 UTC | May 23, 12:55 UTC | 22h 34m |
| 2026-05-21 | UTA572 | KJA → VKO | May 21, 22:45 UTC | May 22, 14:35 UTC | 15h 50m |
| 2026-05-20 | UTA358 | KUF → VKO | May 20, 19:45 UTC | May 21, 05:05 UTC | 9h 20m |
| 2026-05-20 | UTA572 | KJA → VKO | May 20, 01:05 UTC | May 20, 17:25 UTC | 16h 21m |
| 2026-05-19 | UTA572 | KJA → VKO | May 19, 10:35 UTC | May 20, 01:45 UTC | 15h 10m |
| 2026-05-17 | UTA463 | VKO → TJM | May 17, 14:50 UTC | May 18, 10:05 UTC | 19h 15m |
| 2026-05-16 | UTA572 | KJA → VKO | May 16, 22:10 UTC | May 17, 15:25 UTC | 17h 15m |
| 2026-05-13 | UTA248 | SGC → VKO | May 13, 09:35 UTC | May 14, 03:45 UTC | 18h 10m |
| 2026-05-12 | UTA248 | SGC → VKO | May 12, 17:30 UTC | May 13, 10:20 UTC | 16h 50m |
| 2026-05-08 | UTA592 | UFA → VKO | May 8, 13:40 UTC | May 8, 13:55 UTC | 15m |
| 2026-05-06 | UTA591 | VKO → UFA | May 6, 18:15 UTC | May 6, 19:35 UTC | 1h 20m |
| 2026-05-06 | UTA6136 | IAA → VKO | May 6, 16:45 UTC | May 6, 17:00 UTC | 15m |
| 2026-05-05 | UTA6136 | IAA → VKO | May 5, 22:45 UTC | May 6, 16:00 UTC | 17h 15m |
| 2026-05-03 | UTA463 | VKO → TJM | May 3, 14:00 UTC | May 3, 23:45 UTC | 9h 45m |
| 2026-05-03 | UTA463 | VKO → TJM | May 3, 03:45 UTC | May 3, 23:45 UTC | 20h 0m |
| 2026-05-03 | UTA572 | KJA → VKO | May 3, 00:40 UTC | May 3, 23:45 UTC | 23h 4m |
| 2026-05-02 | UTA572 | KJA → VKO | May 2, 22:05 UTC | May 3, 14:40 UTC | 16h 34m |
| 2026-05-02 | UTA575 | VKO → KRR | May 2, 10:30 UTC | May 2, 11:05 UTC | 35m |
| 2026-04-29 | UTA591 | VKO → UFA | Apr 29, 16:40 UTC | Apr 29, 17:01 UTC | 20m |
| 2026-04-29 | UTA364 | UFA → VKO | Apr 29, 09:50 UTC | Apr 29, 11:20 UTC | 1h 30m |
| 2026-04-26 | UTA572 | KJA → VKO | Apr 26, 22:05 UTC | Apr 27, 03:10 UTC | 5h 5m |
| 2026-04-26 | UTA572 | KJA → VKO | Apr 26, 02:50 UTC | Apr 27, 01:20 UTC | 22h 30m |
| 2026-04-24 | UTA463 | VKO → TJM | Apr 24, 08:25 UTC | Apr 24, 08:50 UTC | 25m |
| 2026-04-24 | UTA463 | VKO → TJM | Apr 24, 07:40 UTC | Apr 24, 07:50 UTC | 10m |
| 2026-04-24 | UTA356 | GRV → VKO | Apr 24, 03:10 UTC | Apr 24, 03:35 UTC | 25m |
| 2026-04-23 | UTA463 | VKO → TJM | Apr 23, 07:40 UTC | Apr 23, 07:55 UTC | 15m |
| 2026-04-22 | UTA248 | SGC → VKO | Apr 22, 03:35 UTC | Apr 22, 15:10 UTC | 11h 35m |
| 2026-04-21 | UTA248 | SGC → VKO | Apr 21, 18:20 UTC | Apr 22, 15:10 UTC | 20h 50m |
| 2026-04-21 | UTA435 | SGC → KRR | Apr 21, 07:05 UTC | Apr 22, 04:20 UTC | 21h 15m |
| 2026-04-20 | UTA435 | SGC → KRR | Apr 20, 10:45 UTC | Apr 21, 08:05 UTC | 21h 20m |
| 2026-04-20 | UTA521 | SGC → AER | Apr 20, 08:30 UTC | Apr 20, 08:45 UTC | 15m |
| 2026-04-18 | UTA291 | LED → GDZ | Apr 18, 18:20 UTC | Apr 19, 09:50 UTC | 15h 30m |
| 2026-04-17 | 295 | SVO → SVO | Apr 17, 09:00 UTC | Apr 17, 09:15 UTC | 15m |
| 2026-04-17 | UTA572 | KJA → VKO | Apr 17, 01:20 UTC | Apr 17, 01:30 UTC | 10m |
| 2026-04-17 | UTA572 | KJA → VKO | Apr 17, 00:50 UTC | Apr 17, 01:15 UTC | 25m |
| 2026-04-16 | UTA571 | - | Apr 16, 22:20 UTC | Apr 16, 22:45 UTC | 25m |
| 2026-04-16 | UTA571 | - | Apr 16, 19:40 UTC | Apr 16, 20:20 UTC | 40m |
| 2026-04-16 | UTA296 | - | Apr 16, 14:25 UTC | Apr 16, 15:05 UTC | 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-73145 page for operator, model, and routing details .