sensors Mode-S transponder
406F74
ICAO 24-bit transponder address · allocated to United Kingdom
Currently assigned to G-ZBKH · BOEING 787-9 Dreamliner
- Hex
- 406F74
- Octal
- 20067564
- Decimal
- 4,222,836
- Country
- GB
- Tail
- G-ZBKH
- Type
- B789
- Flights observed
- 168
- Distinct callsigns
- 20
- Country
- GB
- Last broadcast
- 9d ago
Last known position
Country allocation
The ICAO 24-bit address 406F74 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 |
|---|---|---|---|
| BAW16 | British Airways | 27 | 2026-06-30 |
| BAW168 | - | 25 | 2026-06-28 |
| BAW15 | British Airways | 25 | 2026-06-29 |
| BAW169 | - | 20 | 2026-06-27 |
| BAW6 | - | 9 | 2026-07-04 |
| BAW5 | British Airways | 8 | 2026-07-03 |
| BAW33 | British Airways | 7 | 2026-06-18 |
| BAW34 | - | 5 | 2026-06-18 |
| BAW60 | - | 4 | 2026-06-16 |
| BAW36 | British Airways | 4 | 2026-04-18 |
| BAW243 | British Airways | 4 | 2026-06-11 |
| BAW242 | - | 4 | 2026-06-12 |
| BAW35 | British Airways | 3 | 2026-04-17 |
| BAW271 | British Airways | 3 | 2026-06-15 |
| BAW270 | - | 3 | 2026-06-16 |
| BAW81V | - | 2 | 2026-07-01 |
| BAW26E | - | 2 | 2026-07-01 |
| BAW250 | British Airways | 2 | 2026-05-11 |
| BAW130 | - | 2 | 2026-07-02 |
| BAW9ZY | British Airways | 1 | 2026-05-20 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-05 | BAW9174 | - | Jul 5, 07:15 UTC | Jul 5, 07:45 UTC | 30m |
| 2026-07-04 | BAW6 | HND → LHR | Jul 4, 04:20 UTC | Jul 4, 18:10 UTC | 13h 50m |
| 2026-07-03 | BAW5 | LHR → NRT | Jul 3, 12:30 UTC | Jul 4, 01:15 UTC | 12h 45m |
| 2026-07-02 | BAW130 | - | Jul 2, 23:20 UTC | Jul 3, 08:40 UTC | 9h 20m |
| 2026-07-02 | BAW130 | - | Jul 2, 22:15 UTC | Jul 2, 22:35 UTC | 20m |
| 2026-07-02 | BAW131 | - | Jul 2, 09:40 UTC | Jul 2, 18:55 UTC | 9h 15m |
| 2026-07-01 | BAW81V | - | Jul 1, 20:45 UTC | Jul 2, 05:25 UTC | 8h 40m |
| 2026-07-01 | BAW26E | - | Jul 1, 08:35 UTC | Jul 1, 18:15 UTC | 9h 40m |
| 2026-06-30 | BAW16 | SIN → LHR | Jun 30, 15:00 UTC | Jul 1, 04:05 UTC | 13h 5m |
| 2026-06-30 | BAW16 | SIN → LHR | Jun 30, 05:00 UTC | Jun 30, 12:50 UTC | 7h 50m |
| 2026-06-29 | BAW15 | SIN → SYD | Jun 29, 18:55 UTC | Jun 29, 19:29 UTC | 35m |
| 2026-06-29 | BAW15 | SIN → SYD | Jun 29, 12:34 UTC | Jun 29, 12:45 UTC | 10m |
| 2026-06-28 | BAW15 | SIN → SYD | Jun 28, 21:34 UTC | Jun 29, 10:20 UTC | 12h 45m |
| 2026-06-28 | BAW168 | - | Jun 28, 05:24 UTC | Jun 28, 18:19 UTC | 12h 55m |
| 2026-06-27 | BAW168 | - | Jun 27, 17:20 UTC | Jun 28, 17:00 UTC | 23h 40m |
| 2026-06-27 | BAW169 | - | Jun 27, 15:05 UTC | Jun 28, 14:19 UTC | 23h 15m |
| 2026-06-27 | BAW169 | - | Jun 27, 13:49 UTC | Jun 28, 13:00 UTC | 23h 10m |
| 2026-06-26 | BAW16 | SIN → LHR | Jun 26, 15:05 UTC | Jun 27, 04:09 UTC | 13h 5m |
| 2026-06-26 | BAW16 | SIN → LHR | Jun 26, 12:29 UTC | Jun 26, 12:39 UTC | 10m |
| 2026-06-26 | BAW16 | SIN → LHR | Jun 26, 04:59 UTC | Jun 26, 05:35 UTC | 35m |
| 2026-06-25 | BAW15 | SIN → SYD | Jun 25, 12:40 UTC | Jun 25, 19:39 UTC | 7h 0m |
| 2026-06-24 | BAW15 | SIN → SYD | Jun 24, 22:19 UTC | Jun 25, 10:25 UTC | 12h 5m |
| 2026-06-24 | BAW168 | - | Jun 24, 04:59 UTC | Jun 24, 17:45 UTC | 12h 45m |
| 2026-06-23 | BAW168 | - | Jun 23, 18:39 UTC | Jun 24, 16:59 UTC | 22h 20m |
| 2026-06-23 | BAW168 | - | Jun 23, 15:30 UTC | Jun 24, 15:00 UTC | 23h 30m |
| 2026-06-23 | BAW169 | - | Jun 23, 13:05 UTC | Jun 24, 13:00 UTC | 23h 55m |
| 2026-06-23 | BAW169 | - | Jun 23, 11:35 UTC | Jun 24, 05:20 UTC | 17h 45m |
| 2026-06-22 | BAW16 | SIN → LHR | Jun 22, 15:20 UTC | Jun 23, 04:29 UTC | 13h 10m |
| 2026-06-22 | BAW16 | SIN → LHR | Jun 22, 04:54 UTC | Jun 22, 05:29 UTC | 35m |
| 2026-06-21 | BAW15 | SIN → SYD | Jun 21, 19:05 UTC | Jun 21, 19:45 UTC | 40m |
| 2026-06-20 | BAW15 | SIN → SYD | Jun 20, 21:30 UTC | Jun 21, 10:04 UTC | 12h 35m |
| 2026-06-20 | BAW168 | - | Jun 20, 04:44 UTC | Jun 20, 17:19 UTC | 12h 35m |
| 2026-06-19 | BAW168 | - | Jun 19, 15:09 UTC | Jun 20, 14:59 UTC | 23h 50m |
| 2026-06-19 | BAW169 | - | Jun 19, 13:04 UTC | Jun 20, 12:59 UTC | 23h 55m |
| 2026-06-19 | BAW169 | - | Jun 19, 11:30 UTC | Jun 20, 05:14 UTC | 17h 45m |
| 2026-06-18 | BAW34 | - | Jun 18, 16:40 UTC | Jun 19, 05:34 UTC | 12h 54m |
| 2026-06-18 | BAW33 | LHR → KUL | Jun 18, 08:35 UTC | Jun 18, 09:10 UTC | 35m |
| 2026-06-17 | BAW33 | LHR → KUL | Jun 17, 20:45 UTC | Jun 18, 05:50 UTC | 9h 5m |
| 2026-06-16 | BAW60 | - | Jun 16, 23:45 UTC | Jun 17, 17:05 UTC | 17h 20m |
| 2026-06-16 | BAW60 | - | Jun 16, 21:05 UTC | Jun 17, 17:05 UTC | 20h 0m |
| 2026-06-16 | BAW60 | - | Jun 16, 19:05 UTC | Jun 17, 17:05 UTC | 22h 1m |
| 2026-06-16 | BAW60 | - | Jun 16, 17:45 UTC | Jun 17, 17:00 UTC | 23h 16m |
| 2026-06-16 | BAW270 | LAS → LHR | Jun 16, 00:50 UTC | Jun 16, 10:20 UTC | 9h 30m |
| 2026-06-15 | BAW271 | LHR → LAS | Jun 15, 12:00 UTC | Jun 15, 21:30 UTC | 9h 30m |
| 2026-06-14 | BAW16 | SIN → LHR | Jun 14, 15:15 UTC | Jun 15, 04:50 UTC | 13h 34m |
| 2026-06-14 | BAW16 | SIN → LHR | Jun 14, 12:55 UTC | Jun 14, 13:05 UTC | 10m |
| 2026-06-14 | BAW16 | SIN → LHR | Jun 14, 04:55 UTC | Jun 14, 05:35 UTC | 40m |
| 2026-06-13 | BAW15 | SIN → SYD | Jun 13, 12:45 UTC | Jun 13, 19:25 UTC | 6h 40m |
| 2026-06-12 | BAW15 | SIN → SYD | Jun 12, 21:25 UTC | Jun 13, 09:40 UTC | 12h 14m |
| 2026-06-12 | BAW242 | - | Jun 12, 04:25 UTC | Jun 12, 14:40 UTC | 10h 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-ZBKH page for operator, model, and routing details .