sensors Mode-S transponder
4246B7
ICAO 24-bit transponder address · allocated to United Kingdom
- Hex
- 4246B7
- Octal
- 20443267
- Decimal
- 4,343,479
- Country
- GB
- Flights observed
- 187
- Distinct callsigns
- 20
- Country
- GB
- Last broadcast
- 11d ago
Last known position
Country allocation
The ICAO 24-bit address 4246B7 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 |
|---|---|---|---|
| AHY8226 | - | 14 | 2026-07-11 |
| AHY107 | Azerbaijan Airlines | 11 | 2026-07-24 |
| AHY035 | Azerbaijan Airlines | 11 | 2026-07-24 |
| AHY061 | - | 9 | 2026-07-16 |
| AHY703 | - | 8 | 2026-07-13 |
| AHY036 | Azerbaijan Airlines | 8 | 2026-07-25 |
| AHY025 | - | 8 | 2026-06-26 |
| AHY8237 | - | 6 | 2026-07-03 |
| AHY8003 | Azerbaijan Airlines | 6 | 2026-07-26 |
| AHY063 | Azerbaijan Airlines | 6 | 2026-07-25 |
| AHY034 | - | 6 | 2026-07-15 |
| AHY026 | - | 6 | 2026-06-27 |
| AHY077 | Azerbaijan Airlines | 5 | 2026-07-25 |
| AHY064 | Azerbaijan Airlines | 5 | 2026-07-26 |
| AHY045 | - | 5 | 2026-07-17 |
| AHY033 | - | 5 | 2026-07-15 |
| AHY110 | Azerbaijan Airlines | 4 | 2026-05-30 |
| AHY108 | - | 4 | 2026-07-12 |
| AHY8238 | - | 3 | 2026-07-02 |
| AHY155 | - | 3 | 2026-07-01 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | AHY8003 | GYD → ESB | Jul 26, 16:55 UTC | Jul 26, 21:35 UTC | 4h 40m |
| 2026-07-26 | AHY064 | BER → GYD | Jul 26, 10:10 UTC | Jul 26, 13:45 UTC | 3h 35m |
| 2026-07-25 | AHY063 | GYD → BER | Jul 25, 20:20 UTC | Jul 26, 08:30 UTC | 12h 11m |
| 2026-07-25 | AHY077 | GYD → IST | Jul 25, 18:25 UTC | Jul 25, 18:45 UTC | 20m |
| 2026-07-25 | AHY036 | MXP → GYD | Jul 25, 09:45 UTC | Jul 25, 17:40 UTC | 7h 55m |
| 2026-07-24 | AHY035 | GYD → MXP | Jul 24, 11:50 UTC | Jul 25, 08:10 UTC | 20h 20m |
| 2026-07-24 | AHY035 | GYD → MXP | Jul 24, 11:20 UTC | Jul 25, 08:10 UTC | 20h 50m |
| 2026-07-24 | AHY107 | GYD → LGW | Jul 24, 04:10 UTC | Jul 24, 09:30 UTC | 5h 20m |
| 2026-07-23 | AHY036 | MXP → GYD | Jul 23, 09:55 UTC | Jul 23, 18:20 UTC | 8h 25m |
| 2026-07-22 | AHY035 | GYD → MXP | Jul 22, 20:30 UTC | Jul 23, 08:05 UTC | 11h 35m |
| 2026-07-22 | AHY077 | - | Jul 22, 18:20 UTC | Jul 22, 18:45 UTC | 25m |
| 2026-07-22 | AHY077 | - | Jul 22, 16:15 UTC | Jul 22, 17:30 UTC | 1h 15m |
| 2026-07-22 | AHY036 | - | Jul 22, 11:10 UTC | Jul 22, 13:35 UTC | 2h 25m |
| 2026-07-22 | AHY035 | GYD → MXP | Jul 22, 03:40 UTC | Jul 22, 05:00 UTC | 1h 20m |
| 2026-07-21 | AHY4732 | ZRH → ZRH | Jul 21, 14:30 UTC | Jul 21, 18:00 UTC | 3h 30m |
| 2026-07-19 | AHY4731 | - | Jul 19, 20:10 UTC | Jul 20, 12:35 UTC | 16h 25m |
| 2026-07-19 | AHY064 | - | Jul 19, 09:50 UTC | Jul 19, 17:40 UTC | 7h 50m |
| 2026-07-18 | AHY063 | - | Jul 18, 14:15 UTC | Jul 19, 08:00 UTC | 17h 45m |
| 2026-07-18 | AHY063 | - | Jul 18, 11:50 UTC | Jul 19, 08:00 UTC | 20h 10m |
| 2026-07-18 | AHY046 | BCN → BER | Jul 18, 10:05 UTC | Jul 19, 08:00 UTC | 21h 55m |
| 2026-07-17 | AHY045 | - | Jul 17, 14:00 UTC | Jul 18, 08:20 UTC | 18h 21m |
| 2026-07-17 | AHY4006 | - | Jul 17, 01:09 UTC | Jul 17, 12:35 UTC | 11h 25m |
| 2026-07-16 | AHY4005 | - | Jul 16, 07:50 UTC | Jul 16, 22:30 UTC | 14h 40m |
| 2026-07-16 | AHY061 | - | Jul 16, 03:55 UTC | Jul 16, 06:25 UTC | 2h 30m |
| 2026-07-15 | AHY034 | - | Jul 15, 11:50 UTC | Jul 15, 14:40 UTC | 2h 50m |
| 2026-07-15 | AHY033 | - | Jul 15, 06:35 UTC | Jul 15, 09:45 UTC | 3h 10m |
| 2026-07-14 | AHY4006 | - | Jul 14, 21:30 UTC | Jul 15, 04:00 UTC | 6h 29m |
| 2026-07-14 | AHY4005 | - | Jul 14, 08:00 UTC | Jul 14, 20:15 UTC | 12h 15m |
| 2026-07-13 | AHY061 | - | Jul 13, 12:00 UTC | Jul 14, 06:35 UTC | 18h 35m |
| 2026-07-13 | AHY061 | - | Jul 13, 10:30 UTC | Jul 14, 06:35 UTC | 20h 5m |
| 2026-07-13 | AHY703 | - | Jul 13, 06:20 UTC | Jul 14, 05:20 UTC | 23h 0m |
| 2026-07-12 | AHY108 | - | Jul 12, 11:05 UTC | Jul 12, 15:25 UTC | 4h 20m |
| 2026-07-11 | AHY107 | TBS → LGW | Jul 11, 22:15 UTC | Jul 12, 09:25 UTC | 11h 10m |
| 2026-07-11 | AHY8226 | TBS → TBS | Jul 11, 17:30 UTC | Jul 11, 20:55 UTC | 3h 25m |
| 2026-07-11 | AHY036 | MXP → TBS | Jul 11, 10:05 UTC | Jul 11, 16:20 UTC | 6h 15m |
| 2026-07-11 | AHY035 | - | Jul 11, 03:40 UTC | Jul 11, 08:10 UTC | 4h 30m |
| 2026-07-10 | AHY108 | - | Jul 10, 11:25 UTC | Jul 10, 20:35 UTC | 9h 10m |
| 2026-07-09 | AHY107 | - | Jul 9, 16:45 UTC | Jul 10, 09:35 UTC | 16h 50m |
| 2026-07-09 | AHY107 | - | Jul 9, 11:50 UTC | Jul 10, 09:35 UTC | 21h 45m |
| 2026-07-09 | AHY107 | - | Jul 9, 10:00 UTC | Jul 10, 09:35 UTC | 23h 35m |
| 2026-07-08 | AHY063 | - | Jul 8, 23:30 UTC | Jul 9, 08:15 UTC | 8h 45m |
| 2026-07-08 | AHY8226 | - | Jul 8, 19:05 UTC | Jul 8, 22:00 UTC | 2h 55m |
| 2026-07-08 | AHY8225 | - | Jul 8, 17:20 UTC | Jul 8, 17:55 UTC | 35m |
| 2026-07-08 | AHY036 | - | Jul 8, 10:15 UTC | Jul 8, 13:50 UTC | 3h 35m |
| 2026-07-08 | AHY035 | - | Jul 8, 03:30 UTC | Jul 8, 08:00 UTC | 4h 30m |
| 2026-07-07 | AHY322 | TLV → GYD | Jul 7, 22:30 UTC | Jul 8, 00:35 UTC | 2h 5m |
| 2026-07-07 | AHY036 | MXP → TLV | Jul 7, 10:05 UTC | Jul 7, 21:05 UTC | 11h 0m |
| 2026-07-06 | AHY035 | - | Jul 6, 13:50 UTC | Jul 7, 08:40 UTC | 18h 50m |
| 2026-07-06 | AHY035 | - | Jul 6, 11:50 UTC | Jul 7, 08:40 UTC | 20h 50m |
| 2026-07-06 | AHY035 | VIE → MXP | Jul 6, 11:00 UTC | Jul 7, 08:40 UTC | 21h 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.