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
- 48
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 13h 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 |
|---|---|---|---|
| TUP6490 | - | 6 | 2026-06-01 |
| TUP6482 | Aviastar-TU | 6 | 2026-05-20 |
| TUP9101 | Aviastar-TU | 5 | 2026-06-01 |
| TUP9615 | - | 3 | 2026-04-22 |
| TUP6456 | Aviastar-TU | 3 | 2026-05-27 |
| TUP9681 | - | 2 | 2026-05-15 |
| TUP9611 | - | 2 | 2026-05-19 |
| TUP9103 | - | 2 | 2026-05-13 |
| TUP6419 | - | 2 | 2026-04-25 |
| TUP6417 | - | 2 | 2026-05-28 |
| TUP6335 | - | 2 | 2026-04-24 |
| TUP9616 | - | 1 | 2026-04-15 |
| TUP6494 | - | 1 | 2026-05-23 |
| TUP6493 | - | 1 | 2026-04-24 |
| TUP6492 | Aviastar-TU | 1 | 2026-06-01 |
| TUP6487 | - | 1 | 2026-04-17 |
| TUP6457 | - | 1 | 2026-06-02 |
| TUP6455 | - | 1 | 2026-05-26 |
| TUP6454 | - | 1 | 2026-05-18 |
| TUP6453 | - | 1 | 2026-05-23 |
Recent flights last 48
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 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 |
| 2026-05-26 | TUP6455 | - | May 26, 10:10 UTC | May 27, 05:04 UTC | 18h 55m |
| 2026-05-26 | TUP6490 | - | May 26, 03:09 UTC | May 26, 06:20 UTC | 3h 10m |
| 2026-05-23 | TUP6453 | - | May 23, 23:10 UTC | May 23, 23:50 UTC | 40m |
| 2026-05-23 | TUP6494 | - | May 23, 15:10 UTC | May 23, 18:15 UTC | 3h 5m |
| 2026-05-21 | TUP6417 | - | May 21, 16:15 UTC | May 22, 00:25 UTC | 8h 10m |
| 2026-05-20 | TUP9101 | VKO → NBC | May 20, 12:00 UTC | May 20, 15:00 UTC | 3h 0m |
| 2026-05-20 | TUP6482 | NBC → NBC | May 20, 04:50 UTC | May 20, 08:15 UTC | 3h 25m |
| 2026-05-19 | TUP6482 | NBC → NBC | May 19, 08:05 UTC | May 20, 08:00 UTC | 23h 56m |
| 2026-05-19 | TUP9611 | - | May 19, 07:00 UTC | May 20, 05:30 UTC | 22h 31m |
| 2026-05-19 | TUP9611 | - | May 19, 06:10 UTC | May 19, 06:25 UTC | 15m |
| 2026-05-18 | TUP6454 | - | May 18, 01:40 UTC | May 18, 08:05 UTC | 6h 25m |
| 2026-05-15 | TUP9681 | - | May 15, 21:45 UTC | May 15, 23:15 UTC | 1h 30m |
| 2026-05-14 | TUP9101 | VKO → NBC | May 14, 09:50 UTC | May 14, 10:15 UTC | 25m |
| 2026-05-14 | TUP9101 | VKO → NBC | May 14, 08:50 UTC | May 14, 09:10 UTC | 20m |
| 2026-05-13 | TUP6482 | NBC → NBC | May 13, 15:55 UTC | May 14, 06:10 UTC | 14h 15m |
| 2026-05-13 | TUP9103 | - | May 13, 09:20 UTC | May 13, 13:45 UTC | 4h 25m |
| 2026-05-13 | TUP6490 | - | May 13, 03:05 UTC | May 13, 06:20 UTC | 3h 15m |
| 2026-05-11 | TUP9681 | - | May 11, 00:45 UTC | May 11, 02:10 UTC | 1h 25m |
| 2026-05-10 | TUP9101 | VKO → NBC | May 10, 14:34 UTC | May 10, 14:49 UTC | 15m |
| 2026-04-30 | TUP9103 | - | Apr 30, 17:55 UTC | Apr 30, 18:10 UTC | 15m |
| 2026-04-30 | TUP6482 | NBC → NBC | Apr 30, 09:20 UTC | Apr 30, 16:00 UTC | 6h 41m |
| 2026-04-29 | TUP6482 | NBC → NBC | Apr 29, 19:15 UTC | Apr 30, 16:00 UTC | 20h 45m |
| 2026-04-29 | TUP6482 | NBC → NBC | Apr 29, 16:55 UTC | Apr 30, 16:00 UTC | 23h 5m |
| 2026-04-29 | TUP6490 | - | Apr 29, 10:20 UTC | Apr 29, 13:35 UTC | 3h 15m |
| 2026-04-28 | TUP6490 | - | Apr 28, 17:35 UTC | Apr 29, 13:35 UTC | 20h 1m |
| 2026-04-28 | TUP6415 | - | Apr 28, 02:45 UTC | Apr 28, 11:20 UTC | 8h 35m |
| 2026-04-25 | TUP6419 | - | Apr 25, 02:20 UTC | Apr 25, 11:50 UTC | 9h 30m |
| 2026-04-24 | TUP6335 | - | Apr 24, 15:25 UTC | Apr 24, 22:45 UTC | 7h 20m |
| 2026-04-24 | TUP6493 | - | Apr 24, 02:50 UTC | Apr 24, 03:00 UTC | 10m |
| 2026-04-22 | TUP9615 | - | Apr 22, 01:25 UTC | Apr 22, 10:50 UTC | 9h 25m |
| 2026-04-21 | TUP6456 | BAX → SVO | Apr 21, 00:15 UTC | Apr 21, 09:05 UTC | 8h 50m |
| 2026-04-19 | TUP6420 | - | Apr 19, 11:15 UTC | Apr 19, 11:25 UTC | 10m |
| 2026-04-18 | TUP6419 | - | Apr 18, 09:10 UTC | Apr 18, 11:20 UTC | 2h 10m |
| 2026-04-17 | TUP6336 | - | Apr 17, 22:30 UTC | Apr 17, 22:50 UTC | 20m |
| 2026-04-17 | TUP6335 | - | Apr 17, 15:30 UTC | Apr 17, 16:00 UTC | 30m |
| 2026-04-17 | TUP6487 | - | Apr 17, 02:59 UTC | Apr 17, 03:10 UTC | 10m |
| 2026-04-15 | TUP9616 | - | Apr 15, 10:30 UTC | Apr 15, 10:45 UTC | 15m |
| 2026-04-15 | TUP9615 | - | Apr 15, 02:55 UTC | Apr 15, 03:50 UTC | 55m |
| 2026-04-15 | TUP9615 | - | Apr 15, 01:35 UTC | Apr 15, 02:50 UTC | 1h 15m |
| 2026-04-14 | TUP6456 | - | Apr 14, 06:45 UTC | Apr 14, 07:00 UTC | 15m |
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 .