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
- 129
- Distinct callsigns
- 20
- Country
- GB
- Last broadcast
- 14h ago
Last known 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 | Sakaviaservice | 7 | 2026-04-30 |
| AZG4862 | Sakaviaservice | 7 | 2026-04-17 |
| AZG785 | Sakaviaservice | 6 | 2026-04-16 |
| AZG4861 | - | 6 | 2026-04-14 |
| AZG6118 | Sakaviaservice | 5 | 2026-05-01 |
| AZG4882 | - | 5 | 2026-04-14 |
| AZG4881 | Sakaviaservice | 4 | 2026-05-04 |
| AZG995 | - | 3 | 2026-05-21 |
| AZG9791 | Sakaviaservice | 3 | 2026-05-05 |
| AZG8891 | Sakaviaservice | 3 | 2026-04-17 |
| AZG290 | Sakaviaservice | 3 | 2026-05-17 |
| AZG276 | Sakaviaservice | 3 | 2026-05-17 |
| AZG275 | Sakaviaservice | 3 | 2026-05-17 |
| AZG274 | - | 3 | 2026-05-22 |
| AZG922 | Sakaviaservice | 2 | 2026-04-27 |
| AZG902 | Sakaviaservice | 2 | 2026-05-29 |
| AZG901 | - | 2 | 2026-05-28 |
| AZG8582 | - | 2 | 2026-04-15 |
| AZG8581 | - | 2 | 2026-04-15 |
| AZG3236 | Sakaviaservice | 2 | 2026-05-23 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | AZG902 | NRT → GYD | May 29, 08:20 UTC | May 29, 10:25 UTC | 2h 5m |
| 2026-05-28 | AZG901 | - | May 28, 11:30 UTC | May 29, 05:00 UTC | 17h 30m |
| 2026-05-28 | AZG3319 | GYD → BOM | May 28, 07:30 UTC | May 28, 07:50 UTC | 20m |
| 2026-05-27 | AZG3220 | - | May 27, 16:05 UTC | May 28, 06:45 UTC | 14h 40m |
| 2026-05-26 | AZG1134 | DAC → GYD | May 26, 23:19 UTC | May 27, 12:05 UTC | 12h 46m |
| 2026-05-26 | AZG1133 | GYD → DAC | May 26, 19:10 UTC | May 26, 21:20 UTC | 2h 10m |
| 2026-05-24 | AZG902 | NRT → GYD | May 24, 05:15 UTC | May 24, 12:10 UTC | 6h 55m |
| 2026-05-23 | AZG901 | - | May 23, 22:30 UTC | May 24, 00:25 UTC | 1h 55m |
| 2026-05-23 | AZG3236 | HHN → GYD | May 23, 09:00 UTC | May 23, 13:00 UTC | 4h 0m |
| 2026-05-23 | AZG9892 | - | May 23, 01:00 UTC | May 23, 04:55 UTC | 3h 54m |
| 2026-05-22 | AZG274 | - | May 22, 05:50 UTC | May 22, 09:40 UTC | 3h 50m |
| 2026-05-22 | AZG273 | JFK → MXP | May 22, 01:00 UTC | May 22, 02:30 UTC | 1h 30m |
| 2026-05-21 | AZG996 | MAD → ZAZ | May 21, 09:20 UTC | May 21, 22:45 UTC | 13h 25m |
| 2026-05-21 | AZG995 | - | May 21, 00:35 UTC | May 21, 05:40 UTC | 5h 5m |
| 2026-05-20 | AZG995 | - | May 20, 06:50 UTC | May 21, 05:40 UTC | 22h 50m |
| 2026-05-20 | AZG995 | - | May 20, 06:40 UTC | May 21, 04:45 UTC | 22h 5m |
| 2026-05-19 | AZG206 | AMS → AMS | May 19, 16:50 UTC | May 20, 07:00 UTC | 14h 11m |
| 2026-05-19 | AZG205 | GYD → GYD | May 19, 09:30 UTC | May 19, 14:05 UTC | 4h 35m |
| 2026-05-19 | AZG1404 | - | May 19, 00:45 UTC | May 19, 02:40 UTC | 1h 55m |
| 2026-05-18 | AZG1403 | STN → GYD | May 18, 21:45 UTC | May 18, 21:55 UTC | 10m |
| 2026-05-18 | AZG3822 | HHN → GYD | May 18, 11:25 UTC | May 18, 21:05 UTC | 9h 39m |
| 2026-05-18 | AZG3821 | - | May 18, 04:05 UTC | May 18, 08:25 UTC | 4h 20m |
| 2026-05-17 | AZG276 | MXP → GYD | May 17, 19:15 UTC | May 17, 22:50 UTC | 3h 35m |
| 2026-05-17 | AZG275 | MAD → GYD | May 17, 12:55 UTC | May 17, 17:05 UTC | 4h 10m |
| 2026-05-17 | AZG292 | - | May 17, 03:45 UTC | May 17, 07:15 UTC | 3h 30m |
| 2026-05-17 | AZG290 | MAD → MXP | May 17, 00:00 UTC | May 17, 01:20 UTC | 1h 20m |
| 2026-05-16 | AZG6177 | - | May 16, 08:51 UTC | May 16, 21:30 UTC | 12h 40m |
| 2026-05-15 | AZG4872 | ORD → EMA | May 15, 22:55 UTC | May 16, 06:45 UTC | 7h 51m |
| 2026-05-15 | AZG1224 | ATL → ORD | May 15, 16:25 UTC | May 15, 18:05 UTC | 1h 40m |
| 2026-05-15 | AZG1324 | - | May 15, 04:20 UTC | May 15, 13:15 UTC | 8h 55m |
| 2026-05-14 | AZG1324 | - | May 14, 21:30 UTC | May 15, 01:35 UTC | 4h 5m |
| 2026-05-14 | AZG1224 | - | May 14, 15:45 UTC | May 14, 16:50 UTC | 1h 5m |
| 2026-05-14 | AZG1223 | JFK → IST | May 14, 10:20 UTC | May 14, 11:35 UTC | 1h 15m |
| 2026-05-14 | AZG274 | - | May 14, 03:05 UTC | May 14, 06:40 UTC | 3h 35m |
| 2026-05-13 | AZG273 | JFK → MXP | May 13, 19:55 UTC | May 14, 00:00 UTC | 4h 5m |
| 2026-05-13 | AZG3234 | HHN → GYD | May 13, 12:00 UTC | May 13, 15:50 UTC | 3h 50m |
| 2026-05-13 | AZG3233 | - | May 13, 08:00 UTC | May 13, 08:50 UTC | 50m |
| 2026-05-12 | AZG323 | GYD → STN | May 12, 15:25 UTC | May 13, 06:00 UTC | 14h 35m |
| 2026-05-12 | AZG205 | GYD → GYD | May 12, 07:45 UTC | May 12, 12:25 UTC | 4h 40m |
| 2026-05-11 | AZG202 | AMS → GYD | May 11, 16:25 UTC | May 11, 20:30 UTC | 4h 5m |
| 2026-05-11 | AZG201 | GYD → AMS | May 11, 00:15 UTC | May 11, 14:10 UTC | 13h 55m |
| 2026-05-10 | AZG3237 | - | May 10, 08:00 UTC | May 10, 20:00 UTC | 12h 0m |
| 2026-05-10 | AZG3219 | GYD → DEL | May 10, 04:09 UTC | May 10, 04:55 UTC | 45m |
| 2026-05-09 | AZG208 | AMS → GYD | May 9, 18:20 UTC | May 9, 22:20 UTC | 4h 0m |
| 2026-05-09 | AZG207 | GYD → AMS | May 9, 08:20 UTC | May 9, 13:05 UTC | 4h 45m |
| 2026-05-08 | AZG752 | LGG → GYD | May 8, 23:30 UTC | May 9, 03:40 UTC | 4h 10m |
| 2026-05-08 | AZG751 | GYD → GYD | May 8, 08:05 UTC | May 8, 20:20 UTC | 12h 15m |
| 2026-05-07 | AZG3235 | - | May 7, 23:39 UTC | May 8, 03:55 UTC | 4h 15m |
| 2026-05-06 | AZG6138 | - | May 6, 18:55 UTC | May 6, 23:30 UTC | 4h 35m |
| 2026-05-06 | AZG6137 | DAC → ZAZ | May 6, 02:20 UTC | May 6, 16:20 UTC | 14h 0m |
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 .