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
- 83
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 9h 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 |
|---|---|---|---|
| TUP9634 | - | 8 | 2026-07-12 |
| TUP9632 | - | 8 | 2026-06-30 |
| TUP9625 | - | 6 | 2026-07-08 |
| TUP9628 | - | 5 | 2026-06-01 |
| TUP9627 | Aviastar-TU | 5 | 2026-06-08 |
| TUP9631 | - | 4 | 2026-06-15 |
| TUP9630 | - | 4 | 2026-07-13 |
| TUP9629 | - | 4 | 2026-07-17 |
| TUP9626 | - | 4 | 2026-04-30 |
| TUP6420 | - | 4 | 2026-05-26 |
| TUP9633 | - | 3 | 2026-05-15 |
| TUP6488 | - | 3 | 2026-06-12 |
| TUP6454 | - | 3 | 2026-05-24 |
| TUP9688 | - | 2 | 2026-05-20 |
| TUP9648 | - | 2 | 2026-04-14 |
| TUP9622 | - | 2 | 2026-06-07 |
| TUP9619 | - | 2 | 2026-04-22 |
| TUP9617 | - | 2 | 2026-07-03 |
| TUP9612 | - | 2 | 2026-07-07 |
| TUP6496 | - | 2 | 2026-07-14 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | TUP9629 | - | Jul 17, 20:20 UTC | Jul 17, 21:55 UTC | 1h 35m |
| 2026-07-17 | TUP9618 | - | Jul 17, 13:20 UTC | Jul 17, 14:50 UTC | 1h 30m |
| 2026-07-14 | TUP6496 | - | Jul 14, 16:30 UTC | Jul 14, 16:50 UTC | 20m |
| 2026-07-13 | TUP9630 | - | Jul 13, 01:10 UTC | Jul 13, 16:15 UTC | 15h 5m |
| 2026-07-12 | TUP9634 | - | Jul 12, 23:00 UTC | Jul 12, 23:30 UTC | 30m |
| 2026-07-10 | TUP9634 | - | Jul 10, 15:55 UTC | Jul 10, 16:10 UTC | 15m |
| 2026-07-09 | TUP9634 | - | Jul 9, 23:05 UTC | Jul 10, 14:50 UTC | 15h 45m |
| 2026-07-08 | TUP9625 | SVO → SVO | Jul 8, 20:45 UTC | Jul 8, 20:55 UTC | 10m |
| 2026-07-07 | TUP9630 | - | Jul 7, 21:25 UTC | Jul 8, 12:20 UTC | 14h 55m |
| 2026-07-07 | TUP9629 | - | Jul 7, 20:20 UTC | Jul 7, 20:35 UTC | 15m |
| 2026-07-07 | TUP9612 | - | Jul 7, 13:05 UTC | Jul 7, 14:45 UTC | 1h 40m |
| 2026-07-03 | TUP9617 | - | Jul 3, 01:25 UTC | Jul 3, 16:25 UTC | 15h 0m |
| 2026-06-30 | TUP9629 | - | Jun 30, 20:30 UTC | Jun 30, 20:50 UTC | 20m |
| 2026-06-30 | TUP9632 | - | Jun 30, 13:50 UTC | Jun 30, 14:25 UTC | 35m |
| 2026-06-24 | TUP9634 | - | Jun 24, 13:14 UTC | Jun 25, 00:29 UTC | 11h 15m |
| 2026-06-23 | TUP9634 | - | Jun 23, 18:04 UTC | Jun 24, 14:29 UTC | 20h 25m |
| 2026-06-23 | TUP9612 | - | Jun 23, 02:20 UTC | Jun 23, 11:29 UTC | 9h 10m |
| 2026-06-23 | TUP9611 | SVO → SVO | Jun 23, 01:25 UTC | Jun 23, 01:35 UTC | 10m |
| 2026-06-20 | TUP6494 | - | Jun 20, 04:54 UTC | Jun 20, 23:04 UTC | 18h 10m |
| 2026-06-19 | TUP9681 | - | Jun 19, 01:34 UTC | Jun 19, 01:50 UTC | 15m |
| 2026-06-17 | TUP9625 | - | Jun 17, 21:15 UTC | Jun 17, 22:35 UTC | 1h 20m |
| 2026-06-15 | TUP9631 | - | Jun 15, 17:59 UTC | Jun 15, 18:20 UTC | 20m |
| 2026-06-13 | TUP9630 | - | Jun 13, 10:10 UTC | Jun 13, 12:05 UTC | 1h 55m |
| 2026-06-12 | TUP6488 | - | Jun 12, 06:20 UTC | Jun 12, 06:50 UTC | 30m |
| 2026-06-08 | TUP9627 | NJC → VKO | Jun 8, 14:15 UTC | Jun 8, 23:30 UTC | 9h 15m |
| 2026-06-07 | TUP6496 | - | Jun 7, 21:30 UTC | Jun 8, 14:40 UTC | 17h 10m |
| 2026-06-07 | TUP9622 | - | Jun 7, 05:05 UTC | Jun 7, 21:50 UTC | 16h 45m |
| 2026-06-02 | TUP6458 | - | Jun 2, 22:40 UTC | Jun 3, 16:30 UTC | 17h 50m |
| 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 |
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 .