Not currently tracked · last seen Jul 26, 20:20 UTC
- Flights observed
- 358 showing last 50
- Avg flight time
- 1h 40m
- Typical route
- IST → AMM
- Last seen
- Jul 26, 20:20 UTC
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-26 | STN → AMM | Jul 26, 16:00 UTC | Jul 26, 20:20 UTC | 4h 20m |
| 2026-07-26 | AMM → STN | Jul 26, 08:15 UTC | Jul 26, 13:25 UTC | 5h 10m |
| 2026-07-26 | DAM → AMM | Jul 26, 05:35 UTC | Jul 26, 06:00 UTC | 25m |
| 2026-07-26 | AMM → DAM | Jul 26, 03:50 UTC | Jul 26, 04:10 UTC | 20m |
| 2026-07-25 | IST → AMM | Jul 25, 18:45 UTC | Jul 25, 20:35 UTC | 1h 50m |
| 2026-07-25 | AMM → IST | Jul 25, 14:55 UTC | Jul 25, 16:45 UTC | 1h 50m |
| 2026-07-25 | IST → AMM | Jul 25, 11:45 UTC | Jul 25, 13:35 UTC | 1h 50m |
| 2026-07-25 | AMM → IST | Jul 25, 07:35 UTC | Jul 25, 09:40 UTC | 2h 5m |
| 2026-07-25 | SHJ → AMM | Jul 25, 01:15 UTC | Jul 25, 04:00 UTC | 2h 45m |
| 2026-07-24 | AMM → SHJ | Jul 24, 21:00 UTC | Jul 24, 23:45 UTC | 2h 45m |
| 2026-07-24 | TUN → AMM | Jul 24, 13:15 UTC | Jul 24, 16:30 UTC | 3h 15m |
| 2026-07-24 | AMM → TUN | Jul 24, 07:40 UTC | Jul 24, 11:00 UTC | 3h 20m |
| 2026-07-23 | BGW → AMM | Jul 23, 22:35 UTC | Jul 24, 02:25 UTC | 3h 50m |
| 2026-07-23 | IST → AMM | Jul 23, 19:10 UTC | Jul 23, 21:00 UTC | 1h 50m |
| 2026-07-23 | AMM → IST | Jul 23, 15:30 UTC | Jul 23, 17:30 UTC | 2h 0m |
| 2026-07-23 | BEY → AMM | Jul 23, 09:55 UTC | Jul 23, 10:35 UTC | 40m |
| 2026-07-23 | AMM → BEY | Jul 23, 08:00 UTC | Jul 23, 08:30 UTC | 30m |
| 2026-07-23 | ALP → AMM | Jul 23, 04:00 UTC | Jul 23, 04:35 UTC | 35m |
| 2026-07-23 | AMM → ALP | Jul 23, 01:30 UTC | Jul 23, 02:05 UTC | 35m |
| 2026-07-22 | CAI → AMM | Jul 22, 18:55 UTC | Jul 22, 19:50 UTC | 55m |
| 2026-07-22 | AMM → CAI | Jul 22, 16:30 UTC | Jul 22, 17:30 UTC | 1h 0m |
| 2026-07-22 | CAI → AMM | Jul 22, 11:45 UTC | Jul 22, 12:35 UTC | 50m |
| 2026-07-22 | CAI → AMM | Jul 22, 03:20 UTC | Jul 22, 04:10 UTC | 50m |
| 2026-07-21 | AMM → CAI | Jul 21, 22:50 UTC | Jul 21, 23:55 UTC | 1h 5m |
| 2026-07-21 | STN → AMM | Jul 21, 15:25 UTC | Jul 21, 20:10 UTC | 4h 45m |
| 2026-07-21 | AMM → STN | Jul 21, 08:55 UTC | Jul 21, 13:50 UTC | 4h 55m |
| 2026-07-20 | IST → AMM | Jul 20, 20:50 UTC | Jul 20, 22:35 UTC | 1h 45m |
| 2026-07-20 | - | Jul 20, 16:55 UTC | Jul 20, 18:50 UTC | 1h 55m |
| 2026-07-20 | TZX → ADJ | Jul 20, 13:25 UTC | Jul 20, 15:00 UTC | 1h 35m |
| 2026-07-20 | ADJ → TZX | Jul 20, 10:35 UTC | Jul 20, 12:05 UTC | 1h 30m |
| 2026-07-20 | - | Jul 20, 06:00 UTC | Jul 20, 09:15 UTC | 3h 15m |
| 2026-07-20 | - | Jul 20, 04:45 UTC | Jul 20, 05:05 UTC | 20m |
| 2026-07-19 | - | Jul 19, 23:20 UTC | Jul 20, 00:00 UTC | 40m |
| 2026-07-19 | - | Jul 19, 21:35 UTC | Jul 19, 22:05 UTC | 30m |
| 2026-07-19 | - | Jul 19, 15:00 UTC | Jul 19, 16:15 UTC | 1h 15m |
| 2026-07-19 | - | Jul 19, 12:05 UTC | Jul 19, 13:20 UTC | 1h 15m |
| 2026-07-19 | - | Jul 19, 07:05 UTC | Jul 19, 07:50 UTC | 45m |
| 2026-07-18 | - | Jul 18, 03:20 UTC | Jul 18, 04:05 UTC | 45m |
| 2026-07-17 | - | Jul 17, 23:30 UTC | Jul 18, 01:15 UTC | 1h 45m |
| 2026-07-17 | - | Jul 17, 19:35 UTC | Jul 17, 21:20 UTC | 1h 45m |
| 2026-07-17 | - | Jul 17, 14:35 UTC | Jul 17, 15:49 UTC | 1h 15m |
| 2026-07-17 | - | Jul 17, 11:45 UTC | Jul 17, 13:15 UTC | 1h 30m |
| 2026-07-17 | ADJ → ADJ | Jul 17, 06:29 UTC | Jul 17, 09:30 UTC | 3h 0m |
| 2026-07-17 | - | Jul 17, 04:59 UTC | Jul 17, 05:25 UTC | 25m |
| 2026-07-17 | - | Jul 17, 03:05 UTC | Jul 17, 03:30 UTC | 25m |
| 2026-07-16 | - | Jul 16, 23:29 UTC | Jul 17, 00:04 UTC | 35m |
| 2026-07-16 | - | Jul 16, 21:35 UTC | Jul 16, 22:10 UTC | 35m |
| 2026-07-16 | - | Jul 16, 19:14 UTC | Jul 16, 19:55 UTC | 40m |
| 2026-07-16 | - | Jul 16, 14:25 UTC | Jul 16, 14:55 UTC | 30m |
| 2026-07-16 | - | Jul 16, 11:50 UTC | Jul 16, 12:55 UTC | 1h 5m |
Specifications
| Registration | JY-RAN |
| Aircraft type | AIRBUS A-320neo (A20N) |
| Mode-S code | 74482E · 35044056 (octal) |
Looking for transponder-level data? View the Mode-S 74482E page for country allocation, callsign history, and ADS-B signal details.
JY-RAN frequently asked
What type of aircraft is JY-RAN?
JY-RAN is a AIRBUS A-320neo (ICAO type code A20N).
What is the Mode-S transponder code for JY-RAN?
JY-RAN broadcasts on Mode-S (ICAO 24-bit) address 74482E (octal 35044056). View the transponder page.
What route does JY-RAN typically fly?
JY-RAN most frequently flies between IST and AMM based on observed flights.
Where is JY-RAN right now?
JY-RAN is not currently being tracked; last seen Jul 26, 20:20 UTC.