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