sensors Mode-S transponder
4243C4
ICAO 24-bit transponder address · allocated to United Kingdom
Currently assigned to VQ-BVC · BOEING 747-8
- Hex
- 4243C4
- Octal
- 20441704
- Decimal
- 4,342,724
- Country
- GB
- Tail
- VQ-BVC
- Type
- B748
- Flights observed
- 87
- Distinct callsigns
- 20
- Country
- GB
- Last broadcast
- Jul 26, 13:45 UTC
Last known position
Country allocation
The ICAO 24-bit address 4243C4 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 |
|---|---|---|---|
| AZG903 | - | 7 | 2026-07-25 |
| AZG124 | - | 6 | 2026-07-26 |
| AZG904 | Sakaviaservice | 5 | 2026-07-26 |
| AZG128 | - | 5 | 2026-06-30 |
| AZG129 | Sakaviaservice | 4 | 2026-06-30 |
| AZG998 | - | 3 | 2026-07-04 |
| AZG997 | - | 3 | 2026-07-04 |
| AZG624 | - | 3 | 2026-07-20 |
| AZG5721 | Sakaviaservice | 3 | 2026-06-02 |
| AZG121 | - | 3 | 2026-06-19 |
| AZG783 | - | 2 | 2026-07-22 |
| AZG648 | - | 2 | 2026-07-13 |
| AZG647 | - | 2 | 2026-07-12 |
| AZG631 | - | 2 | 2026-07-24 |
| AZG5789 | Sakaviaservice | 2 | 2026-06-03 |
| AZG3824 | Sakaviaservice | 2 | 2026-07-24 |
| AZG3823 | Sakaviaservice | 2 | 2026-07-23 |
| AZG3321 | - | 2 | 2026-07-20 |
| AZG208 | - | 2 | 2026-06-28 |
| AZG207 | Sakaviaservice | 2 | 2026-06-28 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | AZG124 | - | Jul 26, 13:25 UTC | Jul 26, 13:45 UTC | 20m |
| 2026-07-26 | AZG904 | NRT → GYD | Jul 26, 07:55 UTC | Jul 26, 09:40 UTC | 1h 45m |
| 2026-07-25 | AZG903 | - | Jul 25, 11:20 UTC | Jul 26, 05:15 UTC | 17h 55m |
| 2026-07-25 | AZG903 | - | Jul 25, 10:00 UTC | Jul 26, 05:15 UTC | 19h 15m |
| 2026-07-25 | AZG903 | - | Jul 25, 07:10 UTC | Jul 26, 05:15 UTC | 22h 5m |
| 2026-07-24 | AZG631 | - | Jul 24, 21:30 UTC | Jul 25, 03:20 UTC | 5h 50m |
| 2026-07-24 | AZG3824 | HHN → GYD | Jul 24, 09:50 UTC | Jul 24, 13:30 UTC | 3h 40m |
| 2026-07-23 | AZG3823 | GYD → HHN | Jul 23, 23:20 UTC | Jul 24, 03:35 UTC | 4h 15m |
| 2026-07-23 | AZG786 | ORD → GYD | Jul 23, 08:25 UTC | Jul 23, 18:55 UTC | 10h 30m |
| 2026-07-22 | AZG783 | LUX → ORD | Jul 22, 18:40 UTC | Jul 23, 03:05 UTC | 8h 25m |
| 2026-07-22 | AZG783 | - | Jul 22, 12:45 UTC | Jul 22, 13:55 UTC | 1h 10m |
| 2026-07-22 | AZG3232 | HHN → HHN | Jul 22, 05:15 UTC | Jul 22, 05:25 UTC | 10m |
| 2026-07-21 | AZG3231 | JFK → HHN | Jul 21, 19:50 UTC | Jul 22, 00:10 UTC | 4h 20m |
| 2026-07-21 | AZG1404 | - | Jul 21, 13:45 UTC | Jul 21, 15:30 UTC | 1h 45m |
| 2026-07-20 | AZG1403 | STN → GYD | Jul 20, 21:25 UTC | Jul 21, 11:20 UTC | 13h 54m |
| 2026-07-20 | AZG624 | - | Jul 20, 17:45 UTC | Jul 20, 18:15 UTC | 30m |
| 2026-07-20 | AZG624 | - | Jul 20, 14:25 UTC | Jul 20, 16:05 UTC | 1h 40m |
| 2026-07-20 | AZG3321 | - | Jul 20, 07:05 UTC | Jul 20, 07:30 UTC | 25m |
| 2026-07-19 | - | - | Jul 19, 14:25 UTC | Jul 19, 18:20 UTC | 3h 55m |
| 2026-07-19 | AZG124 | - | Jul 19, 13:15 UTC | Jul 19, 13:40 UTC | 25m |
| 2026-07-19 | AZG904 | NRT → GYD | Jul 19, 08:15 UTC | Jul 19, 09:55 UTC | 1h 40m |
| 2026-07-18 | AZG903 | - | Jul 18, 10:40 UTC | Jul 19, 04:35 UTC | 17h 55m |
| 2026-07-18 | AZG903 | - | Jul 18, 07:40 UTC | Jul 19, 04:35 UTC | 20h 55m |
| 2026-07-17 | AZG631 | - | Jul 17, 21:39 UTC | Jul 18, 03:20 UTC | 5h 41m |
| 2026-07-13 | AZG648 | - | Jul 13, 08:55 UTC | Jul 13, 09:10 UTC | 15m |
| 2026-07-12 | AZG647 | - | Jul 12, 21:55 UTC | Jul 13, 06:15 UTC | 8h 20m |
| 2026-07-12 | - | - | Jul 12, 18:35 UTC | Jul 12, 18:45 UTC | 10m |
| 2026-07-12 | AZG5515 | - | Jul 12, 15:35 UTC | Jul 12, 16:15 UTC | 40m |
| 2026-07-10 | AZG3824 | HHN → GYD | Jul 10, 12:15 UTC | Jul 10, 15:40 UTC | 3h 25m |
| 2026-07-10 | AZG3823 | - | Jul 10, 03:45 UTC | Jul 10, 08:10 UTC | 4h 25m |
| 2026-07-05 | AZG217 | - | Jul 5, 07:05 UTC | Jul 5, 09:00 UTC | 1h 55m |
| 2026-07-05 | AZG216 | - | Jul 5, 00:50 UTC | Jul 5, 03:15 UTC | 2h 25m |
| 2026-07-04 | AZG998 | - | Jul 4, 15:50 UTC | Jul 4, 20:30 UTC | 4h 40m |
| 2026-07-04 | AZG997 | - | Jul 4, 05:15 UTC | Jul 4, 10:40 UTC | 5h 25m |
| 2026-06-30 | AZG129 | ICN → GYD | Jun 30, 13:55 UTC | Jun 30, 14:10 UTC | 15m |
| 2026-06-30 | AZG128 | - | Jun 30, 10:20 UTC | Jun 30, 10:50 UTC | 30m |
| 2026-06-30 | AZG128 | - | Jun 30, 09:15 UTC | Jun 30, 09:40 UTC | 25m |
| 2026-06-28 | AZG208 | - | Jun 28, 20:19 UTC | Jun 29, 00:20 UTC | 4h 0m |
| 2026-06-28 | AZG207 | GYD → AMS | Jun 28, 12:55 UTC | Jun 28, 17:25 UTC | 4h 30m |
| 2026-06-28 | AZG762 | LGG → GYD | Jun 28, 04:50 UTC | Jun 28, 08:44 UTC | 3h 55m |
| 2026-06-27 | AZG998 | - | Jun 27, 10:54 UTC | Jun 28, 00:00 UTC | 13h 5m |
| 2026-06-27 | AZG997 | - | Jun 27, 01:39 UTC | Jun 27, 06:35 UTC | 4h 55m |
| 2026-06-23 | AZG039 | GYD → PVG | Jun 23, 19:15 UTC | Jun 24, 07:59 UTC | 12h 45m |
| 2026-06-23 | AZG129 | ICN → GYD | Jun 23, 12:35 UTC | Jun 24, 07:59 UTC | 19h 25m |
| 2026-06-23 | AZG129 | ICN → GYD | Jun 23, 11:24 UTC | Jun 23, 11:40 UTC | 15m |
| 2026-06-23 | AZG128 | GYD → ICN | Jun 23, 07:35 UTC | Jun 23, 07:55 UTC | 20m |
| 2026-06-23 | AZG128 | GYD → ICN | Jun 23, 06:24 UTC | Jun 23, 06:49 UTC | 25m |
| 2026-06-21 | AZG124 | ICN → GYD | Jun 21, 13:09 UTC | Jun 21, 13:29 UTC | 20m |
| 2026-06-21 | AZG904 | NRT → GYD | Jun 21, 08:15 UTC | Jun 21, 10:19 UTC | 2h 5m |
| 2026-06-21 | AZG903 | - | Jun 21, 01:59 UTC | Jun 21, 04:44 UTC | 2h 45m |
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-BVC page for operator, model, and routing details .