sensors Mode-S transponder
14FA18
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-64024 · TUPOLEV Tu-204/214/224/234
- Hex
- 14FA18
- Octal
- 05175030
- Decimal
- 1,374,744
- Country
- RU
- Tail
- RA-64024
- Type
- T204
- Flights observed
- 90
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 44m ago
Last known position
Country allocation
The ICAO 24-bit address 14FA18 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 |
|---|---|---|---|
| TUP6482 | Aviastar-TU | 8 | 2026-06-11 |
| TUP6473 | - | 7 | 2026-07-14 |
| TUP6490 | - | 6 | 2026-06-01 |
| TUP9101 | Aviastar-TU | 5 | 2026-06-01 |
| TUP6456 | Aviastar-TU | 5 | 2026-06-09 |
| TUP9615 | - | 4 | 2026-06-10 |
| TUP6492 | Aviastar-TU | 4 | 2026-06-17 |
| TUP6474 | - | 4 | 2026-07-10 |
| TUP6495 | - | 3 | 2026-06-30 |
| TUP6493 | - | 3 | 2026-06-19 |
| TUP6481 | - | 3 | 2026-06-24 |
| TUP6455 | - | 3 | 2026-06-08 |
| TUP6452 | Aviastar-TU | 3 | 2026-06-25 |
| TUP9681 | - | 2 | 2026-05-15 |
| TUP9617 | - | 2 | 2026-06-26 |
| TUP9611 | - | 2 | 2026-05-19 |
| TUP9103 | - | 2 | 2026-05-13 |
| TUP6494 | - | 2 | 2026-06-12 |
| TUP6491 | - | 2 | 2026-07-04 |
| TUP6475 | - | 2 | 2026-07-10 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-18 | TUP6496 | - | Jul 18, 01:50 UTC | Jul 18, 02:00 UTC | 10m |
| 2026-07-15 | TUP6451 | - | Jul 15, 12:40 UTC | Jul 15, 15:25 UTC | 2h 45m |
| 2026-07-14 | TUP6473 | - | Jul 14, 14:20 UTC | Jul 15, 06:20 UTC | 15h 59m |
| 2026-07-14 | TUP6473 | - | Jul 14, 05:05 UTC | Jul 14, 15:20 UTC | 10h 15m |
| 2026-07-12 | TUP6453 | - | Jul 12, 05:25 UTC | Jul 12, 18:05 UTC | 12h 40m |
| 2026-07-11 | TUP6473 | - | Jul 11, 19:00 UTC | Jul 12, 18:01 UTC | 23h 0m |
| 2026-07-11 | TUP6473 | - | Jul 11, 03:35 UTC | Jul 11, 19:35 UTC | 16h 0m |
| 2026-07-10 | TUP6473 | - | Jul 10, 22:55 UTC | Jul 11, 19:35 UTC | 20h 40m |
| 2026-07-10 | TUP6475 | - | Jul 10, 12:05 UTC | Jul 11, 03:40 UTC | 15h 35m |
| 2026-07-10 | TUP6475 | - | Jul 10, 02:25 UTC | Jul 10, 23:10 UTC | 20h 45m |
| 2026-07-10 | TUP6474 | - | Jul 10, 00:05 UTC | Jul 10, 23:10 UTC | 23h 5m |
| 2026-07-04 | TUP6491 | - | Jul 4, 23:20 UTC | Jul 5, 06:40 UTC | 7h 20m |
| 2026-07-04 | TUP6474 | - | Jul 4, 18:45 UTC | Jul 4, 19:10 UTC | 25m |
| 2026-06-30 | TUP6495 | - | Jun 30, 23:10 UTC | Jul 1, 12:40 UTC | 13h 30m |
| 2026-06-30 | TUP6474 | - | Jun 30, 19:10 UTC | Jun 30, 19:40 UTC | 30m |
| 2026-06-29 | TUP6473 | - | Jun 29, 22:05 UTC | Jun 30, 19:40 UTC | 21h 36m |
| 2026-06-29 | TUP6473 | - | Jun 29, 20:09 UTC | Jun 30, 19:40 UTC | 23h 31m |
| 2026-06-27 | TUP6495 | - | Jun 27, 23:50 UTC | Jun 28, 00:30 UTC | 40m |
| 2026-06-26 | TUP9617 | - | Jun 26, 00:39 UTC | Jun 26, 03:00 UTC | 2h 20m |
| 2026-06-25 | TUP6452 | KJA → SVO | Jun 25, 07:54 UTC | Jun 25, 08:20 UTC | 25m |
| 2026-06-25 | TUP6452 | KJA → SVO | Jun 25, 07:00 UTC | Jun 25, 07:19 UTC | 20m |
| 2026-06-24 | TUP6481 | - | Jun 24, 02:09 UTC | Jun 24, 02:54 UTC | 45m |
| 2026-06-22 | TUP6491 | - | Jun 22, 04:09 UTC | Jun 22, 15:45 UTC | 11h 35m |
| 2026-06-19 | TUP6493 | - | Jun 19, 04:25 UTC | Jun 19, 14:24 UTC | 10h 0m |
| 2026-06-18 | TUP6493 | - | Jun 18, 16:05 UTC | Jun 19, 14:24 UTC | 22h 19m |
| 2026-06-18 | TUP6481 | - | Jun 18, 15:45 UTC | Jun 19, 13:59 UTC | 22h 14m |
| 2026-06-18 | TUP6481 | - | Jun 18, 12:10 UTC | Jun 19, 06:44 UTC | 18h 34m |
| 2026-06-17 | TUP6492 | NJC → SVO | Jun 17, 08:55 UTC | Jun 17, 09:20 UTC | 25m |
| 2026-06-17 | TUP6492 | NJC → SVO | Jun 17, 02:55 UTC | Jun 17, 08:10 UTC | 5h 15m |
| 2026-06-12 | TUP6494 | - | Jun 12, 17:00 UTC | Jun 13, 12:20 UTC | 19h 19m |
| 2026-06-11 | TUP6482 | NBC → NBC | Jun 11, 04:40 UTC | Jun 11, 15:50 UTC | 11h 10m |
| 2026-06-10 | TUP6482 | NBC → NBC | Jun 10, 06:05 UTC | Jun 11, 05:20 UTC | 23h 15m |
| 2026-06-10 | TUP9615 | - | Jun 10, 04:35 UTC | Jun 10, 06:55 UTC | 2h 20m |
| 2026-06-09 | TUP6456 | BAX → SVO | Jun 9, 19:40 UTC | Jun 9, 20:15 UTC | 35m |
| 2026-06-09 | TUP6456 | BAX → SVO | Jun 9, 00:05 UTC | Jun 9, 19:00 UTC | 18h 55m |
| 2026-06-08 | TUP6455 | - | Jun 8, 22:05 UTC | Jun 9, 19:00 UTC | 20h 55m |
| 2026-06-08 | TUP6455 | - | Jun 8, 21:50 UTC | Jun 9, 19:00 UTC | 21h 10m |
| 2026-06-08 | TUP6492 | NJC → SVO | Jun 8, 14:40 UTC | Jun 8, 17:55 UTC | 3h 15m |
| 2026-06-06 | TUP6495 | - | Jun 6, 22:25 UTC | Jun 7, 01:35 UTC | 3h 10m |
| 2026-06-06 | TUP6474 | - | Jun 6, 14:54 UTC | Jun 6, 17:54 UTC | 3h 0m |
| 2026-06-05 | TUP9617 | - | Jun 5, 00:45 UTC | Jun 5, 03:00 UTC | 2h 15m |
| 2026-06-04 | TUP6452 | KJA → SVO | Jun 4, 12:50 UTC | Jun 4, 19:15 UTC | 6h 25m |
| 2026-06-02 | TUP6457 | - | Jun 2, 11:25 UTC | Jun 2, 12:05 UTC | 40m |
| 2026-06-01 | TUP6490 | - | Jun 1, 12:05 UTC | Jun 2, 07:25 UTC | 19h 20m |
| 2026-06-01 | TUP6490 | - | Jun 1, 10:15 UTC | Jun 2, 07:25 UTC | 21h 10m |
| 2026-06-01 | TUP9101 | VKO → NBC | Jun 1, 09:40 UTC | Jun 2, 07:25 UTC | 21h 45m |
| 2026-06-01 | TUP6492 | NJC → SVO | Jun 1, 02:40 UTC | Jun 1, 05:40 UTC | 3h 0m |
| 2026-05-28 | TUP6417 | - | May 28, 17:15 UTC | May 28, 23:05 UTC | 5h 50m |
| 2026-05-27 | TUP6451 | - | May 27, 12:50 UTC | May 27, 13:55 UTC | 1h 5m |
| 2026-05-27 | TUP6456 | BAX → SVO | May 27, 05:59 UTC | May 27, 06:25 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-64024 page for operator, model, and routing details .