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