Not currently tracked · last seen 4h ago
- Flights observed
- 256 showing last 50
- Avg flight time
- 1h 18m
- Typical route
- MUC → ATH
- Last seen
- 4h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-14 | MUC → ATH | Jul 14, 04:35 UTC | Jul 14, 06:40 UTC | 2h 5m |
| 2026-07-14 | CGN → MUC | Jul 14, 02:25 UTC | Jul 14, 03:10 UTC | 45m |
| 2026-07-13 | MUC → CGN | Jul 13, 21:30 UTC | Jul 13, 22:30 UTC | 1h 0m |
| 2026-07-13 | ATH → MUC | Jul 13, 17:50 UTC | Jul 13, 20:00 UTC | 2h 10m |
| 2026-07-13 | MUC → ATH | Jul 13, 04:25 UTC | Jul 13, 06:25 UTC | 2h 0m |
| 2026-07-13 | CGN → MUC | Jul 13, 02:20 UTC | Jul 13, 03:05 UTC | 45m |
| 2026-07-10 | MUC → CGN | Jul 10, 21:10 UTC | Jul 10, 21:55 UTC | 45m |
| 2026-07-10 | ATH → MUC | Jul 10, 17:45 UTC | Jul 10, 19:55 UTC | 2h 10m |
| 2026-07-10 | MUC → ATH | Jul 10, 04:40 UTC | Jul 10, 06:35 UTC | 1h 55m |
| 2026-07-10 | CGN → MUC | Jul 10, 02:40 UTC | Jul 10, 03:25 UTC | 45m |
| 2026-07-09 | MUC → CGN | Jul 9, 21:40 UTC | Jul 9, 22:30 UTC | 50m |
| 2026-07-09 | ATH → MUC | Jul 9, 17:50 UTC | Jul 9, 20:15 UTC | 2h 25m |
| 2026-07-09 | MUC → ATH | Jul 9, 04:25 UTC | Jul 9, 06:20 UTC | 1h 55m |
| 2026-07-09 | CGN → MUC | Jul 9, 02:30 UTC | Jul 9, 03:15 UTC | 45m |
| 2026-07-08 | MUC → CGN | Jul 8, 21:35 UTC | Jul 8, 22:35 UTC | 1h 0m |
| 2026-07-08 | ATH → MUC | Jul 8, 18:00 UTC | Jul 8, 20:25 UTC | 2h 25m |
| 2026-07-08 | MUC → ATH | Jul 8, 04:30 UTC | Jul 8, 06:20 UTC | 1h 50m |
| 2026-07-08 | CGN → MUC | Jul 8, 02:35 UTC | Jul 8, 03:20 UTC | 45m |
| 2026-07-07 | MUC → CGN | Jul 7, 21:10 UTC | Jul 7, 21:55 UTC | 45m |
| 2026-07-07 | ATH → MUC | Jul 7, 17:50 UTC | Jul 7, 20:00 UTC | 2h 10m |
| 2026-07-07 | MUC → ATH | Jul 7, 04:30 UTC | Jul 7, 06:30 UTC | 2h 0m |
| 2026-07-07 | CGN → MUC | Jul 7, 02:35 UTC | Jul 7, 03:20 UTC | 45m |
| 2026-07-06 | - | Jul 6, 21:25 UTC | Jul 6, 22:15 UTC | 50m |
| 2026-07-06 | MUC → MUC | Jul 6, 21:05 UTC | Jul 6, 21:10 UTC | 5m |
| 2026-07-06 | ATH → MUC | Jul 6, 18:00 UTC | Jul 6, 20:10 UTC | 2h 10m |
| 2026-07-06 | MUC → ATH | Jul 6, 04:20 UTC | Jul 6, 06:15 UTC | 1h 55m |
| 2026-07-06 | CGN → MUC | Jul 6, 02:25 UTC | Jul 6, 03:10 UTC | 45m |
| 2026-07-03 | LYS → CGN | Jul 3, 22:40 UTC | Jul 3, 23:40 UTC | 1h 0m |
| 2026-07-03 | - | Jul 3, 18:35 UTC | Jul 3, 19:15 UTC | 40m |
| 2026-07-03 | LYS → TLS | Jul 3, 04:05 UTC | Jul 3, 04:45 UTC | 40m |
| 2026-07-03 | CGN → LYS | Jul 3, 01:45 UTC | Jul 3, 02:40 UTC | 55m |
| 2026-07-02 | CDG → CGN | Jul 2, 21:40 UTC | Jul 2, 22:35 UTC | 55m |
| 2026-07-02 | BOD → CDG | Jul 2, 19:20 UTC | Jul 2, 20:20 UTC | 1h 0m |
| 2026-07-02 | - | Jul 2, 03:40 UTC | Jul 2, 04:25 UTC | 45m |
| 2026-07-02 | CGN → CDG | Jul 2, 00:40 UTC | Jul 2, 01:20 UTC | 40m |
| 2026-07-01 | LYS → CGN | Jul 1, 20:30 UTC | Jul 1, 21:35 UTC | 1h 5m |
| 2026-07-01 | - | Jul 1, 18:40 UTC | Jul 1, 19:20 UTC | 40m |
| 2026-07-01 | LYS → TLS | Jul 1, 04:15 UTC | Jul 1, 05:00 UTC | 45m |
| 2026-07-01 | CGN → LYS | Jul 1, 01:50 UTC | Jul 1, 02:50 UTC | 1h 0m |
| 2026-06-30 | MUC → CGN | Jun 30, 21:20 UTC | Jun 30, 22:00 UTC | 40m |
| 2026-06-30 | ATH → MUC | Jun 30, 17:50 UTC | Jun 30, 20:05 UTC | 2h 15m |
| 2026-06-30 | MUC → ATH | Jun 30, 04:45 UTC | Jun 30, 06:55 UTC | 2h 10m |
| 2026-06-30 | CGN → MUC | Jun 30, 02:35 UTC | Jun 30, 03:20 UTC | 45m |
| 2026-06-29 | ATH → CGN | Jun 29, 18:44 UTC | Jun 29, 21:14 UTC | 2h 30m |
| 2026-06-29 | MUC → ATH | Jun 29, 04:55 UTC | Jun 29, 06:59 UTC | 2h 5m |
| 2026-06-29 | CGN → MUC | Jun 29, 02:20 UTC | Jun 29, 03:10 UTC | 50m |
| 2026-06-26 | MUC → CGN | Jun 26, 20:59 UTC | Jun 26, 21:55 UTC | 55m |
| 2026-06-26 | ATH → MUC | Jun 26, 17:59 UTC | Jun 26, 20:04 UTC | 2h 5m |
| 2026-06-26 | MUC → ATH | Jun 26, 04:34 UTC | Jun 26, 06:39 UTC | 2h 5m |
| 2026-06-26 | CGN → MUC | Jun 26, 02:24 UTC | Jun 26, 03:15 UTC | 50m |
Specifications
| Registration | OY-SRU |
| Aircraft type | BOEING 767-300 (B763) |
| Mode-S code | 45CE55 · 21347125 (octal) |
Looking for transponder-level data? View the Mode-S 45CE55 page for country allocation, callsign history, and ADS-B signal details.
OY-SRU frequently asked
What type of aircraft is OY-SRU?
OY-SRU is a BOEING 767-300 (ICAO type code B763).
What is the Mode-S transponder code for OY-SRU?
OY-SRU broadcasts on Mode-S (ICAO 24-bit) address 45CE55 (octal 21347125). View the transponder page.
What route does OY-SRU typically fly?
OY-SRU most frequently flies between MUC and ATH based on observed flights.
Where is OY-SRU right now?
OY-SRU is not currently being tracked; last seen 4h ago.