Flight
NOS613
Flight history and live tracking for NOS613, operated by Neos. Recent flights from the PlaneTrack independent receiver network, with departure and arrival times, aircraft used, and a real-time position feed.
Route
| Airline | Neos |
| Observed route | LIRF → LGST |
Flight history 13 flights since Jun 2026
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-09-27estimated | ? | ? | 02:52Z | 09:14Z | 6h 21m | EI-NEO |
| 2026-09-26estimated | LIRF | LGST | 01:40 CEST | 02:58 EEST | 0h 17m | EI-NEO |
| 2026-09-12estimated | LIRF | LGST | 22:10 CEST | 02:28 EEST | 3h 17m | EI-NYE |
| 2026-09-05estimated | LIRF | LGST | 17:33 CEST | 23:22 EEST | 4h 48m | EI-NEO |
Earlier flights (9) - back to 2026-06-27
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-08-29estimated | LIRF | LGST | 20:01 CEST | 01:08 EEST | 4h 06m | EI-XIN |
| 2026-08-22estimated | LIRF | LGST | 17:26 CEST | 22:14 EEST | 3h 47m | EI-NEO |
| 2026-08-15estimated | LIRF | LGST | 20:12 CEST | 01:44 EEST | 4h 31m | EI-XIN |
| 2026-07-18estimated | LIRF | LGST | 20:08 CEST | 00:34 EEST | 3h 26m | EI-NEO |
| 2026-07-11estimated | LIRF | LGST | 17:42 CEST | 22:54 EEST | 4h 11m | EI-NYE |
| 2026-07-04estimated | ? | ? | 22:40Z | 23:16Z | 0h 35m | EI-NUA |
| 2026-07-04estimated | LIRF | LGST | 20:36 CEST | 22:26 EEST | 0h 50m | EI-NUA |
| 2026-06-27estimated | ? | ? | 19:10Z | 19:56Z | 0h 46m | EI-NEO |
| 2026-06-27estimated | LIRF | LGST | 17:26 CEST | 18:52 EEST | 0h 25m | EI-NEO |
Times are local to each airport. Hover for UTC. Flights marked estimated were completed with route prediction or partial coverage; partial records have a confirmed departure but no reliable arrival fix.
Follow this flight
Get an email when NOS613 flies + if it runs late.
Data access
Live positions and 365-day history for this flight are available through the PlaneTrack API (commercial use from $29/month) and as one-off CSV extracts from our archive (from $9.99, with a free one-day sample). Questions: [email protected]