sensors Mode-S transponder
151E8A
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73354 · BOEING 757-200
- Hex
- 151E8A
- Octal
- 05217212
- Decimal
- 1,384,074
- Country
- RU
- Tail
- RA-73354
- Type
- B752
- Flights observed
- 55
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 18h ago
Last known position
Country allocation
The ICAO 24-bit address 151E8A 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 |
|---|---|---|---|
| TUP9632 | - | 7 | 2026-05-18 |
| TUP9628 | - | 5 | 2026-06-01 |
| TUP9627 | Aviastar-TU | 4 | 2026-05-28 |
| TUP9626 | - | 4 | 2026-04-30 |
| TUP9625 | - | 4 | 2026-05-13 |
| TUP6420 | - | 4 | 2026-05-26 |
| TUP9634 | - | 3 | 2026-05-02 |
| TUP9633 | - | 3 | 2026-05-15 |
| TUP9631 | - | 3 | 2026-04-19 |
| TUP6454 | - | 3 | 2026-05-24 |
| TUP9688 | - | 2 | 2026-05-20 |
| TUP9648 | - | 2 | 2026-04-14 |
| TUP9619 | - | 2 | 2026-04-22 |
| TUP6488 | - | 2 | 2026-04-17 |
| TUP9647 | - | 1 | 2026-04-13 |
| TUP9643 | - | 1 | 2026-05-27 |
| TUP9630 | - | 1 | 2026-05-08 |
| TUP9629 | - | 1 | 2026-05-06 |
| TUP9622 | - | 1 | 2026-05-05 |
| TUP9617 | - | 1 | 2026-04-22 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-01 | TUP9628 | - | Jun 1, 22:20 UTC | Jun 2, 12:25 UTC | 14h 5m |
| 2026-05-28 | TUP9627 | NJC → VKO | May 28, 23:50 UTC | May 29, 00:10 UTC | 20m |
| 2026-05-27 | TUP9643 | - | May 27, 03:45 UTC | May 27, 17:05 UTC | 13h 21m |
| 2026-05-26 | TUP6420 | - | May 26, 21:34 UTC | May 27, 17:05 UTC | 19h 31m |
| 2026-05-26 | TUP6420 | - | May 26, 18:50 UTC | May 27, 17:05 UTC | 22h 16m |
| 2026-05-26 | TUP6420 | - | May 26, 00:35 UTC | May 26, 22:15 UTC | 21h 40m |
| 2026-05-25 | TUP6420 | - | May 25, 23:04 UTC | May 26, 22:15 UTC | 23h 10m |
| 2026-05-24 | TUP6454 | - | May 24, 16:15 UTC | May 24, 19:50 UTC | 3h 35m |
| 2026-05-20 | TUP9688 | - | May 20, 22:35 UTC | May 21, 18:10 UTC | 19h 35m |
| 2026-05-20 | TUP9688 | - | May 20, 22:10 UTC | May 21, 18:10 UTC | 20h 0m |
| 2026-05-18 | TUP9632 | - | May 18, 13:10 UTC | May 18, 14:55 UTC | 1h 45m |
| 2026-05-17 | TUP9632 | - | May 17, 17:15 UTC | May 18, 14:55 UTC | 21h 40m |
| 2026-05-15 | TUP9633 | - | May 15, 18:45 UTC | May 15, 19:00 UTC | 15m |
| 2026-05-13 | TUP9625 | - | May 13, 20:30 UTC | May 13, 21:50 UTC | 1h 20m |
| 2026-05-12 | TUP9632 | - | May 12, 18:35 UTC | May 13, 14:05 UTC | 19h 30m |
| 2026-05-12 | TUP9632 | - | May 12, 18:20 UTC | May 13, 14:05 UTC | 19h 45m |
| 2026-05-11 | TUP9627 | NJC → VKO | May 11, 20:40 UTC | May 12, 18:40 UTC | 22h 0m |
| 2026-05-08 | TUP9630 | - | May 8, 22:00 UTC | May 9, 14:25 UTC | 16h 25m |
| 2026-05-06 | TUP9629 | - | May 6, 22:45 UTC | May 7, 13:55 UTC | 15h 10m |
| 2026-05-05 | TUP9633 | - | May 5, 22:20 UTC | May 6, 16:05 UTC | 17h 45m |
| 2026-05-05 | TUP9622 | - | May 5, 09:50 UTC | May 5, 22:45 UTC | 12h 55m |
| 2026-05-03 | TUP9627 | NJC → VKO | May 3, 23:45 UTC | May 4, 00:45 UTC | 1h 0m |
| 2026-05-02 | TUP9634 | - | May 2, 15:25 UTC | May 2, 16:25 UTC | 1h 0m |
| 2026-05-01 | TUP9634 | - | May 1, 17:10 UTC | May 2, 16:25 UTC | 23h 16m |
| 2026-05-01 | TUP9628 | SVO → SVO | May 1, 11:30 UTC | May 1, 11:40 UTC | 10m |
| 2026-04-30 | TUP9627 | NJC → VKO | Apr 30, 20:30 UTC | May 1, 10:40 UTC | 14h 10m |
| 2026-04-30 | TUP9626 | - | Apr 30, 11:00 UTC | May 1, 10:30 UTC | 23h 30m |
| 2026-04-29 | TUP9625 | - | Apr 29, 20:35 UTC | Apr 30, 20:30 UTC | 23h 55m |
| 2026-04-28 | TUP9628 | - | Apr 28, 14:25 UTC | Apr 29, 01:50 UTC | 11h 25m |
| 2026-04-28 | TUP9628 | - | Apr 28, 02:35 UTC | Apr 29, 01:50 UTC | 23h 15m |
| 2026-04-28 | TUP9628 | - | Apr 28, 01:55 UTC | Apr 28, 16:15 UTC | 14h 20m |
| 2026-04-27 | TUP6454 | - | Apr 27, 19:05 UTC | Apr 27, 19:15 UTC | 10m |
| 2026-04-27 | TUP6454 | - | Apr 27, 00:00 UTC | Apr 27, 18:25 UTC | 18h 25m |
| 2026-04-25 | TUP6494 | - | Apr 25, 11:25 UTC | Apr 25, 16:45 UTC | 5h 20m |
| 2026-04-25 | TUP9626 | - | Apr 25, 07:40 UTC | Apr 25, 08:00 UTC | 20m |
| 2026-04-22 | TUP9617 | - | Apr 22, 13:50 UTC | Apr 23, 01:50 UTC | 12h 0m |
| 2026-04-22 | TUP9619 | - | Apr 22, 00:35 UTC | Apr 23, 00:30 UTC | 23h 55m |
| 2026-04-21 | TUP9619 | - | Apr 21, 23:45 UTC | Apr 22, 18:10 UTC | 18h 25m |
| 2026-04-21 | TUP9634 | - | Apr 21, 11:50 UTC | Apr 22, 01:35 UTC | 13h 45m |
| 2026-04-20 | TUP9633 | - | Apr 20, 18:05 UTC | Apr 20, 21:30 UTC | 3h 25m |
| 2026-04-19 | TUP9632 | - | Apr 19, 19:30 UTC | Apr 20, 15:15 UTC | 19h 45m |
| 2026-04-19 | TUP9631 | SVO → SVO | Apr 19, 16:30 UTC | Apr 19, 16:50 UTC | 20m |
| 2026-04-17 | TUP6488 | - | Apr 17, 15:20 UTC | Apr 17, 17:15 UTC | 1h 55m |
| 2026-04-17 | TUP6488 | - | Apr 17, 15:05 UTC | Apr 17, 15:15 UTC | 10m |
| 2026-04-16 | TUP9626 | - | Apr 16, 08:40 UTC | Apr 16, 09:00 UTC | 20m |
| 2026-04-15 | TUP9625 | - | Apr 15, 21:05 UTC | Apr 15, 22:55 UTC | 1h 50m |
| 2026-04-15 | TUP9625 | SVO → SVO | Apr 15, 20:50 UTC | Apr 15, 21:00 UTC | 10m |
| 2026-04-15 | TUP9632 | SVO → SVO | Apr 15, 15:05 UTC | Apr 15, 15:25 UTC | 20m |
| 2026-04-15 | TUP9632 | - | Apr 15, 13:01 UTC | Apr 15, 14:55 UTC | 1h 54m |
| 2026-04-14 | TUP9631 | - | Apr 14, 21:20 UTC | Apr 14, 21:45 UTC | 25m |
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-73354 page for operator, model, and routing details .