Not currently tracked · last seen 13h ago
- Flights observed
- 320 showing last 50
- Avg flight time
- 2h 19m
- Typical route
- HEL → CPH
- Last seen
- 13h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-13 | HEL → CPH | Jul 13, 19:45 UTC | Jul 13, 21:05 UTC | 1h 20m |
| 2026-07-13 | - | Jul 13, 16:45 UTC | Jul 13, 18:45 UTC | 2h 0m |
| 2026-07-13 | HEL → BUD | Jul 13, 13:45 UTC | Jul 13, 15:50 UTC | 2h 5m |
| 2026-07-13 | - | Jul 13, 09:15 UTC | Jul 13, 12:20 UTC | 3h 5m |
| 2026-07-13 | - | Jul 13, 04:45 UTC | Jul 13, 07:45 UTC | 3h 0m |
| 2026-07-12 | CPH → HEL | Jul 12, 18:25 UTC | Jul 12, 19:40 UTC | 1h 15m |
| 2026-07-12 | HEL → CPH | Jul 12, 16:05 UTC | Jul 12, 17:30 UTC | 1h 25m |
| 2026-07-12 | ARN → HEL | Jul 12, 13:50 UTC | Jul 12, 14:30 UTC | 40m |
| 2026-07-12 | HEL → ARN | Jul 12, 12:05 UTC | Jul 12, 12:50 UTC | 45m |
| 2026-07-12 | - | Jul 12, 08:01 UTC | Jul 12, 10:35 UTC | 2h 35m |
| 2026-07-12 | - | Jul 12, 04:10 UTC | Jul 12, 06:35 UTC | 2h 25m |
| 2026-07-11 | CPH → HEL | Jul 11, 17:35 UTC | Jul 11, 19:00 UTC | 1h 25m |
| 2026-07-11 | HEL → CPH | Jul 11, 15:00 UTC | Jul 11, 16:15 UTC | 1h 15m |
| 2026-07-11 | BUD → HEL | Jul 11, 10:15 UTC | Jul 11, 12:20 UTC | 2h 5m |
| 2026-07-11 | HEL → BUD | Jul 11, 07:25 UTC | Jul 11, 09:25 UTC | 2h 0m |
| 2026-07-11 | - | Jul 11, 05:40 UTC | Jul 11, 06:20 UTC | 40m |
| 2026-07-11 | HEL → ARN | Jul 11, 04:05 UTC | Jul 11, 04:45 UTC | 40m |
| 2026-07-10 | NCE → HEL | Jul 10, 17:25 UTC | Jul 10, 20:35 UTC | 3h 10m |
| 2026-07-10 | HEL → NCE | Jul 10, 13:20 UTC | Jul 10, 16:15 UTC | 2h 55m |
| 2026-07-10 | DUB → HEL | Jul 10, 09:10 UTC | Jul 10, 11:50 UTC | 2h 40m |
| 2026-07-10 | - | Jul 10, 05:15 UTC | Jul 10, 08:00 UTC | 2h 45m |
| 2026-07-09 | BUD → HEL | Jul 9, 17:20 UTC | Jul 9, 19:20 UTC | 2h 0m |
| 2026-07-09 | - | Jul 9, 14:15 UTC | Jul 9, 16:10 UTC | 1h 55m |
| 2026-07-09 | - | Jul 9, 11:15 UTC | Jul 9, 12:35 UTC | 1h 20m |
| 2026-07-09 | HEL → CPH | Jul 9, 08:35 UTC | Jul 9, 09:50 UTC | 1h 15m |
| 2026-07-09 | CPH → HEL | Jul 9, 06:10 UTC | Jul 9, 07:30 UTC | 1h 20m |
| 2026-07-09 | HEL → CPH | Jul 9, 03:45 UTC | Jul 9, 05:00 UTC | 1h 15m |
| 2026-07-08 | CPH → HEL | Jul 8, 21:10 UTC | Jul 8, 22:35 UTC | 1h 25m |
| 2026-07-08 | BOD → CPH | Jul 8, 17:25 UTC | Jul 8, 19:35 UTC | 2h 10m |
| 2026-07-08 | CPH → BOD | Jul 8, 14:15 UTC | Jul 8, 16:10 UTC | 1h 55m |
| 2026-07-08 | - | Jul 8, 09:30 UTC | Jul 8, 12:25 UTC | 2h 55m |
| 2026-07-08 | - | Jul 8, 05:30 UTC | Jul 8, 08:00 UTC | 2h 30m |
| 2026-07-07 | DUB → CPH | Jul 7, 19:30 UTC | Jul 7, 21:10 UTC | 1h 40m |
| 2026-07-07 | - | Jul 7, 16:25 UTC | Jul 7, 18:20 UTC | 1h 55m |
| 2026-07-07 | NCE → CPH | Jul 7, 13:05 UTC | Jul 7, 15:15 UTC | 2h 10m |
| 2026-07-07 | - | Jul 7, 09:50 UTC | Jul 7, 11:45 UTC | 1h 55m |
| 2026-07-06 | - | Jul 6, 20:50 UTC | Jul 7, 00:45 UTC | 3h 55m |
| 2026-07-06 | - | Jul 6, 16:05 UTC | Jul 6, 19:30 UTC | 3h 25m |
| 2026-07-06 | - | Jul 6, 10:15 UTC | Jul 6, 14:20 UTC | 4h 5m |
| 2026-07-06 | - | Jul 6, 05:10 UTC | Jul 6, 08:45 UTC | 3h 35m |
| 2026-07-05 | - | Jul 5, 20:05 UTC | Jul 5, 23:35 UTC | 3h 30m |
| 2026-07-05 | - | Jul 5, 16:00 UTC | Jul 5, 19:00 UTC | 3h 0m |
| 2026-07-05 | - | Jul 5, 10:30 UTC | Jul 5, 13:40 UTC | 3h 10m |
| 2026-07-05 | BLL → CHQ | Jul 5, 05:50 UTC | Jul 5, 08:50 UTC | 3h 0m |
| 2026-07-04 | - | Jul 4, 19:00 UTC | Jul 4, 21:35 UTC | 2h 35m |
| 2026-07-04 | - | Jul 4, 15:05 UTC | Jul 4, 17:40 UTC | 2h 35m |
| 2026-07-04 | FAO → BLL | Jul 4, 10:10 UTC | Jul 4, 13:20 UTC | 3h 10m |
| 2026-07-04 | - | Jul 4, 05:10 UTC | Jul 4, 08:25 UTC | 3h 15m |
| 2026-07-03 | - | Jul 3, 11:45 UTC | Jul 3, 16:05 UTC | 4h 20m |
| 2026-07-03 | - | Jul 3, 05:50 UTC | Jul 3, 10:25 UTC | 4h 35m |
Specifications
| Registration | OY-JZO |
| Aircraft type | BOEING 737-800 (B738) |
| Mode-S code | 45AB4F · 21325517 (octal) |
Looking for transponder-level data? View the Mode-S 45AB4F page for country allocation, callsign history, and ADS-B signal details.
OY-JZO frequently asked
What type of aircraft is OY-JZO?
OY-JZO is a BOEING 737-800 (ICAO type code B738).
What is the Mode-S transponder code for OY-JZO?
OY-JZO broadcasts on Mode-S (ICAO 24-bit) address 45AB4F (octal 21325517). View the transponder page.
What route does OY-JZO typically fly?
OY-JZO most frequently flies between HEL and CPH based on observed flights.
Where is OY-JZO right now?
OY-JZO is not currently being tracked; last seen 13h ago.