sensors Mode-S transponder
4080F1
ICAO 24-bit transponder address · allocated to United Kingdom
Currently assigned to G-ONEG · BOEING 777-200LR
- Hex
- 4080F1
- Octal
- 20100361
- Decimal
- 4,227,313
- Country
- GB
- Tail
- G-ONEG
- Type
- B77L
- Flights observed
- 122
- Distinct callsigns
- 20
- Country
- GB
- Last broadcast
- 3h ago
Last known position
Country allocation
The ICAO 24-bit address 4080F1 falls within the block assigned to United Kingdom (GB) by ICAO Annex 10, Volume III. Every aircraft registered in United Kingdom receives a permanent address from this block at the time of registration; the address stays with the airframe even if the aircraft is re-registered to a different operator within the country.
Callsign history 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| AZG9602 | Sakaviaservice | 10 | 2026-05-30 |
| HGO1720 | - | 9 | 2026-05-30 |
| HGO1782 | - | 8 | 2026-05-31 |
| HGO1781 | - | 8 | 2026-05-31 |
| HGO1710 | One Air | 8 | 2026-06-01 |
| AZG9601 | Sakaviaservice | 8 | 2026-05-30 |
| AZG265 | Sakaviaservice | 8 | 2026-05-22 |
| HGO695 | - | 7 | 2026-04-14 |
| AZG713 | Sakaviaservice | 7 | 2026-06-02 |
| HGO697 | - | 6 | 2026-04-16 |
| AZG744 | Sakaviaservice | 5 | 2026-05-21 |
| AZG743 | Sakaviaservice | 5 | 2026-05-14 |
| AZG751 | Sakaviaservice | 4 | 2026-05-28 |
| AZG261 | Sakaviaservice | 4 | 2026-05-06 |
| HGO188 | - | 3 | 2026-04-17 |
| AZG761 | Sakaviaservice | 3 | 2026-05-09 |
| AZG714 | Sakaviaservice | 3 | 2026-05-26 |
| AZG753 | Sakaviaservice | 2 | 2026-05-29 |
| AZG721 | Sakaviaservice | 2 | 2026-05-19 |
| HGO102 | - | 1 | 2026-05-23 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | AZG713 | BHX → GYD | Jun 2, 19:20 UTC | Jun 2, 19:35 UTC | 15m |
| 2026-06-02 | AZG713 | BHX → GYD | Jun 2, 09:15 UTC | Jun 2, 14:00 UTC | 4h 45m |
| 2026-06-01 | HGO1710 | HKG → GYD | Jun 1, 20:55 UTC | Jun 1, 21:10 UTC | 15m |
| 2026-05-31 | HGO1782 | - | May 31, 22:30 UTC | Jun 1, 16:35 UTC | 18h 5m |
| 2026-05-31 | HGO1781 | - | May 31, 13:40 UTC | May 31, 18:50 UTC | 5h 10m |
| 2026-05-30 | HGO1720 | - | May 30, 23:15 UTC | May 30, 23:40 UTC | 25m |
| 2026-05-30 | AZG9602 | OSL → GYD | May 30, 09:05 UTC | May 30, 13:10 UTC | 4h 5m |
| 2026-05-30 | AZG9601 | JFK → OSL | May 30, 05:30 UTC | May 30, 07:10 UTC | 1h 40m |
| 2026-05-29 | AZG753 | GYD → LGG | May 29, 08:20 UTC | May 30, 02:25 UTC | 18h 5m |
| 2026-05-29 | AZG753 | GYD → LGG | May 29, 07:05 UTC | May 30, 02:25 UTC | 19h 20m |
| 2026-05-28 | AZG751 | GYD → GYD | May 28, 23:20 UTC | May 29, 04:00 UTC | 4h 40m |
| 2026-05-28 | AZG732 | LGG → GYD | May 28, 16:20 UTC | May 28, 20:10 UTC | 3h 50m |
| 2026-05-27 | AZG731 | GYD → LGG | May 27, 20:45 UTC | May 28, 13:20 UTC | 16h 35m |
| 2026-05-27 | HGO1781 | - | May 27, 14:05 UTC | May 27, 19:00 UTC | 4h 55m |
| 2026-05-26 | AZG714 | LGG → GYD | May 26, 16:45 UTC | May 26, 20:45 UTC | 4h 0m |
| 2026-05-26 | AZG713 | BHX → GYD | May 26, 09:29 UTC | May 26, 13:45 UTC | 4h 15m |
| 2026-05-25 | HGO1710 | HKG → GYD | May 25, 21:04 UTC | May 25, 21:19 UTC | 15m |
| 2026-05-25 | HGO1720 | - | May 25, 17:25 UTC | May 25, 17:55 UTC | 30m |
| 2026-05-24 | HGO1782 | - | May 24, 21:10 UTC | May 24, 23:46 UTC | 2h 36m |
| 2026-05-24 | HGO1781 | - | May 24, 12:55 UTC | May 24, 17:40 UTC | 4h 45m |
| 2026-05-24 | HGO1710 | HKG → GYD | May 24, 02:15 UTC | May 24, 02:30 UTC | 15m |
| 2026-05-23 | HGO1720 | - | May 23, 22:35 UTC | May 23, 23:05 UTC | 30m |
| 2026-05-23 | AZG9602 | OSL → GYD | May 23, 08:15 UTC | May 23, 12:35 UTC | 4h 20m |
| 2026-05-23 | HGO102 | - | May 23, 04:10 UTC | May 23, 05:55 UTC | 1h 45m |
| 2026-05-22 | HGO101 | - | May 22, 15:35 UTC | May 22, 15:55 UTC | 20m |
| 2026-05-22 | AZG265 | GYD → LUX | May 22, 09:20 UTC | May 22, 13:35 UTC | 4h 15m |
| 2026-05-22 | AZG742 | MXP → GYD | May 22, 00:45 UTC | May 22, 04:50 UTC | 4h 5m |
| 2026-05-21 | AZG744 | LGG → LGG | May 21, 08:05 UTC | May 21, 21:10 UTC | 13h 5m |
| 2026-05-20 | AZG9602 | OSL → GYD | May 20, 16:40 UTC | May 21, 05:50 UTC | 13h 10m |
| 2026-05-20 | AZG9601 | JFK → OSL | May 20, 12:40 UTC | May 20, 14:20 UTC | 1h 40m |
| 2026-05-19 | AZG265 | GYD → LUX | May 19, 22:00 UTC | May 20, 10:30 UTC | 12h 31m |
| 2026-05-19 | AZG721 | GYD → LGG | May 19, 04:55 UTC | May 19, 17:20 UTC | 12h 25m |
| 2026-05-18 | AZG713 | BHX → GYD | May 18, 20:30 UTC | May 19, 00:50 UTC | 4h 20m |
| 2026-05-18 | HGO1710 | HKG → GYD | May 18, 09:10 UTC | May 18, 09:25 UTC | 15m |
| 2026-05-18 | HGO1720 | - | May 18, 04:30 UTC | May 18, 05:00 UTC | 30m |
| 2026-05-17 | HGO1782 | - | May 17, 10:10 UTC | May 17, 14:35 UTC | 4h 25m |
| 2026-05-16 | HGO1781 | - | May 16, 15:31 UTC | May 17, 06:55 UTC | 15h 25m |
| 2026-05-15 | AZG9602 | OSL → GYD | May 15, 19:20 UTC | May 16, 12:16 UTC | 16h 56m |
| 2026-05-15 | AZG9601 | JFK → OSL | May 15, 15:30 UTC | May 15, 17:10 UTC | 1h 40m |
| 2026-05-15 | AZG265 | GYD → LUX | May 15, 09:30 UTC | May 15, 13:50 UTC | 4h 20m |
| 2026-05-15 | AZG744 | LGG → LGG | May 15, 01:55 UTC | May 15, 05:55 UTC | 4h 0m |
| 2026-05-14 | AZG743 | GYD → LGG | May 14, 11:20 UTC | May 14, 23:15 UTC | 11h 55m |
| 2026-05-14 | AZG284 | GYD → VIE | May 14, 03:35 UTC | May 14, 07:05 UTC | 3h 30m |
| 2026-05-13 | AZG9602 | OSL → GYD | May 13, 18:40 UTC | May 13, 23:05 UTC | 4h 25m |
| 2026-05-13 | AZG9601 | JFK → OSL | May 13, 14:15 UTC | May 13, 15:50 UTC | 1h 35m |
| 2026-05-12 | AZG265 | GYD → LUX | May 12, 21:45 UTC | May 13, 11:55 UTC | 14h 10m |
| 2026-05-12 | AZG721 | GYD → LGG | May 12, 13:51 UTC | May 12, 18:30 UTC | 4h 40m |
| 2026-05-12 | AZG714 | LGG → GYD | May 12, 04:50 UTC | May 12, 08:45 UTC | 3h 55m |
| 2026-05-11 | AZG713 | BHX → GYD | May 11, 20:50 UTC | May 11, 22:05 UTC | 1h 15m |
| 2026-05-11 | HGO1710 | HKG → GYD | May 11, 09:25 UTC | May 11, 09:40 UTC | 15m |
About Mode-S
A Mode-S transponder code (also called an "ICAO 24-bit address" or "hex code") is a 6-character hexadecimal identifier permanently assigned to an aircraft when it's first registered. Unlike callsigns (which change with each flight) or registrations (which can change if an aircraft is sold internationally), the Mode-S address stays with the airframe for the life of the aircraft in that country.
Every ADS-B transmission from an aircraft includes its Mode-S address, making it the most reliable way to identify a specific airframe. Flight-tracking services like Apparatus use the Mode-S address as the primary key for tying position broadcasts, callsigns, and ownership records together.
Prefer a tail-number view? See the G-ONEG page for operator, model, and routing details .