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