Not currently tracked · last seen 1h ago
- Flights observed
- 393 showing last 50
- Avg flight time
- 1h 26m
- Typical route
- BEG → AYT
- Last seen
- 1h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-17 | - | Jul 17, 22:35 UTC | Jul 18, 00:15 UTC | 1h 40m |
| 2026-07-17 | - | Jul 17, 19:20 UTC | Jul 17, 20:55 UTC | 1h 35m |
| 2026-07-17 | - | Jul 17, 17:25 UTC | Jul 17, 17:55 UTC | 30m |
| 2026-07-17 | - | Jul 17, 15:40 UTC | Jul 17, 16:00 UTC | 20m |
| 2026-07-17 | - | Jul 17, 13:05 UTC | Jul 17, 14:20 UTC | 1h 15m |
| 2026-07-17 | - | Jul 17, 10:10 UTC | Jul 17, 11:35 UTC | 1h 25m |
| 2026-07-17 | BEG → GOT | Jul 17, 06:54 UTC | Jul 17, 08:49 UTC | 1h 55m |
| 2026-07-17 | BEG → AYT | Jul 17, 03:20 UTC | Jul 17, 04:59 UTC | 1h 40m |
| 2026-07-16 | ARN → BEG | Jul 16, 18:50 UTC | Jul 16, 21:05 UTC | 2h 15m |
| 2026-07-16 | BEG → ARN | Jul 16, 15:25 UTC | Jul 16, 17:35 UTC | 2h 10m |
| 2026-07-15 | - | Jul 15, 12:55 UTC | Jul 15, 14:15 UTC | 1h 20m |
| 2026-07-15 | BEG → PMO | Jul 15, 10:10 UTC | Jul 15, 11:35 UTC | 1h 25m |
| 2026-07-15 | - | Jul 15, 06:55 UTC | Jul 15, 08:50 UTC | 1h 55m |
| 2026-07-15 | BEG → AYT | Jul 15, 03:10 UTC | Jul 15, 04:50 UTC | 1h 40m |
| 2026-07-14 | LIS → BEG | Jul 14, 15:55 UTC | Jul 14, 18:55 UTC | 3h 0m |
| 2026-07-14 | BEG → LIS | Jul 14, 10:35 UTC | Jul 14, 14:15 UTC | 3h 40m |
| 2026-07-14 | - | Jul 14, 06:20 UTC | Jul 14, 08:10 UTC | 1h 50m |
| 2026-07-14 | BEG → AYT | Jul 14, 03:10 UTC | Jul 14, 04:50 UTC | 1h 40m |
| 2026-07-13 | - | Jul 13, 18:50 UTC | Jul 13, 21:25 UTC | 2h 35m |
| 2026-07-13 | BEG → MAD | Jul 13, 14:10 UTC | Jul 13, 17:15 UTC | 3h 5m |
| 2026-07-13 | - | Jul 13, 12:20 UTC | Jul 13, 12:45 UTC | 25m |
| 2026-07-13 | - | Jul 13, 10:30 UTC | Jul 13, 10:50 UTC | 20m |
| 2026-07-13 | - | Jul 13, 06:50 UTC | Jul 13, 07:20 UTC | 30m |
| 2026-07-13 | - | Jul 13, 05:15 UTC | Jul 13, 05:35 UTC | 20m |
| 2026-07-12 | - | Jul 12, 20:15 UTC | Jul 12, 20:40 UTC | 25m |
| 2026-07-12 | - | Jul 12, 18:40 UTC | Jul 12, 19:01 UTC | 20m |
| 2026-07-12 | TIV → BEG | Jul 12, 17:20 UTC | Jul 12, 17:45 UTC | 25m |
| 2026-07-12 | SKP → BEG | Jul 12, 15:30 UTC | Jul 12, 15:55 UTC | 25m |
| 2026-07-11 | MIR → BEG | Jul 11, 19:15 UTC | Jul 11, 21:05 UTC | 1h 50m |
| 2026-07-11 | - | Jul 11, 16:25 UTC | Jul 11, 18:10 UTC | 1h 45m |
| 2026-07-11 | - | Jul 11, 13:20 UTC | Jul 11, 14:55 UTC | 1h 35m |
| 2026-07-11 | BEG → MIR | Jul 11, 10:35 UTC | Jul 11, 12:35 UTC | 2h 0m |
| 2026-07-11 | - | Jul 11, 06:50 UTC | Jul 11, 08:50 UTC | 2h 0m |
| 2026-07-11 | BEG → AYT | Jul 11, 03:20 UTC | Jul 11, 05:15 UTC | 1h 55m |
| 2026-07-10 | MIR → BEG | Jul 10, 22:05 UTC | Jul 10, 23:45 UTC | 1h 40m |
| 2026-07-10 | - | Jul 10, 19:05 UTC | Jul 10, 20:50 UTC | 1h 45m |
| 2026-07-10 | - | Jul 10, 17:30 UTC | Jul 10, 17:55 UTC | 25m |
| 2026-07-10 | - | Jul 10, 15:55 UTC | Jul 10, 16:15 UTC | 20m |
| 2026-07-10 | - | Jul 10, 13:15 UTC | Jul 10, 14:35 UTC | 1h 20m |
| 2026-07-10 | - | Jul 10, 10:00 UTC | Jul 10, 11:25 UTC | 1h 25m |
| 2026-07-10 | - | Jul 10, 07:00 UTC | Jul 10, 08:45 UTC | 1h 45m |
| 2026-07-10 | - | Jul 10, 03:20 UTC | Jul 10, 05:00 UTC | 1h 40m |
| 2026-07-10 | - | Jul 10, 00:20 UTC | Jul 10, 00:30 UTC | 10m |
| 2026-07-09 | - | Jul 9, 21:55 UTC | Jul 9, 22:05 UTC | 10m |
| 2026-07-09 | - | Jul 9, 17:25 UTC | Jul 9, 19:30 UTC | 2h 5m |
| 2026-07-08 | MIR → BEG | Jul 8, 19:35 UTC | Jul 8, 21:30 UTC | 1h 55m |
| 2026-07-08 | - | Jul 8, 16:55 UTC | Jul 8, 18:35 UTC | 1h 40m |
| 2026-07-08 | PMO → BEG | Jul 8, 13:50 UTC | Jul 8, 15:15 UTC | 1h 25m |
| 2026-07-08 | BEG → PMO | Jul 8, 10:05 UTC | Jul 8, 11:25 UTC | 1h 20m |
| 2026-07-08 | - | Jul 8, 06:45 UTC | Jul 8, 08:15 UTC | 1h 30m |
Specifications
| Registration | YU-APT |
| Aircraft type | AIRBUS A-320 (A320) |
| Mode-S code | 4C01F3 · 23000763 (octal) |
Looking for transponder-level data? View the Mode-S 4C01F3 page for country allocation, callsign history, and ADS-B signal details.
YU-APT frequently asked
What type of aircraft is YU-APT?
YU-APT is a AIRBUS A-320 (ICAO type code A320).
What is the Mode-S transponder code for YU-APT?
YU-APT broadcasts on Mode-S (ICAO 24-bit) address 4C01F3 (octal 23000763). View the transponder page.
What route does YU-APT typically fly?
YU-APT most frequently flies between BEG and AYT based on observed flights.
Where is YU-APT right now?
YU-APT is not currently being tracked; last seen 1h ago.