sensors Mode-S transponder
42441F
ICAO 24-bit transponder address · allocated to United Kingdom
Currently assigned to VQ-BBM · BOEING 747-8
- Hex
- 42441F
- Octal
- 20442037
- Decimal
- 4,342,815
- Country
- GB
- Tail
- VQ-BBM
- Type
- B748
- Flights observed
- 86
- Distinct callsigns
- 20
- Country
- GB
- Last broadcast
- 42m ago
Last known position
Country allocation
The ICAO 24-bit address 42441F 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 |
|---|---|---|---|
| AZG203 | Sakaviaservice | 6 | 2026-05-21 |
| AZG148 | Sakaviaservice | 5 | 2026-05-26 |
| AZG624 | - | 4 | 2026-05-18 |
| AZG922 | Sakaviaservice | 3 | 2026-05-17 |
| AZG904 | Sakaviaservice | 3 | 2026-05-24 |
| AZG8592 | - | 3 | 2026-05-23 |
| AZG631 | - | 3 | 2026-05-29 |
| AZG6117 | Sakaviaservice | 3 | 2026-04-17 |
| AZG571 | Sakaviaservice | 3 | 2026-05-09 |
| AZG274 | - | 3 | 2026-04-17 |
| AZG204 | Sakaviaservice | 3 | 2026-05-21 |
| AZG147 | - | 3 | 2026-05-26 |
| AZG1148 | Sakaviaservice | 3 | 2026-05-19 |
| AZG903 | - | 2 | 2026-05-03 |
| AZG711 | - | 2 | 2026-04-13 |
| AZG632 | Sakaviaservice | 2 | 2026-05-30 |
| AZG625 | Sakaviaservice | 2 | 2026-05-17 |
| AZG4871 | Sakaviaservice | 2 | 2026-05-15 |
| AZG3821 | - | 2 | 2026-05-24 |
| AZG273 | Sakaviaservice | 2 | 2026-04-17 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | AZG632 | SIN → GYD | May 30, 06:55 UTC | May 30, 11:45 UTC | 4h 50m |
| 2026-05-29 | AZG631 | - | May 29, 07:55 UTC | May 30, 02:55 UTC | 19h 0m |
| 2026-05-29 | AZG202 | AMS → GYD | May 29, 06:20 UTC | May 30, 02:55 UTC | 20h 35m |
| 2026-05-28 | AZG201 | - | May 28, 01:05 UTC | May 28, 17:50 UTC | 16h 45m |
| 2026-05-27 | AZG128 | GYD → ICN | May 27, 21:20 UTC | May 27, 21:45 UTC | 25m |
| 2026-05-27 | AZG128 | GYD → ICN | May 27, 20:20 UTC | May 27, 20:35 UTC | 15m |
| 2026-05-27 | AZG238 | HHN → GYD | May 27, 06:55 UTC | May 27, 10:40 UTC | 3h 45m |
| 2026-05-27 | AZG237 | GYD → HHN | May 27, 02:09 UTC | May 27, 02:29 UTC | 20m |
| 2026-05-26 | AZG237 | GYD → HHN | May 26, 22:20 UTC | May 26, 23:35 UTC | 1h 15m |
| 2026-05-26 | AZG148 | HKG → GYD | May 26, 09:55 UTC | May 26, 10:10 UTC | 15m |
| 2026-05-26 | AZG147 | - | May 26, 06:25 UTC | May 26, 06:59 UTC | 35m |
| 2026-05-25 | AZG5132 | - | May 25, 14:05 UTC | May 26, 03:05 UTC | 12h 59m |
| 2026-05-24 | AZG3821 | - | May 24, 16:15 UTC | May 25, 09:25 UTC | 17h 10m |
| 2026-05-24 | AZG904 | NRT → GYD | May 24, 12:05 UTC | May 24, 13:55 UTC | 1h 50m |
| 2026-05-23 | AZG8592 | - | May 23, 14:10 UTC | May 24, 09:35 UTC | 19h 25m |
| 2026-05-23 | AZG8592 | - | May 23, 09:50 UTC | May 24, 09:35 UTC | 23h 45m |
| 2026-05-23 | AZG8592 | - | May 23, 09:25 UTC | May 24, 07:45 UTC | 22h 20m |
| 2026-05-22 | AZG631 | - | May 22, 21:20 UTC | May 23, 02:55 UTC | 5h 35m |
| 2026-05-21 | AZG204 | AMS → GYD | May 21, 11:15 UTC | May 21, 15:30 UTC | 4h 15m |
| 2026-05-21 | AZG203 | BRU → GYD | May 21, 01:55 UTC | May 21, 06:20 UTC | 4h 25m |
| 2026-05-20 | AZG203 | BRU → GYD | May 20, 07:50 UTC | May 21, 06:20 UTC | 22h 30m |
| 2026-05-20 | AZG203 | BRU → GYD | May 20, 06:40 UTC | May 21, 05:45 UTC | 23h 5m |
| 2026-05-20 | AZG148 | HKG → GYD | May 20, 04:00 UTC | May 20, 04:20 UTC | 20m |
| 2026-05-20 | AZG147 | - | May 20, 00:50 UTC | May 20, 01:25 UTC | 35m |
| 2026-05-19 | AZG1148 | HKG → HKG | May 19, 03:00 UTC | May 19, 05:25 UTC | 2h 25m |
| 2026-05-18 | AZG1148 | HKG → HKG | May 18, 23:55 UTC | May 19, 00:15 UTC | 20m |
| 2026-05-18 | AZG624 | - | May 18, 17:40 UTC | May 18, 21:00 UTC | 3h 19m |
| 2026-05-18 | AZG624 | - | May 18, 15:55 UTC | May 18, 16:05 UTC | 10m |
| 2026-05-17 | AZG625 | HKG → HKG | May 17, 17:55 UTC | May 17, 18:10 UTC | 15m |
| 2026-05-17 | AZG922 | HKG → DWC | May 17, 14:30 UTC | May 17, 15:01 UTC | 30m |
| 2026-05-16 | AZG1572 | HKG → HKG | May 16, 20:50 UTC | May 16, 21:10 UTC | 20m |
| 2026-05-16 | AZG1571 | AVV → HKG | May 16, 16:55 UTC | May 16, 17:20 UTC | 25m |
| 2026-05-16 | AZG1571 | AVV → HKG | May 16, 01:20 UTC | May 16, 15:01 UTC | 13h 41m |
| 2026-05-15 | AZG786 | ORD → GYD | May 15, 14:20 UTC | May 15, 22:15 UTC | 7h 54m |
| 2026-05-15 | AZG4871 | GYD → ORD | May 15, 01:15 UTC | May 15, 09:40 UTC | 8h 25m |
| 2026-05-14 | AZG4871 | GYD → ORD | May 14, 18:45 UTC | May 14, 22:45 UTC | 4h 0m |
| 2026-05-13 | AZG923 | HKG → GYD | May 13, 06:05 UTC | May 13, 06:20 UTC | 15m |
| 2026-05-13 | AZG922 | HKG → DWC | May 13, 02:25 UTC | May 13, 02:55 UTC | 30m |
| 2026-05-12 | AZG148 | HKG → GYD | May 12, 02:45 UTC | May 12, 02:55 UTC | 10m |
| 2026-05-10 | AZG625 | HKG → HKG | May 10, 22:05 UTC | May 10, 22:30 UTC | 25m |
| 2026-05-10 | AZG624 | - | May 10, 19:09 UTC | May 10, 19:35 UTC | 25m |
| 2026-05-10 | AZG624 | - | May 10, 08:35 UTC | May 10, 17:25 UTC | 8h 50m |
| 2026-05-09 | AZG148 | HKG → GYD | May 9, 13:30 UTC | May 9, 13:50 UTC | 20m |
| 2026-05-09 | AZG571 | GYD → HKG | May 9, 08:20 UTC | May 9, 08:40 UTC | 20m |
| 2026-05-09 | AZG571 | GYD → HKG | May 9, 05:05 UTC | May 9, 06:10 UTC | 1h 5m |
| 2026-05-08 | AZG571 | GYD → HKG | May 8, 10:39 UTC | May 9, 06:10 UTC | 19h 30m |
| 2026-05-08 | AZG121 | - | May 8, 00:09 UTC | May 8, 00:29 UTC | 20m |
| 2026-05-05 | AZG041 | - | May 5, 23:30 UTC | May 5, 23:55 UTC | 25m |
| 2026-05-04 | AZG3822 | HHN → GYD | May 4, 09:35 UTC | May 4, 13:35 UTC | 4h 0m |
| 2026-05-03 | AZG3821 | - | May 3, 15:00 UTC | May 4, 05:35 UTC | 14h 35m |
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 VQ-BBM page for operator, model, and routing details .