Not currently tracked · last seen 4d ago
- Flights observed
- 39
- Avg flight time
- 42m
- Typical route
- -
- Last seen
- 4d ago
Last known area
Recent flights last 39
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-26 | - | Jul 26, 18:05 UTC | Jul 26, 18:25 UTC | 20m |
| 2026-07-26 | - | Jul 26, 16:15 UTC | Jul 26, 17:20 UTC | 1h 5m |
| 2026-07-19 | - | Jul 19, 20:10 UTC | Jul 19, 22:25 UTC | 2h 15m |
| 2026-07-19 | - | Jul 19, 17:50 UTC | Jul 19, 18:10 UTC | 20m |
| 2026-07-19 | - | Jul 19, 16:00 UTC | Jul 19, 16:20 UTC | 20m |
| 2026-07-19 | - | Jul 19, 01:00 UTC | Jul 19, 01:30 UTC | 30m |
| 2026-07-18 | - | Jul 18, 22:05 UTC | Jul 18, 22:15 UTC | 10m |
| 2026-07-18 | - | Jul 18, 16:20 UTC | Jul 18, 18:35 UTC | 2h 15m |
| 2026-07-17 | - | Jul 17, 01:49 UTC | Jul 17, 02:05 UTC | 15m |
| 2026-07-16 | - | Jul 16, 13:10 UTC | Jul 16, 13:30 UTC | 20m |
| 2026-07-16 | - | Jul 16, 02:30 UTC | Jul 16, 03:15 UTC | 45m |
| 2026-07-11 | - | Jul 11, 23:00 UTC | Jul 12, 01:30 UTC | 2h 30m |
| 2026-07-02 | - | Jul 2, 22:35 UTC | Jul 3, 01:05 UTC | 2h 30m |
| 2026-07-01 | - | Jul 1, 23:00 UTC | Jul 1, 23:15 UTC | 15m |
| 2026-07-01 | - | Jul 1, 01:05 UTC | Jul 1, 01:45 UTC | 40m |
| 2026-06-30 | - | Jun 30, 21:15 UTC | Jun 30, 22:00 UTC | 45m |
| 2026-06-30 | - | Jun 30, 20:25 UTC | Jun 30, 20:35 UTC | 10m |
| 2026-06-30 | - | Jun 30, 16:50 UTC | Jun 30, 17:05 UTC | 15m |
| 2026-06-28 | - | Jun 28, 20:54 UTC | Jun 28, 21:45 UTC | 50m |
| 2026-06-28 | - | Jun 28, 17:50 UTC | Jun 28, 18:34 UTC | 45m |
| 2026-06-24 | - | Jun 24, 01:30 UTC | Jun 24, 01:55 UTC | 25m |
| 2026-05-29 | - | May 29, 23:00 UTC | May 29, 23:55 UTC | 55m |
| 2026-05-28 | - | May 28, 21:10 UTC | May 28, 21:25 UTC | 15m |
| 2026-05-26 | - | May 26, 23:10 UTC | May 26, 23:35 UTC | 25m |
| 2026-05-26 | - | May 26, 19:15 UTC | May 26, 19:50 UTC | 35m |
| 2026-05-26 | - | May 26, 17:39 UTC | May 26, 17:55 UTC | 15m |
| 2026-05-26 | - | May 26, 16:30 UTC | May 26, 16:40 UTC | 10m |
| 2026-05-26 | - | May 26, 02:44 UTC | May 26, 03:00 UTC | 15m |
| 2026-05-26 | - | May 26, 01:40 UTC | May 26, 02:00 UTC | 20m |
| 2026-05-24 | - | May 24, 23:40 UTC | May 24, 23:46 UTC | 6m |
| 2026-05-24 | - | May 24, 02:25 UTC | May 24, 02:55 UTC | 30m |
| 2026-05-10 | - | May 10, 21:54 UTC | May 10, 22:49 UTC | 55m |
| 2026-05-09 | - | May 9, 23:35 UTC | May 10, 00:49 UTC | 1h 15m |
| 2026-05-09 | - | May 9, 21:09 UTC | May 9, 21:34 UTC | 25m |
| 2026-04-27 | - | Apr 27, 00:20 UTC | Apr 27, 01:05 UTC | 45m |
| 2026-04-24 | - | Apr 24, 22:05 UTC | Apr 24, 23:35 UTC | 1h 30m |
| 2026-04-24 | - | Apr 24, 20:55 UTC | Apr 24, 21:05 UTC | 10m |
| 2026-04-24 | - | Apr 24, 18:25 UTC | Apr 24, 19:00 UTC | 35m |
| 2026-04-23 | - | Apr 23, 21:05 UTC | Apr 23, 21:15 UTC | 10m |
Specifications
| Registration | N262GB |
| Operator | GAME COMPOSITES LLC |
| Mode-S code | A28703 · 50503403 (octal) |
Looking for transponder-level data? View the Mode-S A28703 page for country allocation, callsign history, and ADS-B signal details.
N262GB frequently asked
Who operates N262GB?
N262GB is operated by GAME COMPOSITES LLC.
What is the Mode-S transponder code for N262GB?
N262GB broadcasts on Mode-S (ICAO 24-bit) address A28703 (octal 50503403). View the transponder page.
Where is N262GB right now?
N262GB is not currently being tracked; last seen 4d ago.