sensors Mode-S transponder
4007F7
ICAO 24-bit transponder address · allocated to United Kingdom
Currently assigned to G-YMML · BOEING 777-200
- Hex
- 4007F7
- Octal
- 20003767
- Decimal
- 4,196,343
- Country
- GB
- Tail
- G-YMML
- Type
- B772
- Flights observed
- 163
- Distinct callsigns
- 20
- Country
- GB
- Last broadcast
- 10d ago
Last known position
Country allocation
The ICAO 24-bit address 4007F7 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 |
|---|---|---|---|
| BAW5VY | - | 10 | 2026-06-29 |
| BAW248 | - | 10 | 2026-07-03 |
| BAW21V | - | 10 | 2026-06-22 |
| BAW88C | - | 9 | 2026-06-30 |
| BAW276 | - | 9 | 2026-06-27 |
| BAW120 | - | 9 | 2026-06-23 |
| BAW249 | - | 8 | 2026-07-02 |
| BAW2LJ | - | 7 | 2026-06-25 |
| BAW265 | - | 7 | 2026-06-21 |
| BAW264 | - | 7 | 2026-06-22 |
| BAW134 | British Airways | 6 | 2026-05-04 |
| BAW22B | - | 5 | 2026-06-24 |
| BAW135 | British Airways | 5 | 2026-05-04 |
| BAW51B | British Airways | 4 | 2026-04-17 |
| BAW46EZ | - | 4 | 2026-07-02 |
| BAW461 | - | 4 | 2026-07-02 |
| BAW143 | British Airways | 4 | 2026-05-23 |
| BAW142 | British Airways | 4 | 2026-05-23 |
| BAW7CP | British Airways | 3 | 2026-04-26 |
| BAW6AC | British Airways | 3 | 2026-04-27 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-03 | BAW248 | - | Jul 3, 20:15 UTC | Jul 4, 06:45 UTC | 10h 30m |
| 2026-07-03 | BAW248 | - | Jul 3, 16:10 UTC | Jul 3, 18:20 UTC | 2h 10m |
| 2026-07-02 | BAW249 | - | Jul 2, 21:10 UTC | Jul 3, 14:30 UTC | 17h 20m |
| 2026-07-02 | BAW461 | MAD → LHR | Jul 2, 15:50 UTC | Jul 2, 17:45 UTC | 1h 55m |
| 2026-07-02 | BAW46EZ | - | Jul 2, 11:45 UTC | Jul 2, 13:35 UTC | 1h 50m |
| 2026-07-01 | BAW248 | - | Jul 1, 20:20 UTC | Jul 2, 06:45 UTC | 10h 25m |
| 2026-07-01 | BAW248 | - | Jul 1, 15:45 UTC | Jul 1, 17:50 UTC | 2h 5m |
| 2026-07-01 | BAW249 | - | Jul 1, 11:00 UTC | Jul 1, 13:55 UTC | 2h 55m |
| 2026-06-30 | BAW249 | - | Jun 30, 21:05 UTC | Jul 1, 08:00 UTC | 10h 55m |
| 2026-06-30 | BAW88C | YVR → LHR | Jun 30, 04:10 UTC | Jun 30, 13:10 UTC | 9h 0m |
| 2026-06-29 | BAW5VY | - | Jun 29, 16:59 UTC | Jun 30, 01:45 UTC | 8h 46m |
| 2026-06-29 | BAW88C | - | Jun 29, 04:39 UTC | Jun 29, 13:30 UTC | 8h 50m |
| 2026-06-28 | BAW5VY | - | Jun 28, 17:50 UTC | Jun 29, 02:35 UTC | 8h 45m |
| 2026-06-27 | BAW276 | - | Jun 27, 17:49 UTC | Jun 28, 12:35 UTC | 18h 45m |
| 2026-06-27 | BAW276 | - | Jun 27, 15:49 UTC | Jun 28, 12:35 UTC | 20h 45m |
| 2026-06-27 | BAW276 | - | Jun 27, 15:24 UTC | Jun 28, 12:35 UTC | 21h 10m |
| 2026-06-26 | BAW248 | - | Jun 26, 20:04 UTC | Jun 27, 06:54 UTC | 10h 50m |
| 2026-06-26 | BAW248 | - | Jun 26, 15:34 UTC | Jun 26, 18:09 UTC | 2h 35m |
| 2026-06-26 | BAW249 | - | Jun 26, 10:30 UTC | Jun 26, 13:19 UTC | 2h 50m |
| 2026-06-25 | BAW249 | - | Jun 25, 21:15 UTC | Jun 26, 08:15 UTC | 11h 0m |
| 2026-06-25 | BAW461 | MAD → LHR | Jun 25, 15:54 UTC | Jun 25, 17:49 UTC | 1h 55m |
| 2026-06-25 | BAW46EZ | - | Jun 25, 12:15 UTC | Jun 25, 13:59 UTC | 1h 45m |
| 2026-06-25 | BAW2LJ | - | Jun 25, 01:54 UTC | Jun 25, 08:14 UTC | 6h 20m |
| 2026-06-24 | BAW22B | - | Jun 24, 16:05 UTC | Jun 24, 23:40 UTC | 7h 35m |
| 2026-06-23 | BAW276 | - | Jun 23, 17:50 UTC | Jun 24, 12:30 UTC | 18h 40m |
| 2026-06-23 | BAW276 | - | Jun 23, 15:50 UTC | Jun 24, 12:30 UTC | 20h 40m |
| 2026-06-23 | BAW276 | - | Jun 23, 15:09 UTC | Jun 24, 12:30 UTC | 21h 20m |
| 2026-06-23 | BAW120 | - | Jun 23, 01:30 UTC | Jun 23, 08:50 UTC | 7h 20m |
| 2026-06-22 | BAW21V | - | Jun 22, 15:14 UTC | Jun 22, 23:24 UTC | 8h 10m |
| 2026-06-22 | BAW264 | - | Jun 22, 00:10 UTC | Jun 22, 10:15 UTC | 10h 5m |
| 2026-06-21 | BAW265 | - | Jun 21, 11:00 UTC | Jun 21, 21:39 UTC | 10h 40m |
| 2026-06-21 | BAW64 | - | Jun 21, 03:10 UTC | Jun 21, 05:25 UTC | 2h 15m |
| 2026-06-20 | BAW65 | - | Jun 20, 18:19 UTC | Jun 20, 18:29 UTC | 10m |
| 2026-06-20 | BAW65 | - | Jun 20, 09:49 UTC | Jun 20, 12:59 UTC | 3h 10m |
| 2026-06-11 | BAW5CA | YYZ → LHR | Jun 11, 22:40 UTC | Jun 12, 05:05 UTC | 6h 26m |
| 2026-06-11 | BAW9ZY | LHR → YYZ | Jun 11, 12:55 UTC | Jun 11, 20:25 UTC | 7h 30m |
| 2026-06-11 | BAW98T | YYZ → LHR | Jun 11, 02:20 UTC | Jun 11, 09:00 UTC | 6h 40m |
| 2026-06-10 | BAW99 | LHR → YYZ | Jun 10, 16:45 UTC | Jun 11, 00:10 UTC | 7h 25m |
| 2026-06-10 | BAW120 | CVG → LHR | Jun 10, 02:25 UTC | Jun 10, 09:35 UTC | 7h 10m |
| 2026-06-09 | BAW21V | LHR → CVG | Jun 9, 14:25 UTC | Jun 9, 22:10 UTC | 7h 45m |
| 2026-06-07 | BAW88C | YVR → LHR | Jun 7, 04:15 UTC | Jun 7, 13:10 UTC | 8h 55m |
| 2026-06-06 | BAW5VY | LHR → YVR | Jun 6, 17:00 UTC | Jun 7, 02:00 UTC | 9h 0m |
| 2026-06-05 | BAW276 | HYD → LHR | Jun 5, 17:50 UTC | Jun 6, 12:24 UTC | 18h 35m |
| 2026-06-05 | BAW276 | HYD → LHR | Jun 5, 15:50 UTC | Jun 6, 12:24 UTC | 20h 35m |
| 2026-06-05 | BAW276 | HYD → LHR | Jun 5, 15:40 UTC | Jun 6, 12:24 UTC | 20h 45m |
| 2026-06-04 | BAW290 | LHR → IAD | Jun 4, 23:45 UTC | Jun 5, 06:25 UTC | 6h 40m |
| 2026-06-04 | BAW291 | LHR → SFO | Jun 4, 14:15 UTC | Jun 4, 21:50 UTC | 7h 35m |
| 2026-06-04 | BAW120 | CVG → LHR | Jun 4, 02:40 UTC | Jun 4, 09:55 UTC | 7h 15m |
| 2026-06-03 | BAW21V | LHR → CVG | Jun 3, 16:15 UTC | Jun 4, 00:25 UTC | 8h 10m |
| 2026-06-03 | BAW264 | IAD → LHR | Jun 3, 00:05 UTC | Jun 3, 10:25 UTC | 10h 20m |
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-YMML page for operator, model, and routing details .