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
- 98
- Distinct callsigns
- 20
- Country
- GB
- Last broadcast
- 18h ago
Current 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 | - | 7 | 2026-06-17 |
| AHY703 | Azerbaijan Airlines | 7 | 2026-06-09 |
| AHY107 | - | 6 | 2026-06-18 |
| AHY025 | Azerbaijan Airlines | 6 | 2026-06-09 |
| AHY8003 | Azerbaijan Airlines | 5 | 2026-05-13 |
| AHY034 | Azerbaijan Airlines | 5 | 2026-06-13 |
| AHY110 | Azerbaijan Airlines | 4 | 2026-05-30 |
| AHY033 | Azerbaijan Airlines | 4 | 2026-06-12 |
| AHY026 | Azerbaijan Airlines | 4 | 2026-06-10 |
| AHY074 | Azerbaijan Airlines | 3 | 2026-05-31 |
| AHY064 | - | 3 | 2026-06-21 |
| AHY045 | - | 3 | 2026-06-19 |
| AHY8238 | - | 2 | 2026-06-17 |
| AHY8237 | Azerbaijan Airlines | 2 | 2026-06-09 |
| AHY175 | Azerbaijan Airlines | 2 | 2026-05-08 |
| AHY109 | Azerbaijan Airlines | 2 | 2026-05-30 |
| AHY108 | Azerbaijan Airlines | 2 | 2026-06-15 |
| AHY078 | Azerbaijan Airlines | 2 | 2026-06-10 |
| AHY076 | Azerbaijan Airlines | 2 | 2026-06-07 |
| AHY075 | Azerbaijan Airlines | 2 | 2026-06-07 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-22 | AHY062 | - | Jun 22, 08:15 UTC | Jun 22, 10:00 UTC | 1h 45m |
| 2026-06-21 | AHY064 | - | Jun 21, 11:49 UTC | Jun 22, 06:39 UTC | 18h 50m |
| 2026-06-21 | AHY064 | - | Jun 21, 11:05 UTC | Jun 22, 06:39 UTC | 19h 35m |
| 2026-06-20 | AHY063 | - | Jun 20, 14:19 UTC | Jun 21, 09:04 UTC | 18h 45m |
| 2026-06-20 | AHY046 | BCN → BER | Jun 20, 10:15 UTC | Jun 21, 09:04 UTC | 22h 50m |
| 2026-06-19 | AHY045 | - | Jun 19, 13:50 UTC | Jun 20, 08:25 UTC | 18h 35m |
| 2026-06-19 | AHY045 | - | Jun 19, 11:49 UTC | Jun 20, 08:25 UTC | 20h 35m |
| 2026-06-19 | AHY045 | LGW → BCN | Jun 19, 11:04 UTC | Jun 20, 08:25 UTC | 21h 20m |
| 2026-06-18 | AHY107 | - | Jun 18, 21:30 UTC | Jun 19, 09:30 UTC | 11h 59m |
| 2026-06-18 | AHY156 | - | Jun 18, 08:25 UTC | Jun 18, 19:45 UTC | 11h 20m |
| 2026-06-18 | AHY155 | - | Jun 18, 03:30 UTC | Jun 18, 06:50 UTC | 3h 20m |
| 2026-06-17 | AHY8238 | - | Jun 17, 22:00 UTC | Jun 17, 22:30 UTC | 30m |
| 2026-06-17 | AHY8238 | - | Jun 17, 20:25 UTC | Jun 17, 20:55 UTC | 30m |
| 2026-06-17 | AHY8226 | - | Jun 17, 17:30 UTC | Jun 17, 17:55 UTC | 25m |
| 2026-06-17 | AHY062 | - | Jun 17, 07:45 UTC | Jun 17, 16:05 UTC | 8h 20m |
| 2026-06-17 | AHY061 | - | Jun 17, 03:55 UTC | Jun 17, 06:20 UTC | 2h 25m |
| 2026-06-16 | AHY072 | VIE → GYD | Jun 16, 11:20 UTC | Jun 16, 14:25 UTC | 3h 5m |
| 2026-06-16 | AHY071 | GYD → VIE | Jun 16, 06:10 UTC | Jun 16, 09:40 UTC | 3h 30m |
| 2026-06-15 | AHY108 | LGW → GYD | Jun 15, 11:19 UTC | Jun 15, 15:55 UTC | 4h 35m |
| 2026-06-15 | AHY107 | - | Jun 15, 03:50 UTC | Jun 15, 09:35 UTC | 5h 45m |
| 2026-06-14 | AHY107 | TBS → LGW | Jun 14, 12:50 UTC | Jun 15, 09:35 UTC | 20h 44m |
| 2026-06-14 | AHY8224 | TBS → TBS | Jun 14, 08:00 UTC | Jun 14, 11:35 UTC | 3h 35m |
| 2026-06-13 | AHY034 | TIV → GYD | Jun 13, 11:50 UTC | Jun 14, 06:35 UTC | 18h 45m |
| 2026-06-13 | AHY034 | TIV → GYD | Jun 13, 10:50 UTC | Jun 14, 06:35 UTC | 19h 45m |
| 2026-06-12 | AHY033 | GYD → TIV | Jun 12, 22:00 UTC | Jun 13, 08:55 UTC | 10h 54m |
| 2026-06-12 | AHY108 | LGW → GYD | Jun 12, 11:20 UTC | Jun 12, 20:40 UTC | 9h 20m |
| 2026-06-11 | AHY107 | - | Jun 11, 13:50 UTC | Jun 12, 09:35 UTC | 19h 46m |
| 2026-06-11 | AHY107 | - | Jun 11, 11:50 UTC | Jun 12, 09:35 UTC | 21h 46m |
| 2026-06-11 | AHY107 | - | Jun 11, 11:00 UTC | Jun 12, 09:35 UTC | 22h 35m |
| 2026-06-11 | AHY033 | GYD → TIV | Jun 11, 05:55 UTC | Jun 11, 09:15 UTC | 3h 20m |
| 2026-06-10 | AHY078 | IST → GYD | Jun 10, 21:40 UTC | Jun 10, 22:30 UTC | 50m |
| 2026-06-10 | AHY078 | IST → GYD | Jun 10, 20:15 UTC | Jun 10, 20:45 UTC | 30m |
| 2026-06-10 | AHY077 | GYD → IST | Jun 10, 18:10 UTC | Jun 10, 18:30 UTC | 20m |
| 2026-06-10 | AHY026 | AYT → GYD | Jun 10, 08:10 UTC | Jun 10, 17:30 UTC | 9h 20m |
| 2026-06-09 | AHY025 | GYD → AYT | Jun 9, 22:15 UTC | Jun 10, 06:50 UTC | 8h 35m |
| 2026-06-09 | AHY8237 | GYD → TBS | Jun 9, 20:35 UTC | Jun 9, 20:55 UTC | 20m |
| 2026-06-09 | AHY8226 | TBS → GYD | Jun 9, 18:55 UTC | Jun 9, 19:25 UTC | 30m |
| 2026-06-09 | AHY8226 | TBS → GYD | Jun 9, 16:45 UTC | Jun 9, 16:50 UTC | 5m |
| 2026-06-09 | AHY703 | GYD → RMO | Jun 9, 06:20 UTC | Jun 9, 12:35 UTC | 6h 15m |
| 2026-06-08 | AHY034 | TIV → GYD | Jun 8, 10:50 UTC | Jun 8, 20:05 UTC | 9h 15m |
| 2026-06-08 | AHY033 | GYD → TIV | Jun 8, 08:30 UTC | Jun 8, 09:15 UTC | 45m |
| 2026-06-07 | AHY076 | IST → GYD | Jun 7, 10:00 UTC | Jun 8, 09:15 UTC | 23h 15m |
| 2026-06-07 | AHY076 | IST → GYD | Jun 7, 09:10 UTC | Jun 7, 11:10 UTC | 2h 0m |
| 2026-06-07 | AHY075 | GYD → IST | Jun 7, 06:55 UTC | Jun 7, 07:15 UTC | 20m |
| 2026-06-06 | AHY075 | GYD → IST | Jun 6, 22:10 UTC | Jun 7, 06:20 UTC | 8h 10m |
| 2026-06-06 | AHY8226 | TBS → GYD | Jun 6, 17:54 UTC | Jun 6, 20:55 UTC | 3h 0m |
| 2026-06-06 | AHY703 | GYD → RMO | Jun 6, 06:20 UTC | Jun 6, 16:34 UTC | 10h 15m |
| 2026-06-05 | AHY703 | GYD → RMO | Jun 5, 09:50 UTC | Jun 6, 07:45 UTC | 21h 55m |
| 2026-06-05 | AHY703 | GYD → RMO | Jun 5, 08:15 UTC | Jun 6, 07:45 UTC | 23h 30m |
| 2026-06-05 | AHY025 | GYD → AYT | Jun 5, 04:25 UTC | Jun 5, 06:40 UTC | 2h 15m |
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.