Not currently tracked · last seen 3d ago
- Flights observed
- 50
- Avg flight time
- 2h 8m
- Typical route
- PKX → SVO
- Last seen
- 3d ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-05-27 | PEK → SHA | May 27, 09:45 UTC | May 27, 09:55 UTC | 10m |
| 2026-05-27 | SZX → SHA | May 27, 02:09 UTC | May 27, 02:19 UTC | 10m |
| 2026-05-26 | SHA → SZX | May 26, 12:54 UTC | May 26, 13:10 UTC | 15m |
| 2026-05-26 | SZX → SHA | May 26, 07:45 UTC | May 26, 07:55 UTC | 10m |
| 2026-05-26 | SHA → SZX | May 26, 04:35 UTC | May 26, 05:10 UTC | 35m |
| 2026-05-24 | - | May 24, 02:45 UTC | May 24, 02:55 UTC | 10m |
| 2026-05-23 | TSA → SHA | May 23, 09:40 UTC | May 23, 10:20 UTC | 40m |
| 2026-05-23 | SHA → TSA | May 23, 07:45 UTC | May 23, 08:15 UTC | 30m |
| 2026-05-23 | GMP → SHA | May 23, 03:10 UTC | May 23, 03:35 UTC | 25m |
| 2026-05-23 | SHA → GMP | May 23, 01:20 UTC | May 23, 02:00 UTC | 40m |
| 2026-05-19 | PEK → SHA | May 19, 07:20 UTC | May 19, 07:30 UTC | 10m |
| 2026-05-18 | PKX → SVO | May 18, 07:40 UTC | May 18, 08:20 UTC | 40m |
| 2026-05-18 | PKX → SVO | May 18, 04:25 UTC | May 18, 04:40 UTC | 15m |
| 2026-05-17 | SVO → PKX | May 17, 21:15 UTC | May 17, 21:25 UTC | 10m |
| 2026-05-17 | SVO → PKX | May 17, 18:20 UTC | May 17, 18:40 UTC | 20m |
| 2026-05-17 | PKX → SVO | May 17, 07:25 UTC | May 17, 08:05 UTC | 40m |
| 2026-05-16 | PKX → SVO | May 16, 07:25 UTC | May 16, 08:05 UTC | 40m |
| 2026-05-15 | PKX → SVO | May 15, 07:45 UTC | May 15, 08:20 UTC | 35m |
| 2026-05-13 | SVO → PKX | May 13, 07:45 UTC | May 13, 18:25 UTC | 10h 40m |
| 2026-05-12 | SVO → PKX | May 12, 17:55 UTC | May 13, 15:55 UTC | 22h 0m |
| 2026-05-12 | PKX → SVO | May 12, 07:35 UTC | May 12, 18:20 UTC | 10h 45m |
| 2026-05-10 | PKX → SVO | May 10, 06:20 UTC | May 10, 18:09 UTC | 11h 50m |
| 2026-05-09 | PKX → SVO | May 9, 07:35 UTC | May 10, 06:45 UTC | 23h 10m |
| 2026-05-09 | PKX → SVO | May 9, 04:05 UTC | May 9, 08:35 UTC | 4h 30m |
| 2026-05-08 | PKX → SVO | May 8, 04:29 UTC | May 8, 08:40 UTC | 4h 10m |
| 2026-05-07 | PKX → SVO | May 7, 04:30 UTC | May 7, 08:40 UTC | 4h 10m |
| 2026-05-05 | MFM → SHA | May 5, 12:20 UTC | May 5, 13:15 UTC | 55m |
| 2026-05-05 | SHA → MFM | May 5, 10:20 UTC | May 5, 10:30 UTC | 10m |
| 2026-05-05 | SHA → PEK | May 5, 03:15 UTC | May 5, 03:25 UTC | 10m |
| 2026-05-04 | SHA → PEK | May 4, 07:10 UTC | May 4, 07:25 UTC | 15m |
| 2026-05-03 | SHA → SZX | May 3, 15:00 UTC | May 3, 15:20 UTC | 20m |
| 2026-05-02 | PEK → SHA | May 2, 09:45 UTC | May 2, 09:55 UTC | 10m |
| 2026-05-01 | SHA → PEK | May 1, 04:50 UTC | May 1, 05:00 UTC | 10m |
| 2026-04-29 | PEK → SHA | Apr 29, 06:59 UTC | Apr 29, 07:10 UTC | 10m |
| 2026-04-23 | SHA → PEK | Apr 23, 04:55 UTC | Apr 23, 05:05 UTC | 10m |
| 2026-04-22 | HKG → SHA | Apr 22, 05:25 UTC | Apr 22, 06:35 UTC | 1h 10m |
| 2026-04-22 | SHA → HKG | Apr 22, 02:15 UTC | Apr 22, 03:30 UTC | 1h 15m |
| 2026-04-21 | SHA → PEK | Apr 21, 11:25 UTC | Apr 21, 11:40 UTC | 15m |
| 2026-04-21 | HKG → SHA | Apr 21, 06:00 UTC | Apr 21, 06:15 UTC | 15m |
| 2026-04-21 | HKG → SHA | Apr 21, 05:05 UTC | Apr 21, 05:25 UTC | 20m |
| 2026-04-21 | SHA → HKG | Apr 21, 03:20 UTC | Apr 21, 03:30 UTC | 10m |
| 2026-04-20 | CAN → SHA | Apr 20, 02:05 UTC | Apr 20, 02:15 UTC | 10m |
| 2026-04-19 | SZX → SHA | Apr 19, 07:50 UTC | Apr 19, 08:00 UTC | 10m |
| 2026-04-19 | SHA → SZX | Apr 19, 05:00 UTC | Apr 19, 05:25 UTC | 25m |
| 2026-04-17 | SZX → SHA | Apr 17, 02:00 UTC | Apr 17, 02:10 UTC | 10m |
| 2026-04-16 | - | Apr 16, 12:39 UTC | Apr 16, 13:05 UTC | 25m |
| 2026-04-16 | SHA → SZX | Apr 16, 04:40 UTC | Apr 16, 04:54 UTC | 15m |
| 2026-04-14 | - | Apr 14, 09:25 UTC | Apr 14, 09:50 UTC | 25m |
| 2026-04-14 | - | Apr 14, 07:45 UTC | Apr 14, 08:10 UTC | 25m |
| 2026-04-13 | - | Apr 13, 02:40 UTC | Apr 13, 02:50 UTC | 10m |
Specifications
| Registration | B-6095 |
| Aircraft type | AIRBUS A-330-300 (A333) |
| Mode-S code | 780094 · 36000224 (octal) |
Looking for transponder-level data? View the Mode-S 780094 page for country allocation, callsign history, and ADS-B signal details.
B-6095 frequently asked
What type of aircraft is B-6095?
B-6095 is a AIRBUS A-330-300 (ICAO type code A333).
What is the Mode-S transponder code for B-6095?
B-6095 broadcasts on Mode-S (ICAO 24-bit) address 780094 (octal 36000224). View the transponder page.
What route does B-6095 typically fly?
B-6095 most frequently flies between PKX and SVO based on observed flights.
Where is B-6095 right now?
B-6095 is not currently being tracked; last seen 3d ago.