sensors Mode-S transponder
4007F5
ICAO 24-bit transponder address · allocated to United Kingdom
Currently assigned to G-YMMJ · BOEING 777-200
- Hex
- 4007F5
- Octal
- 20003765
- Decimal
- 4,196,341
- Country
- GB
- Tail
- G-YMMJ
- Type
- B772
- Flights observed
- 237
- Distinct callsigns
- 20
- Country
- GB
- Last broadcast
- Jul 26, 20:55 UTC
Last known position
Country allocation
The ICAO 24-bit address 4007F5 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 |
|---|---|---|---|
| BAW249 | British Airways | 18 | 2026-07-18 |
| BAW248 | British Airways | 16 | 2026-07-18 |
| BAW2LJ | - | 12 | 2026-07-11 |
| BAW276 | - | 12 | 2026-07-05 |
| BAW265 | British Airways | 12 | 2026-07-19 |
| BAW264 | - | 12 | 2026-07-20 |
| BAW22B | - | 12 | 2026-07-10 |
| BAW134 | - | 11 | 2026-07-08 |
| BAW257 | British Airways | 10 | 2026-04-19 |
| BAW198 | British Airways | 10 | 2026-05-09 |
| BAW135 | - | 10 | 2026-07-08 |
| BAW256 | British Airways | 9 | 2026-04-20 |
| BAW98T | British Airways | 6 | 2026-07-22 |
| BAW63 | - | 5 | 2026-07-15 |
| BAW46EZ | - | 5 | 2026-07-11 |
| BAW461 | - | 5 | 2026-07-11 |
| BAW21V | British Airways | 5 | 2026-07-25 |
| BAW120 | British Airways | 5 | 2026-07-26 |
| BAW143 | British Airways | 4 | 2026-05-10 |
| BAW142 | British Airways | 4 | 2026-05-10 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | BAW7W | LHR → IAD | Jul 26, 13:05 UTC | Jul 26, 20:45 UTC | 7h 40m |
| 2026-07-26 | BAW120 | CVG → LHR | Jul 26, 01:35 UTC | Jul 26, 08:55 UTC | 7h 21m |
| 2026-07-25 | BAW21V | LHR → CVG | Jul 25, 15:15 UTC | Jul 25, 23:05 UTC | 7h 50m |
| 2026-07-25 | BAW252N | NAS → LHR | Jul 25, 06:20 UTC | Jul 25, 11:20 UTC | 5h 0m |
| 2026-07-24 | BAW53M | LHR → NAS | Jul 24, 09:45 UTC | Jul 25, 06:30 UTC | 20h 45m |
| 2026-07-22 | BAW98T | YYZ → LHR | Jul 22, 02:45 UTC | Jul 22, 04:25 UTC | 1h 40m |
| 2026-07-21 | BAW99 | LHR → YYZ | Jul 21, 16:50 UTC | Jul 22, 00:05 UTC | 7h 15m |
| 2026-07-21 | BAW86 | YVR → LHR | Jul 21, 01:35 UTC | Jul 21, 10:20 UTC | 8h 45m |
| 2026-07-20 | BAW87 | LHR → YVR | Jul 20, 13:50 UTC | Jul 20, 23:05 UTC | 9h 15m |
| 2026-07-20 | BAW264 | - | Jul 20, 00:15 UTC | Jul 20, 10:20 UTC | 10h 5m |
| 2026-07-19 | BAW265 | LHR → SAN | Jul 19, 11:00 UTC | Jul 19, 21:25 UTC | 10h 25m |
| 2026-07-18 | BAW248 | GIG → LHR | Jul 18, 20:10 UTC | Jul 19, 06:30 UTC | 10h 20m |
| 2026-07-18 | BAW248 | GIG → LHR | Jul 18, 15:45 UTC | Jul 18, 18:15 UTC | 2h 30m |
| 2026-07-18 | BAW249 | LHR → GIG | Jul 18, 10:50 UTC | Jul 18, 13:40 UTC | 2h 50m |
| 2026-07-17 | BAW249 | LHR → GIG | Jul 17, 22:00 UTC | Jul 18, 08:55 UTC | 10h 56m |
| 2026-07-15 | BAW62 | - | Jul 15, 14:00 UTC | Jul 15, 16:20 UTC | 2h 20m |
| 2026-07-15 | BAW63 | - | Jul 15, 05:10 UTC | Jul 15, 05:20 UTC | 10m |
| 2026-07-14 | BAW63 | - | Jul 14, 21:00 UTC | Jul 15, 00:50 UTC | 3h 49m |
| 2026-07-14 | BAW62 | - | Jul 14, 15:00 UTC | Jul 14, 17:10 UTC | 2h 10m |
| 2026-07-13 | BAW63 | - | Jul 13, 21:35 UTC | Jul 14, 01:25 UTC | 3h 50m |
| 2026-07-13 | BAW62 | - | Jul 13, 16:00 UTC | Jul 13, 18:20 UTC | 2h 20m |
| 2026-07-13 | BAW63 | - | Jul 13, 06:30 UTC | Jul 13, 06:40 UTC | 10m |
| 2026-07-12 | BAW63 | - | Jul 12, 22:35 UTC | Jul 13, 02:15 UTC | 3h 40m |
| 2026-07-11 | BAW461 | MAD → LHR | Jul 11, 17:05 UTC | Jul 11, 19:05 UTC | 2h 0m |
| 2026-07-11 | BAW46EZ | - | Jul 11, 13:30 UTC | Jul 11, 15:10 UTC | 1h 40m |
| 2026-07-11 | BAW2LJ | BWI → LHR | Jul 11, 03:30 UTC | Jul 11, 10:10 UTC | 6h 40m |
| 2026-07-10 | BAW22B | LHR → BWI | Jul 10, 16:00 UTC | Jul 10, 23:40 UTC | 7h 40m |
| 2026-07-10 | BAW264 | - | Jul 10, 00:40 UTC | Jul 10, 10:45 UTC | 10h 5m |
| 2026-07-09 | BAW265 | LHR → SAN | Jul 9, 11:35 UTC | Jul 9, 22:05 UTC | 10h 30m |
| 2026-07-08 | BAW134 | - | Jul 8, 12:25 UTC | Jul 8, 19:35 UTC | 7h 10m |
| 2026-07-08 | BAW134 | - | Jul 8, 10:15 UTC | Jul 8, 10:35 UTC | 20m |
| 2026-07-08 | BAW135 | - | Jul 8, 07:45 UTC | Jul 8, 08:05 UTC | 20m |
| 2026-07-08 | BAW135 | - | Jul 8, 06:55 UTC | Jul 8, 07:05 UTC | 10m |
| 2026-07-07 | BAW135 | - | Jul 7, 18:20 UTC | Jul 8, 05:05 UTC | 10h 45m |
| 2026-07-07 | BAW134 | - | Jul 7, 05:55 UTC | Jul 7, 15:20 UTC | 9h 25m |
| 2026-07-06 | BAW135 | - | Jul 6, 19:20 UTC | Jul 7, 03:30 UTC | 8h 10m |
| 2026-07-05 | BAW276 | - | Jul 5, 17:20 UTC | Jul 6, 12:55 UTC | 19h 35m |
| 2026-07-05 | BAW276 | - | Jul 5, 15:40 UTC | Jul 6, 12:55 UTC | 21h 15m |
| 2026-07-04 | BAW276 | - | Jul 4, 17:20 UTC | Jul 5, 12:40 UTC | 19h 20m |
| 2026-07-04 | BAW276 | - | Jul 4, 15:20 UTC | Jul 5, 12:40 UTC | 21h 20m |
| 2026-07-03 | BAW290 | IAD → LHR | Jul 3, 23:45 UTC | Jul 4, 06:30 UTC | 6h 45m |
| 2026-07-03 | BAW291 | - | Jul 3, 13:40 UTC | Jul 3, 21:25 UTC | 7h 45m |
| 2026-07-03 | BAW86 | YVR → LHR | Jul 3, 01:25 UTC | Jul 3, 10:05 UTC | 8h 40m |
| 2026-07-02 | BAW87 | - | Jul 2, 13:45 UTC | Jul 2, 22:55 UTC | 9h 10m |
| 2026-07-02 | BAW2LJ | - | Jul 2, 03:25 UTC | Jul 2, 09:50 UTC | 6h 25m |
| 2026-07-01 | BAW22B | - | Jul 1, 15:55 UTC | Jul 1, 23:25 UTC | 7h 30m |
| 2026-06-30 | BAW277 | LHR → HYD | Jun 30, 15:20 UTC | Jul 1, 12:35 UTC | 21h 15m |
| 2026-06-30 | BAW2LJ | - | Jun 30, 01:55 UTC | Jun 30, 08:30 UTC | 6h 35m |
| 2026-06-29 | BAW22B | - | Jun 29, 16:25 UTC | Jun 29, 23:44 UTC | 7h 20m |
| 2026-06-28 | BAW248 | - | Jun 28, 20:14 UTC | Jun 29, 06:54 UTC | 10h 40m |
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-YMMJ page for operator, model, and routing details .