sensors Mode-S transponder
4246A3
ICAO 24-bit transponder address · allocated to United Kingdom
Currently assigned to VP-BMU · BOEING 777-200LR
- Hex
- 4246A3
- Octal
- 20443243
- Decimal
- 4,343,459
- Country
- GB
- Tail
- VP-BMU
- Type
- B77L
- Flights observed
- 231
- Distinct callsigns
- 20
- Country
- GB
- Last broadcast
- 54m ago
Current position
Country allocation
The ICAO 24-bit address 4246A3 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 |
|---|---|---|---|
| AZG6117 | - | 10 | 2026-06-28 |
| AZG8891 | Sakaviaservice | 9 | 2026-06-07 |
| AZG4861 | - | 8 | 2026-06-30 |
| AZG4862 | Sakaviaservice | 7 | 2026-04-17 |
| AZG785 | Sakaviaservice | 6 | 2026-04-16 |
| AZG6118 | - | 6 | 2026-06-28 |
| AZG4882 | Sakaviaservice | 6 | 2026-06-13 |
| AZG4881 | - | 6 | 2026-06-12 |
| AZG9933 | - | 5 | 2026-07-09 |
| AZG624 | - | 5 | 2026-07-13 |
| AZG6177 | - | 5 | 2026-06-26 |
| AZG6157 | - | 5 | 2026-07-10 |
| AZG7711 | - | 4 | 2026-06-21 |
| AZG6137 | - | 4 | 2026-07-01 |
| AZG4871 | Sakaviaservice | 4 | 2026-06-10 |
| AZG290 | - | 4 | 2026-06-19 |
| AZG276 | - | 4 | 2026-06-27 |
| AZG274 | - | 4 | 2026-07-02 |
| AZG205 | - | 4 | 2026-07-07 |
| AZG995 | - | 3 | 2026-05-21 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | AZG621 | - | Jul 13, 22:20 UTC | Jul 14, 02:45 UTC | 4h 25m |
| 2026-07-13 | AZG624 | ZGN → HKG | Jul 13, 18:30 UTC | Jul 13, 18:50 UTC | 20m |
| 2026-07-13 | AZG624 | - | Jul 13, 15:00 UTC | Jul 13, 16:50 UTC | 1h 50m |
| 2026-07-13 | AZG624 | - | Jul 13, 13:35 UTC | Jul 13, 13:45 UTC | 10m |
| 2026-07-13 | AZG3321 | - | Jul 13, 10:35 UTC | Jul 13, 10:55 UTC | 20m |
| 2026-07-12 | AZG1011 | - | Jul 12, 03:35 UTC | Jul 12, 03:55 UTC | 20m |
| 2026-07-12 | AZG1010 | - | Jul 12, 00:55 UTC | Jul 12, 01:30 UTC | 35m |
| 2026-07-11 | AZG996 | - | Jul 11, 14:45 UTC | Jul 11, 19:20 UTC | 4h 35m |
| 2026-07-11 | AZG6158 | - | Jul 11, 06:50 UTC | Jul 11, 07:30 UTC | 40m |
| 2026-07-10 | AZG6157 | - | Jul 10, 10:55 UTC | Jul 11, 04:55 UTC | 18h 0m |
| 2026-07-10 | AZG6157 | - | Jul 10, 08:50 UTC | Jul 11, 04:55 UTC | 20h 5m |
| 2026-07-10 | AZG6157 | - | Jul 10, 08:15 UTC | Jul 11, 04:55 UTC | 20h 40m |
| 2026-07-09 | AZG9934 | MAD → NRT | Jul 9, 09:30 UTC | Jul 10, 04:45 UTC | 19h 15m |
| 2026-07-09 | AZG9933 | - | Jul 9, 00:20 UTC | Jul 9, 05:35 UTC | 5h 15m |
| 2026-07-08 | AZG9933 | - | Jul 8, 05:55 UTC | Jul 9, 04:45 UTC | 22h 50m |
| 2026-07-07 | AZG206 | - | Jul 7, 17:35 UTC | Jul 7, 21:30 UTC | 3h 55m |
| 2026-07-07 | AZG205 | - | Jul 7, 00:10 UTC | Jul 7, 13:20 UTC | 13h 10m |
| 2026-07-06 | AZG625 | HKG → HKG | Jul 6, 22:00 UTC | Jul 6, 22:20 UTC | 20m |
| 2026-07-06 | AZG624 | - | Jul 6, 15:25 UTC | Jul 6, 19:20 UTC | 3h 55m |
| 2026-07-06 | AZG624 | - | Jul 6, 14:00 UTC | Jul 6, 14:10 UTC | 10m |
| 2026-07-06 | AZG3321 | - | Jul 6, 08:20 UTC | Jul 6, 08:55 UTC | 35m |
| 2026-07-05 | AZG534 | - | Jul 5, 12:50 UTC | Jul 6, 07:30 UTC | 18h 40m |
| 2026-07-05 | AZG534 | - | Jul 5, 12:10 UTC | Jul 6, 07:30 UTC | 19h 20m |
| 2026-07-04 | AZG278 | MXP → DAC | Jul 4, 21:25 UTC | Jul 5, 10:15 UTC | 12h 50m |
| 2026-07-04 | AZG6158 | ZAZ → MXP | Jul 4, 04:35 UTC | Jul 4, 17:50 UTC | 13h 15m |
| 2026-07-03 | AZG6157 | - | Jul 3, 20:15 UTC | Jul 4, 01:15 UTC | 5h 0m |
| 2026-07-02 | AZG334 | - | Jul 2, 18:15 UTC | Jul 2, 20:45 UTC | 2h 30m |
| 2026-07-02 | AZG274 | MXP → DAC | Jul 2, 04:05 UTC | Jul 2, 16:05 UTC | 12h 0m |
| 2026-07-01 | AZG273 | - | Jul 1, 23:35 UTC | Jul 2, 01:05 UTC | 1h 30m |
| 2026-07-01 | AZG6137 | - | Jul 1, 07:30 UTC | Jul 1, 20:15 UTC | 12h 45m |
| 2026-06-30 | AZG4872 | ORD → EMA | Jun 30, 22:35 UTC | Jul 1, 05:30 UTC | 6h 55m |
| 2026-06-30 | AZG4861 | - | Jun 30, 07:05 UTC | Jun 30, 15:30 UTC | 8h 25m |
| 2026-06-30 | AZG4861 | - | Jun 30, 00:55 UTC | Jun 30, 04:55 UTC | 4h 1m |
| 2026-06-29 | AZG3822 | - | Jun 29, 17:10 UTC | Jun 29, 20:59 UTC | 3h 50m |
| 2026-06-28 | AZG6118 | - | Jun 28, 21:45 UTC | Jun 29, 11:25 UTC | 13h 40m |
| 2026-06-28 | AZG6117 | - | Jun 28, 03:25 UTC | Jun 28, 18:55 UTC | 15h 30m |
| 2026-06-27 | AZG6117 | - | Jun 27, 22:49 UTC | Jun 28, 18:55 UTC | 20h 5m |
| 2026-06-27 | AZG6117 | - | Jun 27, 20:49 UTC | Jun 28, 18:55 UTC | 22h 5m |
| 2026-06-27 | AZG2891 | - | Jun 27, 18:45 UTC | Jun 28, 16:45 UTC | 22h 0m |
| 2026-06-27 | AZG276 | - | Jun 27, 06:59 UTC | Jun 27, 10:34 UTC | 3h 35m |
| 2026-06-27 | AZG6178 | - | Jun 27, 00:50 UTC | Jun 27, 02:14 UTC | 1h 25m |
| 2026-06-26 | AZG6177 | - | Jun 26, 08:45 UTC | Jun 26, 22:40 UTC | 13h 55m |
| 2026-06-26 | AZG6157 | - | Jun 26, 00:35 UTC | Jun 26, 05:24 UTC | 4h 50m |
| 2026-06-25 | AZG1224 | - | Jun 25, 18:19 UTC | Jun 25, 20:05 UTC | 1h 45m |
| 2026-06-25 | AZG1223 | - | Jun 25, 05:25 UTC | Jun 25, 16:29 UTC | 11h 5m |
| 2026-06-24 | AZG5951 | GYD → ATL | Jun 24, 16:34 UTC | Jun 25, 01:44 UTC | 9h 10m |
| 2026-06-23 | AZG5951 | GYD → ATL | Jun 23, 23:14 UTC | Jun 24, 12:40 UTC | 13h 25m |
| 2026-06-23 | AZG1148 | HKG → HKG | Jun 23, 20:24 UTC | Jun 23, 20:40 UTC | 15m |
| 2026-06-23 | AZG1147 | TAS → GYD | Jun 23, 09:05 UTC | Jun 23, 17:20 UTC | 8h 15m |
| 2026-06-23 | AZG8588 | - | Jun 23, 01:00 UTC | Jun 23, 04:45 UTC | 3h 45m |
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-BMU page for operator, model, and routing details .