sensors Mode-S transponder
151FCC
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73676 · AIRBUS A-319
- Hex
- 151FCC
- Octal
- 05217714
- Decimal
- 1,384,396
- Country
- RU
- Tail
- RA-73676
- Type
- A319
- Flights observed
- 52
- Distinct callsigns
- 17
- Country
- RU
- Last broadcast
- 14h ago
Last known position
Country allocation
The ICAO 24-bit address 151FCC 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 17 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| SHU5642 | SAT Airlines | 10 | 2026-07-01 |
| SHU5431 | SAT Airlines | 10 | 2026-07-17 |
| SHU5477 | - | 6 | 2026-07-14 |
| SHU5643 | SAT Airlines | 5 | 2026-07-01 |
| SHU5652 | SAT Airlines | 4 | 2026-05-08 |
| SHU5653 | SAT Airlines | 3 | 2026-05-08 |
| SHU5467 | SAT Airlines | 3 | 2026-07-11 |
| SHU4694 | - | 2 | 2026-07-09 |
| SHU5681 | - | 1 | 2026-06-27 |
| SHU5680 | SAT Airlines | 1 | 2026-06-19 |
| SHU564 | - | 1 | 2026-05-21 |
| SHU5607 | SAT Airlines | 1 | 2026-06-16 |
| SHU5476 | SAT Airlines | 1 | 2026-05-09 |
| SHU5468 | SAT Airlines | 1 | 2026-07-10 |
| SHU5466 | SAT Airlines | 1 | 2026-07-11 |
| SHU4696 | SAT Airlines | 1 | 2026-06-13 |
| SHU4695 | - | 1 | 2026-07-09 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | SHU5431 | PKX → KHV | Jul 17, 19:30 UTC | Jul 17, 19:40 UTC | 10m |
| 2026-07-14 | SHU5477 | - | Jul 14, 16:15 UTC | Jul 14, 20:15 UTC | 4h 0m |
| 2026-07-11 | SHU5467 | PKX → VVO | Jul 11, 20:30 UTC | Jul 11, 20:45 UTC | 15m |
| 2026-07-11 | SHU5466 | VVO → PKX | Jul 11, 09:10 UTC | Jul 11, 16:55 UTC | 7h 45m |
| 2026-07-10 | SHU5468 | VVO → PKX | Jul 10, 16:25 UTC | Jul 10, 16:40 UTC | 15m |
| 2026-07-09 | SHU4695 | - | Jul 9, 15:05 UTC | Jul 10, 10:00 UTC | 18h 55m |
| 2026-07-09 | SHU4694 | - | Jul 9, 13:25 UTC | Jul 10, 10:00 UTC | 20h 35m |
| 2026-07-09 | SHU4694 | - | Jul 9, 08:15 UTC | Jul 10, 00:40 UTC | 16h 25m |
| 2026-07-03 | SHU5431 | PKX → KHV | Jul 3, 19:30 UTC | Jul 3, 19:45 UTC | 15m |
| 2026-07-01 | SHU5643 | OVB → KHV | Jul 1, 15:55 UTC | Jul 1, 16:30 UTC | 35m |
| 2026-07-01 | SHU5642 | KHV → OVB | Jul 1, 13:30 UTC | Jul 1, 14:10 UTC | 40m |
| 2026-06-30 | SHU5642 | KHV → OVB | Jun 30, 18:20 UTC | Jul 1, 14:10 UTC | 19h 50m |
| 2026-06-29 | SHU5643 | OVB → KHV | Jun 29, 16:15 UTC | Jun 30, 09:35 UTC | 17h 20m |
| 2026-06-29 | SHU5642 | KHV → OVB | Jun 29, 01:44 UTC | Jun 29, 14:25 UTC | 12h 40m |
| 2026-06-28 | SHU5642 | KHV → OVB | Jun 28, 16:00 UTC | Jun 29, 14:25 UTC | 22h 25m |
| 2026-06-28 | SHU5642 | KHV → OVB | Jun 28, 13:40 UTC | Jun 28, 14:19 UTC | 40m |
| 2026-06-27 | SHU5642 | KHV → OVB | Jun 27, 18:45 UTC | Jun 28, 14:19 UTC | 19h 35m |
| 2026-06-27 | SHU5681 | - | Jun 27, 08:55 UTC | Jun 27, 09:09 UTC | 15m |
| 2026-06-24 | SHU5431 | PKX → KHV | Jun 24, 18:29 UTC | Jun 24, 18:44 UTC | 15m |
| 2026-06-23 | SHU5477 | PVG → KHV | Jun 23, 15:50 UTC | Jun 23, 19:59 UTC | 4h 10m |
| 2026-06-20 | SHU5467 | PKX → VVO | Jun 20, 18:34 UTC | Jun 20, 18:45 UTC | 10m |
| 2026-06-19 | SHU5680 | VVO → UUS | Jun 19, 18:14 UTC | Jun 20, 01:55 UTC | 7h 40m |
| 2026-06-18 | SHU5643 | OVB → KHV | Jun 18, 16:10 UTC | Jun 19, 09:55 UTC | 17h 44m |
| 2026-06-18 | SHU5642 | KHV → OVB | Jun 18, 13:30 UTC | Jun 18, 14:05 UTC | 35m |
| 2026-06-17 | SHU5643 | OVB → KHV | Jun 17, 16:05 UTC | Jun 18, 14:05 UTC | 22h 0m |
| 2026-06-17 | SHU5642 | KHV → OVB | Jun 17, 13:35 UTC | Jun 17, 14:10 UTC | 35m |
| 2026-06-16 | SHU5607 | UUS → VVO | Jun 16, 06:54 UTC | Jun 16, 09:25 UTC | 2h 30m |
| 2026-06-13 | SHU4696 | UUS → PKX | Jun 13, 13:40 UTC | Jun 13, 21:10 UTC | 7h 30m |
| 2026-06-12 | SHU5431 | PKX → KHV | Jun 12, 19:30 UTC | Jun 13, 13:55 UTC | 18h 24m |
| 2026-06-03 | SHU5431 | PKX → KHV | Jun 3, 18:40 UTC | Jun 3, 18:55 UTC | 15m |
| 2026-06-02 | SHU5477 | PVG → KHV | Jun 2, 15:25 UTC | Jun 2, 19:30 UTC | 4h 5m |
| 2026-05-30 | SHU5477 | PVG → KHV | May 30, 15:35 UTC | May 30, 19:30 UTC | 3h 55m |
| 2026-05-27 | SHU5431 | PKX → KHV | May 27, 18:50 UTC | May 27, 19:00 UTC | 10m |
| 2026-05-26 | SHU5477 | PVG → KHV | May 26, 15:24 UTC | May 26, 19:45 UTC | 4h 20m |
| 2026-05-21 | SHU564 | - | May 21, 16:05 UTC | May 21, 16:35 UTC | 30m |
| 2026-05-21 | SHU5642 | KHV → OVB | May 21, 13:45 UTC | May 21, 14:20 UTC | 35m |
| 2026-05-17 | SHU5431 | PKX → KHV | May 17, 18:45 UTC | May 17, 18:55 UTC | 10m |
| 2026-05-09 | SHU5476 | KHV → PVG | May 9, 15:45 UTC | May 9, 20:15 UTC | 4h 30m |
| 2026-05-08 | SHU5653 | IKT → KHV | May 8, 17:35 UTC | May 9, 15:45 UTC | 22h 10m |
| 2026-05-08 | SHU5652 | KHV → IKT | May 8, 15:25 UTC | May 8, 15:50 UTC | 25m |
| 2026-05-07 | SHU5652 | KHV → IKT | May 7, 17:05 UTC | May 8, 15:50 UTC | 22h 45m |
| 2026-05-06 | SHU5431 | PKX → KHV | May 6, 18:50 UTC | May 7, 17:00 UTC | 22h 11m |
| 2026-05-04 | SHU5431 | PKX → KHV | May 4, 20:05 UTC | May 5, 15:55 UTC | 19h 50m |
| 2026-05-01 | SHU5653 | IKT → KHV | May 1, 17:10 UTC | May 2, 16:30 UTC | 23h 21m |
| 2026-05-01 | SHU5652 | KHV → IKT | May 1, 15:25 UTC | May 1, 15:50 UTC | 25m |
| 2026-04-29 | SHU5431 | PKX → KHV | Apr 29, 18:25 UTC | Apr 29, 18:40 UTC | 15m |
| 2026-04-28 | SHU5477 | PVG → KHV | Apr 28, 15:40 UTC | Apr 28, 19:20 UTC | 3h 40m |
| 2026-04-24 | SHU5653 | IKT → KHV | Apr 24, 17:05 UTC | Apr 25, 16:00 UTC | 22h 55m |
| 2026-04-24 | SHU5652 | KHV → IKT | Apr 24, 15:00 UTC | Apr 24, 15:30 UTC | 30m |
| 2026-04-21 | SHU5467 | - | Apr 21, 18:15 UTC | Apr 21, 18:25 UTC | 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-73676 page for operator, model, and routing details .