sensors Mode-S transponder
4246A2
ICAO 24-bit transponder address · allocated to United Kingdom
Currently assigned to VP-BMG · BOEING 777-200LR
- Hex
- 4246A2
- Octal
- 20443242
- Decimal
- 4,343,458
- Country
- GB
- Tail
- VP-BMG
- Type
- B77L
- Flights observed
- 126
- Distinct callsigns
- 20
- Country
- GB
- Last broadcast
- 3h ago
Last known position
Country allocation
The ICAO 24-bit address 4246A2 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 |
|---|---|---|---|
| AZG4871 | Sakaviaservice | 12 | 2026-05-20 |
| AZG788 | Sakaviaservice | 5 | 2026-04-18 |
| AZG785 | Sakaviaservice | 5 | 2026-04-22 |
| AZG1403 | Sakaviaservice | 5 | 2026-05-23 |
| AZG8582 | - | 4 | 2026-05-18 |
| AZG6961 | - | 4 | 2026-04-13 |
| AZG6762 | - | 4 | 2026-04-13 |
| AZG4862 | Sakaviaservice | 4 | 2026-05-09 |
| AZG9934 | - | 3 | 2026-04-16 |
| AZG9933 | Sakaviaservice | 3 | 2026-04-16 |
| AZG784 | Sakaviaservice | 3 | 2026-05-21 |
| AZG692 | Sakaviaservice | 3 | 2026-04-27 |
| AZG6681 | - | 3 | 2026-04-17 |
| AZG6137 | - | 3 | 2026-05-28 |
| AZG236 | Sakaviaservice | 3 | 2026-04-15 |
| AZG235 | - | 3 | 2026-04-14 |
| AZG1404 | - | 3 | 2026-05-24 |
| AZG8581 | - | 2 | 2026-05-04 |
| AZG8116 | Sakaviaservice | 2 | 2026-05-07 |
| AZG6682 | - | 2 | 2026-04-17 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | AZG1581 | - | May 30, 04:40 UTC | May 30, 06:15 UTC | 1h 35m |
| 2026-05-30 | AZG5951 | GYD → ATL | May 30, 02:40 UTC | May 30, 02:50 UTC | 10m |
| 2026-05-29 | AZG5951 | GYD → ATL | May 29, 22:55 UTC | May 30, 02:00 UTC | 3h 5m |
| 2026-05-29 | AZG1406 | - | May 29, 14:05 UTC | May 29, 15:55 UTC | 1h 51m |
| 2026-05-29 | AZG1405 | BUD → IST | May 29, 09:20 UTC | May 29, 12:25 UTC | 3h 5m |
| 2026-05-28 | AZG6137 | - | May 28, 18:50 UTC | May 29, 06:50 UTC | 12h 0m |
| 2026-05-28 | AZG6137 | - | May 28, 07:15 UTC | May 29, 06:30 UTC | 23h 15m |
| 2026-05-27 | AZG2093 | - | May 27, 20:35 UTC | May 28, 18:50 UTC | 22h 15m |
| 2026-05-27 | AZG204 | AMS → GYD | May 27, 16:45 UTC | May 28, 07:40 UTC | 14h 55m |
| 2026-05-26 | AZG203 | BRU → GYD | May 26, 19:50 UTC | May 27, 14:10 UTC | 18h 21m |
| 2026-05-26 | AZG1147 | TAS → GYD | May 26, 16:05 UTC | May 26, 16:40 UTC | 35m |
| 2026-05-25 | AZG217 | TLV → GYD | May 25, 06:45 UTC | May 25, 08:55 UTC | 2h 10m |
| 2026-05-24 | AZG208 | AMS → GYD | May 24, 16:05 UTC | May 25, 03:15 UTC | 11h 10m |
| 2026-05-24 | AZG207 | GYD → AMS | May 24, 08:05 UTC | May 24, 12:35 UTC | 4h 30m |
| 2026-05-24 | AZG1404 | - | May 24, 00:50 UTC | May 24, 01:55 UTC | 1h 5m |
| 2026-05-23 | AZG1403 | STN → GYD | May 23, 20:45 UTC | May 23, 20:55 UTC | 10m |
| 2026-05-23 | AZG1403 | STN → GYD | May 23, 18:40 UTC | May 23, 20:00 UTC | 1h 20m |
| 2026-05-21 | AZG5156 | - | May 21, 08:35 UTC | May 22, 03:45 UTC | 19h 10m |
| 2026-05-21 | AZG784 | ORD → GYD | May 21, 06:40 UTC | May 22, 03:45 UTC | 21h 5m |
| 2026-05-20 | AZG784 | ORD → GYD | May 20, 19:45 UTC | May 21, 03:20 UTC | 7h 35m |
| 2026-05-20 | AZG4871 | GYD → ORD | May 20, 01:20 UTC | May 20, 10:15 UTC | 8h 56m |
| 2026-05-19 | AZG4871 | GYD → ORD | May 19, 04:35 UTC | May 19, 23:40 UTC | 19h 5m |
| 2026-05-19 | AZG4871 | GYD → ORD | May 19, 02:55 UTC | May 19, 23:40 UTC | 20h 45m |
| 2026-05-18 | AZG8582 | - | May 18, 19:35 UTC | May 19, 14:05 UTC | 18h 30m |
| 2026-05-18 | AZG202 | AMS → GYD | May 18, 16:35 UTC | May 19, 14:05 UTC | 21h 29m |
| 2026-05-18 | AZG202 | AMS → GYD | May 18, 16:00 UTC | May 19, 14:05 UTC | 22h 4m |
| 2026-05-17 | AZG201 | GYD → AMS | May 17, 20:45 UTC | May 18, 12:30 UTC | 15h 45m |
| 2026-05-17 | AZG334 | - | May 17, 04:15 UTC | May 17, 18:25 UTC | 14h 10m |
| 2026-05-16 | AZG3096 | - | May 16, 11:41 UTC | May 17, 01:05 UTC | 13h 25m |
| 2026-05-15 | AZG3237 | - | May 15, 14:45 UTC | May 16, 07:51 UTC | 17h 5m |
| 2026-05-15 | AZG3237 | - | May 15, 08:35 UTC | May 16, 07:51 UTC | 23h 15m |
| 2026-05-15 | AZG902 | NRT → GYD | May 15, 08:15 UTC | May 16, 06:31 UTC | 22h 15m |
| 2026-05-14 | AZG901 | - | May 14, 10:35 UTC | May 15, 05:45 UTC | 19h 10m |
| 2026-05-14 | AZG234 | HHN → GYD | May 14, 02:45 UTC | May 14, 06:35 UTC | 3h 50m |
| 2026-05-13 | AZG233 | GYD → HHN | May 13, 19:35 UTC | May 13, 23:55 UTC | 4h 20m |
| 2026-05-13 | AZG6138 | - | May 13, 10:20 UTC | May 13, 14:40 UTC | 4h 20m |
| 2026-05-12 | AZG6137 | MXP → ZAZ | May 12, 16:25 UTC | May 13, 06:40 UTC | 14h 15m |
| 2026-05-12 | AZG271 | GYD → MXP | May 12, 12:05 UTC | May 12, 13:25 UTC | 1h 20m |
| 2026-05-11 | AZG6117 | IAH → LUX | May 11, 15:20 UTC | May 12, 09:30 UTC | 18h 11m |
| 2026-05-11 | AZG1133 | GYD → DAC | May 11, 10:35 UTC | May 11, 12:40 UTC | 2h 5m |
| 2026-05-11 | AZG1404 | - | May 11, 00:45 UTC | May 11, 02:30 UTC | 1h 45m |
| 2026-05-10 | AZG1403 | STN → GYD | May 10, 19:54 UTC | May 10, 21:14 UTC | 1h 20m |
| 2026-05-10 | AZG5334 | - | May 10, 11:20 UTC | May 10, 13:40 UTC | 2h 20m |
| 2026-05-09 | AZG4862 | ORD → GYD | May 9, 19:00 UTC | May 10, 09:05 UTC | 14h 5m |
| 2026-05-09 | AZG4862 | ORD → GYD | May 9, 02:30 UTC | May 9, 10:10 UTC | 7h 40m |
| 2026-05-08 | AZG4871 | GYD → ORD | May 8, 14:00 UTC | May 8, 23:00 UTC | 9h 0m |
| 2026-05-07 | AZG4871 | GYD → ORD | May 7, 20:45 UTC | May 8, 12:04 UTC | 15h 20m |
| 2026-05-07 | AZG8116 | JFK → LGG | May 7, 02:30 UTC | May 7, 17:30 UTC | 15h 0m |
| 2026-05-06 | AZG8116 | JFK → LGG | May 6, 15:40 UTC | May 6, 23:10 UTC | 7h 29m |
| 2026-05-06 | AZG4871 | GYD → ORD | May 6, 04:00 UTC | May 6, 12:50 UTC | 8h 50m |
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-BMG page for operator, model, and routing details .