sensors Mode-S transponder
4246B2
ICAO 24-bit transponder address · allocated to United Kingdom
Currently assigned to VP-BAA · BOEING 777-200LR
- Hex
- 4246B2
- Octal
- 20443262
- Decimal
- 4,343,474
- Country
- GB
- Tail
- VP-BAA
- Type
- B77L
- Flights observed
- 123
- Distinct callsigns
- 20
- Country
- GB
- Last broadcast
- 2h ago
Last known position
Country allocation
The ICAO 24-bit address 4246B2 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 |
|---|---|---|---|
| AZG4861 | Sakaviaservice | 8 | 2026-05-28 |
| AZG324 | Sakaviaservice | 6 | 2026-05-05 |
| AZG323 | Sakaviaservice | 6 | 2026-05-18 |
| AZG901 | - | 5 | 2026-05-01 |
| AZG4881 | Sakaviaservice | 5 | 2026-05-16 |
| AZG8116 | Sakaviaservice | 4 | 2026-05-27 |
| AZG691 | - | 4 | 2026-04-13 |
| AZG4862 | Sakaviaservice | 4 | 2026-05-29 |
| AZG1224 | - | 4 | 2026-05-13 |
| AZG3822 | - | 3 | 2026-04-14 |
| AZG333 | Sakaviaservice | 3 | 2026-05-06 |
| AZG235 | Sakaviaservice | 3 | 2026-05-01 |
| AZG1923 | Sakaviaservice | 3 | 2026-04-16 |
| AZG9790 | Sakaviaservice | 2 | 2026-05-10 |
| AZG923 | Sakaviaservice | 2 | 2026-05-18 |
| AZG8582 | - | 2 | 2026-04-27 |
| AZG4882 | Sakaviaservice | 2 | 2026-05-10 |
| AZG3821 | - | 2 | 2026-04-20 |
| AZG236 | Sakaviaservice | 2 | 2026-05-02 |
| AZG207 | Sakaviaservice | 2 | 2026-04-18 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | AZG4862 | ORD → GYD | May 29, 03:10 UTC | May 29, 23:10 UTC | 20h 0m |
| 2026-05-28 | AZG4861 | GYD → ORD | May 28, 13:55 UTC | May 28, 22:05 UTC | 8h 10m |
| 2026-05-27 | AZG4861 | GYD → ORD | May 27, 21:55 UTC | May 28, 12:15 UTC | 14h 20m |
| 2026-05-27 | AZG8988 | - | May 27, 21:10 UTC | May 27, 21:20 UTC | 10m |
| 2026-05-27 | AZG8116 | JFK → LGG | May 27, 02:39 UTC | May 27, 17:30 UTC | 14h 50m |
| 2026-05-26 | AZG8116 | JFK → LGG | May 26, 16:30 UTC | May 27, 00:14 UTC | 7h 45m |
| 2026-05-26 | AZG4861 | GYD → ORD | May 26, 04:15 UTC | May 26, 13:00 UTC | 8h 45m |
| 2026-05-25 | AZG4861 | GYD → ORD | May 25, 10:00 UTC | May 26, 02:35 UTC | 16h 34m |
| 2026-05-25 | AZG1681 | - | May 25, 02:45 UTC | May 25, 06:40 UTC | 3h 55m |
| 2026-05-24 | AZG285 | VIE → GYD | May 24, 17:15 UTC | May 24, 20:25 UTC | 3h 10m |
| 2026-05-24 | AZG284 | GYD → VIE | May 24, 11:30 UTC | May 24, 14:45 UTC | 3h 15m |
| 2026-05-24 | AZG238 | HHN → GYD | May 24, 01:50 UTC | May 24, 05:40 UTC | 3h 50m |
| 2026-05-23 | AZG237 | GYD → HHN | May 23, 18:30 UTC | May 23, 22:45 UTC | 4h 15m |
| 2026-05-22 | AZG122 | - | May 22, 03:50 UTC | May 22, 09:20 UTC | 5h 30m |
| 2026-05-22 | AZG121 | - | May 22, 00:20 UTC | May 22, 00:40 UTC | 20m |
| 2026-05-21 | AZG9804 | EBL → GYD | May 21, 11:35 UTC | May 21, 23:30 UTC | 11h 55m |
| 2026-05-21 | AZG9803 | ORD → HHN | May 21, 05:30 UTC | May 21, 05:40 UTC | 10m |
| 2026-05-20 | AZG3099 | - | May 20, 19:10 UTC | May 20, 21:45 UTC | 2h 35m |
| 2026-05-20 | AZG6118 | IAH → GYD | May 20, 02:35 UTC | May 20, 15:30 UTC | 12h 56m |
| 2026-05-19 | AZG6117 | IAH → LUX | May 19, 09:20 UTC | May 19, 22:35 UTC | 13h 15m |
| 2026-05-18 | AZG323 | GYD → STN | May 18, 10:35 UTC | May 19, 05:45 UTC | 19h 9m |
| 2026-05-18 | AZG323 | GYD → STN | May 18, 10:25 UTC | May 19, 05:45 UTC | 19h 19m |
| 2026-05-18 | AZG923 | HKG → GYD | May 18, 07:25 UTC | May 18, 07:40 UTC | 15m |
| 2026-05-17 | AZG1147 | TAS → GYD | May 17, 13:15 UTC | May 18, 04:30 UTC | 15h 15m |
| 2026-05-17 | AZG4862 | ORD → GYD | May 17, 00:10 UTC | May 17, 07:45 UTC | 7h 35m |
| 2026-05-16 | AZG4881 | LGG → GYD | May 16, 08:16 UTC | May 16, 20:35 UTC | 12h 20m |
| 2026-05-16 | AZG4881 | LGG → GYD | May 16, 00:35 UTC | May 16, 20:35 UTC | 20h 0m |
| 2026-05-15 | AZG4881 | LGG → GYD | May 15, 22:35 UTC | May 16, 20:35 UTC | 22h 0m |
| 2026-05-15 | AZG4881 | LGG → GYD | May 15, 21:45 UTC | May 16, 20:30 UTC | 22h 45m |
| 2026-05-15 | AZG1581 | - | May 15, 13:55 UTC | May 15, 17:45 UTC | 3h 49m |
| 2026-05-15 | AZG3236 | HHN → GYD | May 15, 03:10 UTC | May 15, 07:20 UTC | 4h 10m |
| 2026-05-14 | AZG3235 | - | May 14, 10:20 UTC | May 15, 00:15 UTC | 13h 55m |
| 2026-05-14 | AZG9791 | ORD → LUX | May 14, 00:50 UTC | May 14, 08:40 UTC | 7h 50m |
| 2026-05-13 | AZG1224 | ATL → ORD | May 13, 14:45 UTC | May 13, 16:30 UTC | 1h 45m |
| 2026-05-13 | AZG1224 | - | May 13, 02:50 UTC | May 13, 12:20 UTC | 9h 30m |
| 2026-05-12 | AZG1224 | - | May 12, 04:35 UTC | May 12, 23:25 UTC | 18h 50m |
| 2026-05-12 | AZG1224 | - | May 12, 04:10 UTC | May 12, 23:25 UTC | 19h 15m |
| 2026-05-11 | AZG1147 | TAS → GYD | May 11, 05:35 UTC | May 11, 22:10 UTC | 16h 36m |
| 2026-05-10 | AZG4882 | ORD → HHN | May 10, 18:29 UTC | May 11, 01:55 UTC | 7h 25m |
| 2026-05-10 | AZG9790 | ORD → IAH | May 10, 06:20 UTC | May 10, 15:09 UTC | 8h 50m |
| 2026-05-09 | AZG9790 | ORD → IAH | May 9, 14:45 UTC | May 10, 04:09 UTC | 13h 25m |
| 2026-05-09 | AZG1572 | HKG → HKG | May 9, 12:00 UTC | May 9, 12:15 UTC | 15m |
| 2026-05-08 | AZG5744 | BUD → HKG | May 8, 14:25 UTC | May 9, 08:20 UTC | 17h 55m |
| 2026-05-08 | AZG5743 | - | May 8, 10:09 UTC | May 8, 12:20 UTC | 2h 10m |
| 2026-05-07 | AZG6157 | - | May 7, 12:45 UTC | May 8, 06:35 UTC | 17h 50m |
| 2026-05-06 | AZG333 | GYD → DAC | May 6, 14:50 UTC | May 7, 10:25 UTC | 19h 35m |
| 2026-05-06 | AZG3320 | - | May 6, 08:50 UTC | May 6, 15:10 UTC | 6h 20m |
| 2026-05-05 | AZG324 | GYD → RUH | May 5, 14:40 UTC | May 6, 09:05 UTC | 18h 25m |
| 2026-05-05 | AZG324 | GYD → RUH | May 5, 12:35 UTC | May 6, 09:05 UTC | 20h 30m |
| 2026-05-05 | AZG324 | GYD → RUH | May 5, 10:45 UTC | May 6, 09:05 UTC | 22h 20m |
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-BAA page for operator, model, and routing details .