sensors Mode-S transponder
4007F1
ICAO 24-bit transponder address · allocated to United Kingdom
Currently assigned to G-YMMF · BOEING 777-200
- Hex
- 4007F1
- Octal
- 20003761
- Decimal
- 4,196,337
- Country
- GB
- Tail
- G-YMMF
- Type
- B772
- Flights observed
- 180
- Distinct callsigns
- 20
- Country
- GB
- Last broadcast
- 35m ago
Last known position
Country allocation
The ICAO 24-bit address 4007F1 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 |
|---|---|---|---|
| BAW2202 | - | 25 | 2026-07-14 |
| BAW2203 | - | 20 | 2026-07-13 |
| BAW2230 | - | 15 | 2026-07-10 |
| BAW2064 | - | 11 | 2026-07-05 |
| BAW39D | - | 10 | 2026-06-23 |
| BAW38W | - | 10 | 2026-06-24 |
| BAW2231 | - | 10 | 2026-07-09 |
| BAW2256 | - | 9 | 2026-07-12 |
| BAW2065 | - | 9 | 2026-07-04 |
| BAW5KW | - | 8 | 2026-07-13 |
| BAW9VA | - | 7 | 2026-07-12 |
| BAW25K | - | 5 | 2026-07-04 |
| BAW2161 | British Airways | 4 | 2026-06-01 |
| BAW2159 | - | 4 | 2026-07-12 |
| BAW12TB | British Airways | 4 | 2026-05-18 |
| BAW12J | British Airways | 4 | 2026-05-18 |
| BAW63H | - | 3 | 2026-07-07 |
| BAW43C | - | 3 | 2026-07-07 |
| BAW22G | - | 3 | 2026-07-08 |
| BAW2204 | - | 3 | 2026-07-08 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | BAW2202 | CUN → LGW | Jul 14, 01:05 UTC | Jul 14, 10:15 UTC | 9h 10m |
| 2026-07-13 | BAW2203 | LGW → CUN | Jul 13, 13:20 UTC | Jul 13, 22:50 UTC | 9h 30m |
| 2026-07-13 | BAW5KW | - | Jul 13, 06:55 UTC | Jul 13, 08:25 UTC | 1h 30m |
| 2026-07-13 | BAW5KW | - | Jul 13, 00:35 UTC | Jul 13, 00:50 UTC | 15m |
| 2026-07-12 | BAW2158 | - | Jul 12, 23:00 UTC | Jul 12, 23:15 UTC | 15m |
| 2026-07-12 | BAW2159 | - | Jul 12, 20:25 UTC | Jul 12, 20:40 UTC | 15m |
| 2026-07-12 | BAW9VA | - | Jul 12, 11:15 UTC | Jul 12, 12:10 UTC | 55m |
| 2026-07-12 | BAW2256 | - | Jul 12, 05:15 UTC | Jul 12, 06:35 UTC | 1h 20m |
| 2026-07-11 | BAW2256 | - | Jul 11, 10:20 UTC | Jul 12, 06:35 UTC | 20h 15m |
| 2026-07-11 | BAW2256 | LGW → LGW | Jul 11, 09:35 UTC | Jul 12, 06:35 UTC | 21h 0m |
| 2026-07-10 | BAW2230 | - | Jul 10, 16:05 UTC | Jul 11, 04:10 UTC | 12h 6m |
| 2026-07-09 | BAW2231 | LGW → BKK | Jul 9, 21:35 UTC | Jul 10, 08:40 UTC | 11h 5m |
| 2026-07-08 | BAW2204 | - | Jul 8, 12:20 UTC | Jul 9, 06:45 UTC | 18h 25m |
| 2026-07-08 | BAW22G | LGW → LGW | Jul 8, 12:00 UTC | Jul 9, 06:45 UTC | 18h 45m |
| 2026-07-07 | BAW63H | MCO → LGW | Jul 7, 21:15 UTC | Jul 8, 05:25 UTC | 8h 10m |
| 2026-07-07 | BAW43C | LGW → MCO | Jul 7, 09:50 UTC | Jul 7, 18:30 UTC | 8h 40m |
| 2026-07-06 | BAW2204 | - | Jul 6, 10:20 UTC | Jul 7, 05:00 UTC | 18h 40m |
| 2026-07-06 | BAW22G | LGW → LGW | Jul 6, 09:25 UTC | Jul 7, 05:00 UTC | 19h 35m |
| 2026-07-05 | BAW2064 | - | Jul 5, 23:50 UTC | Jul 6, 04:55 UTC | 5h 5m |
| 2026-07-04 | BAW2065 | - | Jul 4, 20:15 UTC | Jul 4, 23:15 UTC | 3h 0m |
| 2026-07-04 | BAW25K | - | Jul 4, 11:05 UTC | Jul 4, 12:25 UTC | 1h 20m |
| 2026-07-03 | BAW25K | LGW → LGW | Jul 3, 15:15 UTC | Jul 4, 12:25 UTC | 21h 10m |
| 2026-07-03 | BAW2202 | CUN → LGW | Jul 3, 00:55 UTC | Jul 3, 09:50 UTC | 8h 55m |
| 2026-07-02 | BAW2203 | LGW → CUN | Jul 2, 12:55 UTC | Jul 2, 22:30 UTC | 9h 35m |
| 2026-07-01 | BAW2064 | - | Jul 1, 23:40 UTC | Jul 2, 04:20 UTC | 4h 40m |
| 2026-07-01 | BAW2064 | - | Jul 1, 00:25 UTC | Jul 2, 00:15 UTC | 23h 50m |
| 2026-06-30 | BAW2065 | - | Jun 30, 20:15 UTC | Jul 1, 00:25 UTC | 4h 10m |
| 2026-06-30 | BAW2202 | CUN → LGW | Jun 30, 01:09 UTC | Jun 30, 10:05 UTC | 8h 56m |
| 2026-06-29 | BAW2203 | LGW → CUN | Jun 29, 13:00 UTC | Jun 29, 22:55 UTC | 9h 55m |
| 2026-06-29 | BAW5KW | - | Jun 29, 07:55 UTC | Jun 29, 08:50 UTC | 55m |
| 2026-06-29 | BAW5KW | - | Jun 29, 01:34 UTC | Jun 29, 01:44 UTC | 10m |
| 2026-06-28 | BAW2158 | - | Jun 28, 23:54 UTC | Jun 29, 00:10 UTC | 15m |
| 2026-06-28 | BAW2159 | - | Jun 28, 21:14 UTC | Jun 28, 21:34 UTC | 20m |
| 2026-06-28 | BAW9VA | - | Jun 28, 19:34 UTC | Jun 28, 19:55 UTC | 20m |
| 2026-06-28 | BAW9VA | - | Jun 28, 11:09 UTC | Jun 28, 12:09 UTC | 1h 0m |
| 2026-06-27 | BAW2256 | - | Jun 27, 12:19 UTC | Jun 28, 07:50 UTC | 19h 30m |
| 2026-06-27 | BAW17PA | LGW → LGW | Jun 27, 11:39 UTC | Jun 28, 07:50 UTC | 20h 10m |
| 2026-06-25 | BAW2202 | CUN → LGW | Jun 25, 00:55 UTC | Jun 25, 09:45 UTC | 8h 50m |
| 2026-06-24 | BAW2203 | LGW → CUN | Jun 24, 12:54 UTC | Jun 24, 22:39 UTC | 9h 45m |
| 2026-06-24 | BAW38W | MCO → LGW | Jun 24, 01:34 UTC | Jun 24, 09:19 UTC | 7h 45m |
| 2026-06-23 | BAW39D | LGW → MCO | Jun 23, 14:10 UTC | Jun 23, 22:55 UTC | 8h 45m |
| 2026-06-23 | BAW2202 | CUN → LGW | Jun 23, 01:40 UTC | Jun 23, 10:35 UTC | 8h 55m |
| 2026-06-22 | BAW2203 | LGW → CUN | Jun 22, 13:39 UTC | Jun 22, 23:45 UTC | 10h 5m |
| 2026-06-22 | BAW2064 | - | Jun 22, 00:14 UTC | Jun 22, 05:10 UTC | 4h 55m |
| 2026-06-21 | BAW2064 | - | Jun 21, 00:19 UTC | Jun 22, 00:14 UTC | 23h 55m |
| 2026-06-20 | BAW2065 | - | Jun 20, 20:14 UTC | Jun 21, 00:25 UTC | 4h 10m |
| 2026-06-20 | BAW38W | MCO → LGW | Jun 20, 02:04 UTC | Jun 20, 09:49 UTC | 7h 45m |
| 2026-06-19 | BAW39D | LGW → MCO | Jun 19, 13:54 UTC | Jun 19, 23:04 UTC | 9h 10m |
| 2026-06-18 | BAW2202 | - | Jun 18, 17:40 UTC | Jun 19, 10:50 UTC | 17h 9m |
| 2026-06-18 | BAW2203 | LGW → LGW | Jun 18, 12:35 UTC | Jun 19, 10:50 UTC | 22h 14m |
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-YMMF page for operator, model, and routing details .