sensors Mode-S transponder
4246B3
ICAO 24-bit transponder address · allocated to United Kingdom
Currently assigned to VP-BAU · BOEING 777-200LR
- Hex
- 4246B3
- Octal
- 20443263
- Decimal
- 4,343,475
- Country
- GB
- Tail
- VP-BAU
- Type
- B77L
- Flights observed
- 122
- Distinct callsigns
- 20
- Country
- GB
- Last broadcast
- 44m ago
Last known position
Country allocation
The ICAO 24-bit address 4246B3 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 |
|---|---|---|---|
| AZG1581 | - | 6 | 2026-05-22 |
| AZG9934 | Sakaviaservice | 5 | 2026-05-27 |
| AZG8892 | - | 5 | 2026-05-15 |
| AZG6117 | Sakaviaservice | 5 | 2026-05-27 |
| AZG9933 | Sakaviaservice | 4 | 2026-05-26 |
| AZG783 | Sakaviaservice | 4 | 2026-04-19 |
| AZG6118 | Sakaviaservice | 4 | 2026-05-28 |
| AZG4881 | Sakaviaservice | 4 | 2026-05-23 |
| AZG134 | - | 4 | 2026-05-14 |
| AZG903 | - | 3 | 2026-04-13 |
| AZG784 | Sakaviaservice | 3 | 2026-05-08 |
| AZG6217 | - | 3 | 2026-05-01 |
| AZG6177 | - | 3 | 2026-05-09 |
| AZG534 | Sakaviaservice | 3 | 2026-05-25 |
| AZG4871 | Sakaviaservice | 3 | 2026-05-13 |
| AZG237 | Sakaviaservice | 3 | 2026-04-16 |
| AZG207 | Sakaviaservice | 3 | 2026-05-15 |
| AZG904 | - | 2 | 2026-04-13 |
| AZG902 | Sakaviaservice | 2 | 2026-04-17 |
| AZG901 | - | 2 | 2026-04-17 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | AZG692 | HKG → GYD | May 30, 02:00 UTC | May 30, 04:45 UTC | 2h 45m |
| 2026-05-29 | AZG692 | HKG → GYD | May 29, 23:35 UTC | May 29, 23:50 UTC | 15m |
| 2026-05-29 | AZG691 | - | May 29, 20:00 UTC | May 29, 20:20 UTC | 20m |
| 2026-05-29 | AZG274 | - | May 29, 00:45 UTC | May 29, 04:20 UTC | 3h 35m |
| 2026-05-28 | AZG273 | JFK → MXP | May 28, 17:40 UTC | May 28, 22:00 UTC | 4h 20m |
| 2026-05-28 | AZG232 | HHN → GYD | May 28, 09:25 UTC | May 28, 13:10 UTC | 3h 45m |
| 2026-05-28 | AZG6118 | IAH → GYD | May 28, 04:20 UTC | May 28, 05:55 UTC | 1h 35m |
| 2026-05-27 | AZG6117 | IAH → LUX | May 27, 20:45 UTC | May 28, 01:40 UTC | 4h 55m |
| 2026-05-27 | AZG9934 | MAD → MAD | May 27, 12:20 UTC | May 27, 17:20 UTC | 5h 0m |
| 2026-05-26 | AZG9933 | GYD → MAD | May 26, 20:54 UTC | May 27, 08:30 UTC | 11h 35m |
| 2026-05-26 | AZG9933 | GYD → MAD | May 26, 09:59 UTC | May 27, 08:30 UTC | 22h 30m |
| 2026-05-25 | AZG534 | DAC → GYD | May 25, 18:55 UTC | May 26, 10:05 UTC | 15h 10m |
| 2026-05-25 | AZG5334 | DAC → DAC | May 25, 03:20 UTC | May 25, 16:20 UTC | 13h 0m |
| 2026-05-24 | AZG5156 | - | May 24, 20:10 UTC | May 24, 21:00 UTC | 50m |
| 2026-05-24 | AZG4862 | ORD → GYD | May 24, 11:40 UTC | May 24, 16:55 UTC | 5h 15m |
| 2026-05-23 | AZG4862 | ORD → GYD | May 23, 22:00 UTC | May 24, 05:55 UTC | 7h 55m |
| 2026-05-23 | AZG4881 | LGG → GYD | May 23, 09:55 UTC | May 23, 18:35 UTC | 8h 41m |
| 2026-05-22 | AZG4881 | LGG → GYD | May 22, 17:45 UTC | May 23, 07:15 UTC | 13h 30m |
| 2026-05-22 | AZG1581 | - | May 22, 01:35 UTC | May 22, 13:35 UTC | 12h 0m |
| 2026-05-20 | AZG281 | VIE → JFK | May 20, 18:50 UTC | May 20, 22:00 UTC | 3h 10m |
| 2026-05-20 | AZG280 | GYD → VIE | May 20, 02:35 UTC | May 20, 15:05 UTC | 12h 31m |
| 2026-05-19 | AZG3637 | DAC → DAC | May 19, 09:50 UTC | May 19, 23:55 UTC | 14h 5m |
| 2026-05-19 | AZG3636 | - | May 19, 04:35 UTC | May 19, 07:25 UTC | 2h 50m |
| 2026-05-16 | AZG208 | AMS → GYD | May 16, 18:50 UTC | May 17, 18:35 UTC | 23h 45m |
| 2026-05-16 | AZG208 | AMS → GYD | May 16, 17:20 UTC | May 16, 21:30 UTC | 4h 10m |
| 2026-05-15 | AZG207 | GYD → AMS | May 15, 18:50 UTC | May 16, 14:20 UTC | 19h 31m |
| 2026-05-15 | AZG207 | GYD → AMS | May 15, 18:00 UTC | May 16, 14:20 UTC | 20h 21m |
| 2026-05-15 | AZG207 | GYD → AMS | May 15, 14:50 UTC | May 16, 14:20 UTC | 23h 31m |
| 2026-05-15 | AZG8892 | - | May 15, 14:25 UTC | May 16, 12:45 UTC | 22h 20m |
| 2026-05-15 | AZG8892 | - | May 15, 07:35 UTC | May 16, 02:55 UTC | 19h 19m |
| 2026-05-15 | AZG8891 | GYD → SGN | May 15, 02:05 UTC | May 16, 00:45 UTC | 22h 39m |
| 2026-05-14 | AZG134 | - | May 14, 16:50 UTC | May 15, 16:40 UTC | 23h 49m |
| 2026-05-14 | AZG134 | - | May 14, 15:50 UTC | May 15, 08:10 UTC | 16h 20m |
| 2026-05-13 | AZG8116 | JFK → LGG | May 13, 23:00 UTC | May 14, 13:15 UTC | 14h 15m |
| 2026-05-13 | AZG8116 | JFK → LGG | May 13, 13:05 UTC | May 13, 20:45 UTC | 7h 40m |
| 2026-05-13 | AZG4871 | GYD → ORD | May 13, 01:25 UTC | May 13, 10:20 UTC | 8h 55m |
| 2026-05-12 | AZG4871 | GYD → ORD | May 12, 04:50 UTC | May 12, 23:40 UTC | 18h 50m |
| 2026-05-12 | AZG4871 | GYD → ORD | May 12, 02:55 UTC | May 12, 23:40 UTC | 20h 45m |
| 2026-05-11 | AZG8582 | - | May 11, 14:50 UTC | May 12, 12:55 UTC | 22h 6m |
| 2026-05-11 | AZG8582 | - | May 11, 13:35 UTC | May 12, 12:45 UTC | 23h 11m |
| 2026-05-11 | AZG280 | GYD → VIE | May 11, 07:40 UTC | May 11, 11:10 UTC | 3h 30m |
| 2026-05-09 | AZG6178 | - | May 9, 23:44 UTC | May 10, 04:15 UTC | 4h 30m |
| 2026-05-09 | AZG6177 | - | May 9, 03:25 UTC | May 9, 20:20 UTC | 16h 55m |
| 2026-05-08 | AZG6177 | - | May 8, 23:10 UTC | May 9, 20:20 UTC | 21h 10m |
| 2026-05-08 | AZG6177 | - | May 8, 21:25 UTC | May 9, 20:20 UTC | 22h 55m |
| 2026-05-08 | AZG8892 | - | May 8, 17:40 UTC | May 9, 16:20 UTC | 22h 40m |
| 2026-05-08 | AZG8892 | - | May 8, 10:49 UTC | May 9, 07:35 UTC | 20h 45m |
| 2026-05-08 | AZG8892 | - | May 8, 08:49 UTC | May 9, 07:35 UTC | 22h 45m |
| 2026-05-08 | AZG784 | ORD → GYD | May 8, 08:40 UTC | May 9, 06:45 UTC | 22h 5m |
| 2026-05-07 | AZG784 | ORD → GYD | May 7, 21:50 UTC | May 8, 05:39 UTC | 7h 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-BAU page for operator, model, and routing details .