sensors Mode-S transponder
406F72
ICAO 24-bit transponder address · allocated to United Kingdom
Currently assigned to G-ZBKF · BOEING 787-9 Dreamliner
- Hex
- 406F72
- Octal
- 20067562
- Decimal
- 4,222,834
- Country
- GB
- Tail
- G-ZBKF
- Type
- B789
- Flights observed
- 118
- Distinct callsigns
- 20
- Country
- GB
- Last broadcast
- 19d ago
Last known position
Country allocation
The ICAO 24-bit address 406F72 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 |
|---|---|---|---|
| BAW168 | - | 13 | 2026-07-09 |
| BAW243 | British Airways | 9 | 2026-07-22 |
| BAW242 | British Airways | 9 | 2026-07-23 |
| BAW169 | - | 8 | 2026-07-08 |
| BAW60 | British Airways | 7 | 2026-07-24 |
| BAW16 | - | 7 | 2026-07-11 |
| BAW15 | - | 6 | 2026-07-10 |
| BAW6NC | - | 5 | 2026-07-01 |
| BAW6 | - | 5 | 2026-07-17 |
| BAW5 | - | 5 | 2026-07-16 |
| BAW9EW | - | 4 | 2026-07-02 |
| BAW34 | British Airways | 3 | 2026-07-26 |
| BAW131 | British Airways | 3 | 2026-06-20 |
| BAW130 | British Airways | 3 | 2026-06-20 |
| BAW99 | - | 2 | 2026-06-24 |
| BAW98T | - | 2 | 2026-06-25 |
| BAW33 | British Airways | 2 | 2026-07-25 |
| BAW271 | British Airways | 2 | 2026-05-28 |
| BAW270 | British Airways | 2 | 2026-05-29 |
| BAW139 | - | 2 | 2026-06-15 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | BAW34 | LHR → KUL | Jul 26, 17:50 UTC | Jul 26, 20:05 UTC | 2h 15m |
| 2026-07-26 | BAW34 | LHR → KUL | Jul 26, 15:20 UTC | Jul 26, 15:35 UTC | 15m |
| 2026-07-25 | BAW33 | LHR → KUL | Jul 25, 22:15 UTC | Jul 26, 10:45 UTC | 12h 31m |
| 2026-07-25 | BAW198 | BOM → LHR | Jul 25, 07:45 UTC | Jul 25, 17:00 UTC | 9h 15m |
| 2026-07-24 | BAW199 | LHR → BOM | Jul 24, 20:50 UTC | Jul 25, 05:20 UTC | 8h 30m |
| 2026-07-24 | BAW60 | MLE → LHR | Jul 24, 00:05 UTC | Jul 24, 16:35 UTC | 16h 30m |
| 2026-07-23 | BAW60 | MLE → LHR | Jul 23, 20:35 UTC | Jul 24, 16:35 UTC | 20h 0m |
| 2026-07-23 | BAW60 | MLE → LHR | Jul 23, 18:35 UTC | Jul 24, 16:35 UTC | 22h 0m |
| 2026-07-23 | BAW60 | MLE → LHR | Jul 23, 17:55 UTC | Jul 24, 16:30 UTC | 22h 35m |
| 2026-07-23 | BAW242 | MEX → LHR | Jul 23, 04:25 UTC | Jul 23, 14:20 UTC | 9h 55m |
| 2026-07-22 | BAW243 | LHR → MEX | Jul 22, 14:35 UTC | Jul 23, 01:00 UTC | 10h 25m |
| 2026-07-17 | BAW6 | HND → LHR | Jul 17, 04:35 UTC | Jul 17, 18:44 UTC | 14h 10m |
| 2026-07-16 | BAW5 | - | Jul 16, 12:34 UTC | Jul 17, 01:39 UTC | 13h 5m |
| 2026-07-15 | BAW9609 | HND → LHR | Jul 15, 06:20 UTC | Jul 15, 20:40 UTC | 14h 20m |
| 2026-07-13 | BAW5D | - | Jul 13, 03:10 UTC | Jul 13, 09:15 UTC | 6h 5m |
| 2026-07-12 | BAW9151 | - | Jul 12, 13:05 UTC | Jul 12, 17:15 UTC | 4h 10m |
| 2026-07-11 | BAW16 | - | Jul 11, 14:55 UTC | Jul 12, 03:55 UTC | 13h 0m |
| 2026-07-11 | BAW16 | - | Jul 11, 12:40 UTC | Jul 11, 12:50 UTC | 10m |
| 2026-07-11 | BAW16 | - | Jul 11, 04:45 UTC | Jul 11, 05:15 UTC | 30m |
| 2026-07-10 | BAW15 | - | Jul 10, 19:15 UTC | Jul 10, 19:50 UTC | 35m |
| 2026-07-09 | BAW15 | - | Jul 9, 21:45 UTC | Jul 10, 10:35 UTC | 12h 50m |
| 2026-07-09 | BAW168 | - | Jul 9, 05:40 UTC | Jul 9, 18:10 UTC | 12h 30m |
| 2026-07-08 | BAW168 | - | Jul 8, 18:35 UTC | Jul 9, 18:10 UTC | 23h 35m |
| 2026-07-08 | BAW168 | - | Jul 8, 15:15 UTC | Jul 9, 14:15 UTC | 23h 0m |
| 2026-07-08 | BAW169 | - | Jul 8, 11:30 UTC | Jul 9, 06:00 UTC | 18h 30m |
| 2026-07-07 | BAW16 | SIN → LHR | Jul 7, 15:10 UTC | Jul 8, 04:25 UTC | 13h 15m |
| 2026-07-07 | BAW16 | SIN → LHR | Jul 7, 04:45 UTC | Jul 7, 13:10 UTC | 8h 25m |
| 2026-07-06 | BAW15 | SIN → SYD | Jul 6, 19:10 UTC | Jul 6, 19:45 UTC | 35m |
| 2026-07-05 | BAW15 | SIN → SYD | Jul 5, 21:25 UTC | Jul 6, 09:55 UTC | 12h 30m |
| 2026-07-05 | BAW168 | - | Jul 5, 05:10 UTC | Jul 5, 17:20 UTC | 12h 10m |
| 2026-07-04 | BAW168 | - | Jul 4, 18:35 UTC | Jul 5, 17:20 UTC | 22h 45m |
| 2026-07-04 | BAW168 | - | Jul 4, 14:55 UTC | Jul 5, 13:25 UTC | 22h 30m |
| 2026-07-04 | BAW169 | - | Jul 4, 12:35 UTC | Jul 5, 12:30 UTC | 23h 55m |
| 2026-07-04 | BAW169 | - | Jul 4, 11:30 UTC | Jul 5, 08:55 UTC | 21h 25m |
| 2026-07-03 | BAW242 | - | Jul 3, 12:40 UTC | Jul 3, 14:00 UTC | 1h 20m |
| 2026-07-03 | BAW242 | - | Jul 3, 04:15 UTC | Jul 3, 09:20 UTC | 5h 5m |
| 2026-07-02 | BAW243 | LHR → MEX | Jul 2, 14:55 UTC | Jul 3, 01:40 UTC | 10h 45m |
| 2026-07-02 | BAW9EW | YUL → LHR | Jul 2, 03:10 UTC | Jul 2, 08:50 UTC | 5h 40m |
| 2026-07-01 | BAW6NC | - | Jul 1, 17:30 UTC | Jul 2, 00:15 UTC | 6h 45m |
| 2026-07-01 | BAW242 | MEX → LHR | Jul 1, 04:20 UTC | Jul 1, 14:25 UTC | 10h 5m |
| 2026-06-30 | BAW243 | LHR → MEX | Jun 30, 15:25 UTC | Jul 1, 01:55 UTC | 10h 30m |
| 2026-06-29 | BAW242D | - | Jun 29, 07:15 UTC | Jun 29, 16:55 UTC | 9h 40m |
| 2026-06-29 | BAW243D | - | Jun 29, 02:30 UTC | Jun 29, 04:14 UTC | 1h 45m |
| 2026-06-27 | BAW243 | LHR → MEX | Jun 27, 18:39 UTC | Jun 28, 05:09 UTC | 10h 30m |
| 2026-06-25 | BAW98T | YYZ → LHR | Jun 25, 05:29 UTC | Jun 25, 11:44 UTC | 6h 15m |
| 2026-06-24 | BAW99 | - | Jun 24, 16:59 UTC | Jun 25, 00:05 UTC | 7h 5m |
| 2026-06-24 | BAW186 | AUS → LHR | Jun 24, 03:40 UTC | Jun 24, 12:04 UTC | 8h 25m |
| 2026-06-23 | BAW187 | - | Jun 23, 15:59 UTC | Jun 24, 01:24 UTC | 9h 25m |
| 2026-06-22 | BAW168 | - | Jun 22, 05:29 UTC | Jun 22, 18:09 UTC | 12h 40m |
| 2026-06-21 | BAW168 | - | Jun 21, 14:34 UTC | Jun 22, 14:19 UTC | 23h 45m |
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-ZBKF page for operator, model, and routing details .