sensors Mode-S transponder
4246B4
ICAO 24-bit transponder address · allocated to United Kingdom
Currently assigned to VP-BAK · AIRBUS A-320neo
- Hex
- 4246B4
- Octal
- 20443264
- Decimal
- 4,343,476
- Country
- GB
- Tail
- VP-BAK
- Type
- A20N
- Flights observed
- 242
- Distinct callsigns
- 20
- Country
- GB
- Last broadcast
- Jul 26, 22:45 UTC
Last known position
Country allocation
The ICAO 24-bit address 4246B4 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 |
|---|---|---|---|
| AHY045 | Azerbaijan Airlines | 46 | 2026-07-25 |
| AHY107 | - | 33 | 2026-07-06 |
| AHY046 | Azerbaijan Airlines | 32 | 2026-07-26 |
| AHY108 | - | 20 | 2026-07-21 |
| AHY8105 | - | 7 | 2026-06-27 |
| AHY175 | - | 5 | 2026-07-15 |
| AHY071 | Azerbaijan Airlines | 5 | 2026-07-24 |
| AHY072 | Azerbaijan Airlines | 4 | 2026-07-24 |
| AHY8238 | - | 3 | 2026-07-10 |
| AHY8226 | - | 3 | 2026-07-10 |
| AHY8042 | - | 3 | 2026-07-17 |
| AHY5050 | Azerbaijan Airlines | 3 | 2026-07-16 |
| AHY4026 | - | 3 | 2026-07-23 |
| AHY109 | - | 3 | 2026-07-08 |
| AHY8234 | Azerbaijan Airlines | 2 | 2026-05-03 |
| AHY8233 | Azerbaijan Airlines | 2 | 2026-05-03 |
| AHY8225 | Azerbaijan Airlines | 2 | 2026-05-05 |
| AHY8041 | - | 2 | 2026-06-28 |
| AHY704 | - | 2 | 2026-06-13 |
| AHY703 | - | 2 | 2026-06-13 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | AHY046 | BCN → GYD | Jul 26, 10:10 UTC | Jul 26, 22:40 UTC | 12h 30m |
| 2026-07-25 | AHY045 | GYD → BCN | Jul 25, 13:05 UTC | Jul 26, 08:25 UTC | 19h 21m |
| 2026-07-25 | AHY045 | GYD → BCN | Jul 25, 11:05 UTC | Jul 26, 08:25 UTC | 21h 21m |
| 2026-07-25 | AHY045 | GYD → BCN | Jul 25, 10:45 UTC | Jul 26, 08:25 UTC | 21h 41m |
| 2026-07-24 | AHY045 | GYD → BCN | Jul 24, 16:35 UTC | Jul 25, 08:35 UTC | 16h 0m |
| 2026-07-24 | AHY072 | VIE → GYD | Jul 24, 11:15 UTC | Jul 24, 14:15 UTC | 3h 0m |
| 2026-07-24 | AHY071 | GYD → VIE | Jul 24, 06:00 UTC | Jul 24, 09:50 UTC | 3h 50m |
| 2026-07-23 | AHY4026 | - | Jul 23, 22:05 UTC | Jul 24, 02:05 UTC | 4h 0m |
| 2026-07-23 | AHY4025 | - | Jul 23, 09:50 UTC | Jul 23, 20:50 UTC | 11h 0m |
| 2026-07-23 | AHY063 | GYD → BER | Jul 23, 03:55 UTC | Jul 23, 08:15 UTC | 4h 20m |
| 2026-07-21 | AHY108 | - | Jul 21, 21:05 UTC | Jul 22, 15:15 UTC | 18h 10m |
| 2026-07-21 | AHY108 | - | Jul 21, 19:05 UTC | Jul 22, 15:15 UTC | 20h 10m |
| 2026-07-21 | AHY4026 | - | Jul 21, 17:05 UTC | Jul 22, 15:15 UTC | 22h 10m |
| 2026-07-21 | AHY4026 | - | Jul 21, 16:55 UTC | Jul 22, 15:00 UTC | 22h 5m |
| 2026-07-20 | AHY4025 | - | Jul 20, 22:50 UTC | Jul 21, 15:40 UTC | 16h 50m |
| 2026-07-20 | AHY059 | GYD → BOM | Jul 20, 20:00 UTC | Jul 20, 21:05 UTC | 1h 5m |
| 2026-07-19 | AHY046 | - | Jul 19, 09:55 UTC | Jul 19, 14:20 UTC | 4h 25m |
| 2026-07-18 | AHY045 | - | Jul 18, 13:10 UTC | Jul 19, 08:05 UTC | 18h 55m |
| 2026-07-18 | AHY045 | - | Jul 18, 11:05 UTC | Jul 19, 08:05 UTC | 21h 0m |
| 2026-07-18 | AHY045 | MXP → BCN | Jul 18, 09:45 UTC | Jul 19, 08:05 UTC | 22h 20m |
| 2026-07-17 | AHY035 | TLV → MXP | Jul 17, 22:00 UTC | Jul 18, 08:05 UTC | 10h 6m |
| 2026-07-17 | AHY8042 | - | Jul 17, 10:25 UTC | Jul 17, 20:35 UTC | 10h 10m |
| 2026-07-16 | AHY5050 | AMM → GYD | Jul 16, 23:44 UTC | Jul 17, 08:54 UTC | 9h 10m |
| 2026-07-16 | AHY046 | BCN → ADJ | Jul 16, 12:14 UTC | Jul 16, 22:19 UTC | 10h 5m |
| 2026-07-15 | AHY045 | - | Jul 15, 17:15 UTC | Jul 16, 08:30 UTC | 15h 15m |
| 2026-07-15 | AHY175 | - | Jul 15, 15:00 UTC | Jul 15, 15:15 UTC | 15m |
| 2026-07-15 | AHY4004 | - | Jul 15, 01:00 UTC | Jul 15, 14:15 UTC | 13h 15m |
| 2026-07-14 | AHY4003 | BCN → LPL | Jul 14, 10:10 UTC | Jul 14, 23:15 UTC | 13h 4m |
| 2026-07-13 | AHY045 | - | Jul 13, 13:10 UTC | Jul 14, 08:30 UTC | 19h 20m |
| 2026-07-13 | AHY045 | - | Jul 13, 11:05 UTC | Jul 14, 08:30 UTC | 21h 25m |
| 2026-07-13 | AHY045 | MXP → BCN | Jul 13, 09:45 UTC | Jul 14, 08:30 UTC | 22h 45m |
| 2026-07-12 | AHY4004 | LPL → MXP | Jul 12, 13:25 UTC | Jul 13, 08:10 UTC | 18h 45m |
| 2026-07-12 | AHY4003 | - | Jul 12, 06:35 UTC | Jul 12, 12:25 UTC | 5h 50m |
| 2026-07-11 | AHY176 | - | Jul 11, 18:00 UTC | Jul 11, 19:50 UTC | 1h 50m |
| 2026-07-11 | AHY175 | - | Jul 11, 16:00 UTC | Jul 11, 16:25 UTC | 25m |
| 2026-07-11 | AHY056 | - | Jul 11, 09:05 UTC | Jul 11, 15:15 UTC | 6h 10m |
| 2026-07-11 | AHY055 | - | Jul 11, 04:30 UTC | Jul 11, 07:15 UTC | 2h 45m |
| 2026-07-10 | AHY8238 | - | Jul 10, 22:40 UTC | Jul 10, 23:05 UTC | 25m |
| 2026-07-10 | AHY8238 | - | Jul 10, 21:00 UTC | Jul 10, 21:30 UTC | 30m |
| 2026-07-10 | AHY8226 | - | Jul 10, 18:25 UTC | Jul 10, 18:50 UTC | 25m |
| 2026-07-10 | AHY072 | VIE → TBS | Jul 10, 11:15 UTC | Jul 10, 17:05 UTC | 5h 50m |
| 2026-07-10 | AHY071 | - | Jul 10, 06:00 UTC | Jul 10, 09:50 UTC | 3h 50m |
| 2026-07-09 | AHY5050 | - | Jul 9, 23:50 UTC | Jul 10, 02:40 UTC | 2h 50m |
| 2026-07-09 | AHY046 | - | Jul 9, 10:10 UTC | Jul 9, 22:30 UTC | 12h 20m |
| 2026-07-08 | AHY045 | - | Jul 8, 13:05 UTC | Jul 9, 08:20 UTC | 19h 15m |
| 2026-07-08 | AHY045 | PRG → BCN | Jul 8, 11:15 UTC | Jul 9, 08:20 UTC | 21h 5m |
| 2026-07-08 | AHY109 | DEL → PRG | Jul 8, 00:05 UTC | Jul 8, 09:50 UTC | 9h 45m |
| 2026-07-07 | AHY057 | GYD → DEL | Jul 7, 21:50 UTC | Jul 7, 22:40 UTC | 50m |
| 2026-07-07 | AHY046 | - | Jul 7, 10:55 UTC | Jul 7, 15:20 UTC | 4h 25m |
| 2026-07-06 | AHY045 | - | Jul 6, 13:05 UTC | Jul 7, 08:30 UTC | 19h 25m |
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-BAK page for operator, model, and routing details .