sensors Mode-S transponder
14FA34
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-64052 · TUPOLEV Tu-204/214/224/234
- Hex
- 14FA34
- Octal
- 05175064
- Decimal
- 1,374,772
- Country
- RU
- Tail
- RA-64052
- Type
- T204
- Flights observed
- 47
- Distinct callsigns
- 17
- Country
- RU
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 14FA34 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 |
|---|---|---|---|
| TUP9623 | - | 9 | 2026-07-13 |
| TUP9102 | Aviastar-TU | 9 | 2026-07-12 |
| TUP6456 | - | 7 | 2026-06-30 |
| TUP9657 | - | 3 | 2026-06-16 |
| TUP6452 | Aviastar-TU | 3 | 2026-06-11 |
| TUP9655 | - | 2 | 2026-07-01 |
| TUP9602 | - | 2 | 2026-07-03 |
| TUP9103 | - | 2 | 2026-07-05 |
| TUP6454 | - | 2 | 2026-04-18 |
| TUP9653 | - | 1 | 2026-04-20 |
| TUP9624 | Aviastar-TU | 1 | 2026-05-19 |
| TUP6490 | - | 1 | 2026-06-09 |
| TUP6488 | - | 1 | 2026-07-03 |
| TUP6476 | - | 1 | 2026-04-30 |
| TUP6474 | - | 1 | 2026-05-09 |
| TUP6460 | - | 1 | 2026-06-05 |
| TUP6458 | - | 1 | 2026-07-04 |
Recent flights last 47
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | TUP9623 | - | Jul 13, 03:50 UTC | Jul 13, 06:15 UTC | 2h 25m |
| 2026-07-12 | TUP9102 | NBC → VKO | Jul 12, 20:55 UTC | Jul 12, 21:10 UTC | 15m |
| 2026-07-06 | TUP9623 | - | Jul 6, 05:05 UTC | Jul 7, 00:00 UTC | 18h 55m |
| 2026-07-06 | TUP9623 | - | Jul 6, 03:45 UTC | Jul 7, 00:00 UTC | 20h 15m |
| 2026-07-05 | TUP9103 | - | Jul 5, 21:10 UTC | Jul 5, 21:30 UTC | 20m |
| 2026-07-04 | TUP6458 | - | Jul 4, 05:55 UTC | Jul 4, 08:05 UTC | 2h 10m |
| 2026-07-03 | TUP9602 | - | Jul 3, 11:55 UTC | Jul 4, 02:15 UTC | 14h 20m |
| 2026-07-03 | TUP6488 | - | Jul 3, 03:25 UTC | Jul 4, 02:15 UTC | 22h 50m |
| 2026-07-01 | TUP9655 | - | Jul 1, 23:40 UTC | Jul 2, 00:55 UTC | 1h 15m |
| 2026-07-01 | TUP9655 | - | Jul 1, 22:50 UTC | Jul 1, 23:05 UTC | 15m |
| 2026-06-30 | TUP6456 | - | Jun 30, 08:30 UTC | Jun 30, 10:30 UTC | 2h 0m |
| 2026-06-29 | TUP9602 | - | Jun 29, 13:24 UTC | Jun 30, 05:10 UTC | 15h 45m |
| 2026-06-16 | TUP9657 | - | Jun 16, 17:00 UTC | Jun 16, 17:15 UTC | 15m |
| 2026-06-16 | TUP6456 | BAX → SVO | Jun 16, 04:45 UTC | Jun 16, 06:54 UTC | 2h 10m |
| 2026-06-15 | TUP6456 | BAX → SVO | Jun 15, 23:45 UTC | Jun 16, 00:20 UTC | 35m |
| 2026-06-13 | TUP9102 | NBC → VKO | Jun 13, 22:40 UTC | Jun 13, 23:30 UTC | 50m |
| 2026-06-13 | TUP9102 | NBC → VKO | Jun 13, 03:05 UTC | Jun 13, 23:30 UTC | 20h 24m |
| 2026-06-13 | TUP9102 | NBC → VKO | Jun 13, 02:30 UTC | Jun 13, 23:30 UTC | 20h 59m |
| 2026-06-11 | TUP9623 | - | Jun 11, 22:20 UTC | Jun 12, 00:35 UTC | 2h 15m |
| 2026-06-11 | TUP6452 | KJA → SVO | Jun 11, 07:10 UTC | Jun 11, 07:35 UTC | 25m |
| 2026-06-11 | TUP6452 | KJA → SVO | Jun 11, 01:40 UTC | Jun 11, 02:15 UTC | 35m |
| 2026-06-10 | TUP6452 | KJA → SVO | Jun 10, 03:05 UTC | Jun 11, 02:15 UTC | 23h 10m |
| 2026-06-10 | TUP9623 | - | Jun 10, 00:55 UTC | Jun 10, 03:10 UTC | 2h 15m |
| 2026-06-09 | TUP9102 | NBC → VKO | Jun 9, 10:35 UTC | Jun 9, 11:05 UTC | 30m |
| 2026-06-09 | TUP9102 | NBC → VKO | Jun 9, 09:25 UTC | Jun 9, 10:00 UTC | 35m |
| 2026-06-09 | TUP6490 | - | Jun 9, 02:45 UTC | Jun 9, 05:50 UTC | 3h 5m |
| 2026-06-06 | TUP9623 | - | Jun 6, 01:05 UTC | Jun 6, 03:30 UTC | 2h 25m |
| 2026-06-05 | TUP6460 | - | Jun 5, 06:50 UTC | Jun 5, 08:30 UTC | 1h 40m |
| 2026-06-03 | TUP9623 | - | Jun 3, 02:40 UTC | Jun 3, 04:55 UTC | 2h 15m |
| 2026-06-02 | TUP6456 | BAX → SVO | Jun 2, 04:20 UTC | Jun 2, 06:25 UTC | 2h 5m |
| 2026-06-01 | TUP6456 | BAX → SVO | Jun 1, 23:25 UTC | Jun 1, 23:55 UTC | 30m |
| 2026-05-23 | TUP9103 | - | May 23, 20:40 UTC | May 23, 21:30 UTC | 50m |
| 2026-05-22 | TUP9102 | NBC → VKO | May 22, 17:00 UTC | May 23, 08:00 UTC | 15h 0m |
| 2026-05-19 | TUP9624 | VKO → VKO | May 19, 06:30 UTC | May 19, 18:20 UTC | 11h 50m |
| 2026-05-12 | TUP9102 | NBC → VKO | May 12, 14:30 UTC | May 12, 15:40 UTC | 1h 10m |
| 2026-05-09 | TUP6474 | - | May 9, 02:10 UTC | May 9, 05:25 UTC | 3h 15m |
| 2026-05-05 | TUP9623 | - | May 5, 04:40 UTC | May 5, 17:10 UTC | 12h 30m |
| 2026-05-01 | TUP9102 | NBC → VKO | May 1, 08:50 UTC | May 1, 10:15 UTC | 1h 25m |
| 2026-04-30 | TUP6476 | - | Apr 30, 15:15 UTC | May 1, 05:45 UTC | 14h 30m |
| 2026-04-30 | TUP9623 | - | Apr 30, 02:40 UTC | Apr 30, 11:45 UTC | 9h 5m |
| 2026-04-28 | TUP6456 | BAX → SVO | Apr 28, 04:55 UTC | Apr 28, 07:10 UTC | 2h 15m |
| 2026-04-27 | TUP6456 | BAX → SVO | Apr 27, 22:20 UTC | Apr 28, 00:20 UTC | 2h 0m |
| 2026-04-20 | TUP9653 | - | Apr 20, 18:35 UTC | Apr 20, 22:10 UTC | 3h 35m |
| 2026-04-18 | TUP6454 | - | Apr 18, 06:55 UTC | Apr 18, 07:20 UTC | 25m |
| 2026-04-18 | TUP6454 | - | Apr 18, 00:15 UTC | Apr 18, 00:45 UTC | 30m |
| 2026-04-13 | TUP9657 | VKO → VKO | Apr 13, 19:50 UTC | Apr 13, 20:05 UTC | 15m |
| 2026-04-13 | TUP9657 | VKO → VKO | Apr 13, 16:30 UTC | Apr 13, 20:05 UTC | 3h 35m |
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-64052 page for operator, model, and routing details .