sensors Mode-S transponder
424293
ICAO 24-bit transponder address · allocated to United Kingdom
Currently assigned to VP-BBR · BOEING 787-8 Dreamliner
- Hex
- 424293
- Octal
- 20441223
- Decimal
- 4,342,419
- Country
- GB
- Tail
- VP-BBR
- Type
- B788
- Flights observed
- 90
- Distinct callsigns
- 14
- Country
- GB
- Last broadcast
- 7d ago
Last known position
Country allocation
The ICAO 24-bit address 424293 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 14 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| AHY075 | Azerbaijan Airlines | 12 | 2026-05-18 |
| AHY107 | Azerbaijan Airlines | 11 | 2026-04-26 |
| AHY077 | Azerbaijan Airlines | 11 | 2026-05-07 |
| AHY008 | - | 9 | 2026-05-22 |
| AHY007 | - | 9 | 2026-05-21 |
| AHY078 | Azerbaijan Airlines | 8 | 2026-05-16 |
| AHY067 | Azerbaijan Airlines | 6 | 2026-05-22 |
| AHY108 | Azerbaijan Airlines | 5 | 2026-04-27 |
| AHY076 | Azerbaijan Airlines | 5 | 2026-04-18 |
| AHY5222 | - | 4 | 2026-05-18 |
| AHY022 | Azerbaijan Airlines | 4 | 2026-05-20 |
| AHY021 | Azerbaijan Airlines | 4 | 2026-05-19 |
| AHY026 | Azerbaijan Airlines | 1 | 2026-05-16 |
| AHY025 | Azerbaijan Airlines | 1 | 2026-05-16 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-22 | AHY067 | GYD → PEK | May 22, 11:55 UTC | May 22, 22:40 UTC | 10h 45m |
| 2026-05-22 | AHY008 | - | May 22, 01:15 UTC | May 22, 22:40 UTC | 21h 25m |
| 2026-05-21 | AHY008 | - | May 21, 22:50 UTC | May 22, 22:40 UTC | 23h 50m |
| 2026-05-21 | AHY008 | - | May 21, 21:15 UTC | May 22, 12:00 UTC | 14h 45m |
| 2026-05-21 | AHY007 | - | May 21, 14:40 UTC | May 21, 19:35 UTC | 4h 55m |
| 2026-05-20 | AHY022 | TLV → GYD | May 20, 09:45 UTC | May 20, 11:55 UTC | 2h 10m |
| 2026-05-19 | AHY021 | GYD → TLV | May 19, 18:25 UTC | May 20, 08:05 UTC | 13h 41m |
| 2026-05-19 | AHY067 | GYD → PEK | May 19, 14:55 UTC | May 19, 15:20 UTC | 25m |
| 2026-05-18 | AHY5222 | - | May 18, 16:50 UTC | May 19, 12:05 UTC | 19h 14m |
| 2026-05-18 | AHY5222 | - | May 18, 14:50 UTC | May 19, 12:05 UTC | 21h 14m |
| 2026-05-18 | AHY5222 | - | May 18, 14:10 UTC | May 19, 12:05 UTC | 21h 54m |
| 2026-05-18 | AHY5222 | - | May 18, 10:25 UTC | May 18, 23:40 UTC | 13h 14m |
| 2026-05-18 | AHY075 | GYD → IST | May 18, 06:55 UTC | May 18, 07:05 UTC | 10m |
| 2026-05-17 | AHY075 | GYD → IST | May 17, 18:30 UTC | May 18, 06:10 UTC | 11h 40m |
| 2026-05-17 | AHY067 | GYD → PEK | May 17, 15:01 UTC | May 17, 15:20 UTC | 20m |
| 2026-05-16 | AHY078 | IST → GYD | May 16, 20:40 UTC | May 16, 22:35 UTC | 1h 55m |
| 2026-05-16 | AHY026 | AYT → GYD | May 16, 08:01 UTC | May 16, 17:40 UTC | 9h 40m |
| 2026-05-16 | AHY025 | GYD → AYT | May 16, 04:25 UTC | May 16, 06:31 UTC | 2h 6m |
| 2026-05-09 | AHY008 | - | May 9, 21:25 UTC | May 10, 01:39 UTC | 4h 15m |
| 2026-05-09 | AHY007 | - | May 9, 05:15 UTC | May 9, 19:30 UTC | 14h 15m |
| 2026-05-08 | AHY022 | TLV → GYD | May 8, 08:44 UTC | May 8, 22:25 UTC | 13h 40m |
| 2026-05-08 | AHY021 | GYD → TLV | May 8, 04:49 UTC | May 8, 07:14 UTC | 2h 25m |
| 2026-05-07 | AHY078 | IST → GYD | May 7, 20:25 UTC | May 7, 22:15 UTC | 1h 50m |
| 2026-05-07 | AHY077 | GYD → IST | May 7, 10:55 UTC | May 7, 17:45 UTC | 6h 50m |
| 2026-05-07 | AHY075 | GYD → IST | May 7, 06:20 UTC | May 7, 07:35 UTC | 1h 15m |
| 2026-05-06 | AHY078 | IST → GYD | May 6, 20:10 UTC | May 6, 22:00 UTC | 1h 50m |
| 2026-05-06 | AHY022 | TLV → GYD | May 6, 09:40 UTC | May 6, 17:35 UTC | 7h 54m |
| 2026-05-05 | AHY021 | GYD → TLV | May 5, 18:40 UTC | May 6, 07:50 UTC | 13h 10m |
| 2026-05-05 | AHY067 | GYD → PEK | May 5, 15:01 UTC | May 5, 15:25 UTC | 25m |
| 2026-05-04 | AHY078 | IST → GYD | May 4, 20:15 UTC | May 4, 22:05 UTC | 1h 50m |
| 2026-05-04 | AHY075 | GYD → IST | May 4, 05:00 UTC | May 4, 17:40 UTC | 12h 40m |
| 2026-05-03 | AHY022 | TLV → GYD | May 3, 12:05 UTC | May 3, 22:34 UTC | 10h 30m |
| 2026-05-03 | AHY021 | GYD → TLV | May 3, 07:50 UTC | May 3, 10:25 UTC | 2h 35m |
| 2026-05-02 | AHY008 | - | May 2, 21:20 UTC | May 3, 01:55 UTC | 4h 35m |
| 2026-05-02 | AHY007 | - | May 2, 05:15 UTC | May 2, 19:40 UTC | 14h 25m |
| 2026-05-01 | AHY067 | GYD → PEK | May 1, 15:00 UTC | May 1, 15:25 UTC | 25m |
| 2026-04-30 | AHY008 | - | Apr 30, 21:30 UTC | May 1, 12:00 UTC | 14h 30m |
| 2026-04-30 | AHY007 | - | Apr 30, 14:35 UTC | Apr 30, 19:45 UTC | 5h 10m |
| 2026-04-29 | AHY078 | IST → GYD | Apr 29, 20:20 UTC | Apr 29, 22:10 UTC | 1h 50m |
| 2026-04-29 | AHY077 | GYD → IST | Apr 29, 16:10 UTC | Apr 29, 17:30 UTC | 1h 20m |
| 2026-04-28 | AHY077 | GYD → IST | Apr 28, 18:50 UTC | Apr 29, 17:30 UTC | 22h 41m |
| 2026-04-28 | AHY077 | GYD → IST | Apr 28, 18:35 UTC | Apr 29, 16:45 UTC | 22h 11m |
| 2026-04-28 | AHY067 | GYD → PEK | Apr 28, 15:10 UTC | Apr 28, 15:20 UTC | 10m |
| 2026-04-27 | AHY108 | LGW → GYD | Apr 27, 11:00 UTC | Apr 27, 15:20 UTC | 4h 20m |
| 2026-04-26 | AHY107 | GYD → LGW | Apr 26, 14:50 UTC | Apr 27, 09:30 UTC | 18h 40m |
| 2026-04-26 | AHY107 | GYD → LGW | Apr 26, 12:50 UTC | Apr 27, 09:30 UTC | 20h 40m |
| 2026-04-26 | AHY107 | GYD → LGW | Apr 26, 12:25 UTC | Apr 27, 09:30 UTC | 21h 5m |
| 2026-04-26 | AHY107 | GYD → LGW | Apr 26, 05:20 UTC | Apr 26, 10:30 UTC | 5h 10m |
| 2026-04-25 | AHY077 | GYD → IST | Apr 25, 16:15 UTC | Apr 25, 17:35 UTC | 1h 20m |
| 2026-04-23 | AHY008 | - | Apr 23, 21:25 UTC | Apr 24, 01:55 UTC | 4h 30m |
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 VP-BBR page for operator, model, and routing details .