sensors Mode-S transponder
43C700
ICAO 24-bit transponder address · allocated to United Kingdom
Currently assigned to ZZ343 · Airbus Voyager KC2 (A330-243MRTT)
- Hex
- 43C700
- Octal
- 20743400
- Decimal
- 4,441,856
- Country
- GB
- Tail
- ZZ343
- Type
- A332
- Flights observed
- 79
- Distinct callsigns
- 20
- Country
- GB
- Last broadcast
- Jul 23, 14:15 UTC
Last known position
Country allocation
The ICAO 24-bit address 43C700 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 |
|---|---|---|---|
| RRR9961 | - | 22 | 2026-07-22 |
| RRR9958 | - | 9 | 2026-07-07 |
| RRR9302 | - | 4 | 2026-06-20 |
| RRR2428 | - | 4 | 2026-04-17 |
| TARTN29 | - | 3 | 2026-04-14 |
| RRR2301 | Royal Air Force | 3 | 2026-05-17 |
| RRR2300 | Royal Air Force | 3 | 2026-06-27 |
| TARTN18 | - | 2 | 2026-04-13 |
| RRR9964 | - | 2 | 2026-07-05 |
| TARTN59 | - | 1 | 2026-05-29 |
| TARTN28 | - | 1 | 2026-05-19 |
| TARTN27 | - | 1 | 2026-05-19 |
| TARTN19 | - | 1 | 2026-05-18 |
| TARTN17 | - | 1 | 2026-05-18 |
| RRR9965 | - | 1 | 2026-05-15 |
| RRR9910 | - | 1 | 2026-06-11 |
| RRR9901 | - | 1 | 2026-05-13 |
| RRR9304 | - | 1 | 2026-04-24 |
| RRR861 | - | 1 | 2026-06-07 |
| RRR860 | - | 1 | 2026-06-07 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-23 | RRR2107 | - | Jul 23, 08:35 UTC | Jul 23, 14:15 UTC | 5h 40m |
| 2026-07-22 | RRR9961 | AKT → AKT | Jul 22, 18:20 UTC | Jul 23, 00:30 UTC | 6h 10m |
| 2026-07-22 | RRR9961 | - | Jul 22, 01:15 UTC | Jul 22, 01:35 UTC | 20m |
| 2026-07-21 | RRR9961 | - | Jul 21, 19:25 UTC | Jul 21, 20:00 UTC | 35m |
| 2026-07-20 | RRR9961 | AKT → AKT | Jul 20, 19:35 UTC | Jul 21, 01:40 UTC | 6h 4m |
| 2026-07-19 | RRR9961 | AKT → AKT | Jul 19, 18:45 UTC | Jul 19, 23:30 UTC | 4h 45m |
| 2026-07-19 | RRR9961 | - | Jul 19, 02:40 UTC | Jul 19, 03:00 UTC | 20m |
| 2026-07-18 | RRR9961 | - | Jul 18, 21:40 UTC | Jul 18, 22:10 UTC | 30m |
| 2026-07-17 | RRR9961 | AKT → AKT | Jul 17, 18:29 UTC | Jul 18, 01:30 UTC | 7h 0m |
| 2026-07-16 | RRR9961 | AKT → AKT | Jul 16, 16:30 UTC | Jul 16, 23:29 UTC | 7h 0m |
| 2026-07-15 | RRR9961 | AKT → AKT | Jul 15, 16:35 UTC | Jul 15, 23:30 UTC | 6h 55m |
| 2026-07-14 | RRR9961 | AKT → AKT | Jul 14, 16:35 UTC | Jul 14, 19:40 UTC | 3h 5m |
| 2026-07-13 | RRR9961 | AKT → AKT | Jul 13, 16:25 UTC | Jul 13, 22:45 UTC | 6h 20m |
| 2026-07-12 | RRR9961 | AKT → AKT | Jul 12, 16:25 UTC | Jul 12, 23:25 UTC | 7h 0m |
| 2026-07-10 | RRR9961 | AKT → AKT | Jul 10, 16:25 UTC | Jul 10, 22:25 UTC | 6h 1m |
| 2026-07-09 | RRR9961 | AKT → AKT | Jul 9, 20:20 UTC | Jul 10, 01:35 UTC | 5h 15m |
| 2026-07-08 | RRR9961 | AKT → AKT | Jul 8, 16:30 UTC | Jul 8, 22:30 UTC | 6h 0m |
| 2026-07-07 | RRR9958 | AKT → AKT | Jul 7, 08:30 UTC | Jul 7, 14:30 UTC | 6h 0m |
| 2026-07-06 | RRR9961 | AKT → AKT | Jul 6, 19:20 UTC | Jul 7, 01:30 UTC | 6h 10m |
| 2026-07-06 | RRR9958 | AKT → AKT | Jul 6, 08:25 UTC | Jul 6, 10:45 UTC | 2h 20m |
| 2026-07-05 | RRR9964 | AKT → AKT | Jul 5, 10:50 UTC | Jul 5, 13:30 UTC | 2h 40m |
| 2026-07-03 | RRR9958 | AKT → AKT | Jul 3, 08:35 UTC | Jul 3, 14:35 UTC | 6h 0m |
| 2026-07-01 | RRR9961 | - | Jul 1, 19:55 UTC | Jul 1, 20:30 UTC | 35m |
| 2026-07-01 | RRR9958 | AKT → AKT | Jul 1, 09:30 UTC | Jul 1, 10:50 UTC | 1h 20m |
| 2026-06-30 | RRR9958 | AKT → AKT | Jun 30, 08:25 UTC | Jun 30, 14:25 UTC | 6h 0m |
| 2026-06-29 | RRR9961 | AKT → AKT | Jun 29, 19:24 UTC | Jun 30, 01:25 UTC | 6h 0m |
| 2026-06-29 | RRR9958 | - | Jun 29, 08:29 UTC | Jun 29, 09:05 UTC | 35m |
| 2026-06-28 | RRR9958 | AKT → AKT | Jun 28, 19:25 UTC | Jun 29, 01:34 UTC | 6h 10m |
| 2026-06-27 | RRR2300 | BZZ → AKT | Jun 27, 12:25 UTC | Jun 27, 17:04 UTC | 4h 40m |
| 2026-06-20 | RRR9302 | - | Jun 20, 14:05 UTC | Jun 20, 20:05 UTC | 6h 0m |
| 2026-06-19 | RRR9302 | - | Jun 19, 15:04 UTC | Jun 19, 17:14 UTC | 2h 10m |
| 2026-06-16 | RRR9302 | - | Jun 16, 16:50 UTC | Jun 16, 19:05 UTC | 2h 15m |
| 2026-06-15 | RRR9302 | - | Jun 15, 09:15 UTC | Jun 15, 10:09 UTC | 55m |
| 2026-06-11 | RRR9910 | - | Jun 11, 08:30 UTC | Jun 11, 17:05 UTC | 8h 35m |
| 2026-06-10 | RRR2303 | AKT → BZZ | Jun 10, 10:05 UTC | Jun 10, 15:15 UTC | 5h 10m |
| 2026-06-09 | RRR2302 | BZZ → AKT | Jun 9, 06:55 UTC | Jun 9, 11:30 UTC | 4h 35m |
| 2026-06-08 | RRR2209 | RZE → BZZ | Jun 8, 15:45 UTC | Jun 8, 18:00 UTC | 2h 15m |
| 2026-06-08 | RRR2208 | - | Jun 8, 11:50 UTC | Jun 8, 14:00 UTC | 2h 10m |
| 2026-06-07 | RRR861 | - | Jun 7, 15:25 UTC | Jun 7, 16:20 UTC | 55m |
| 2026-06-07 | RRR860 | - | Jun 7, 12:55 UTC | Jun 7, 13:50 UTC | 55m |
| 2026-06-03 | RRR2289 | TMP → BZZ | Jun 3, 16:15 UTC | Jun 3, 19:10 UTC | 2h 55m |
| 2026-06-03 | RRR2288 | - | Jun 3, 09:35 UTC | Jun 3, 12:25 UTC | 2h 50m |
| 2026-05-31 | RRR2171 | - | May 31, 14:25 UTC | May 31, 21:35 UTC | 7h 10m |
| 2026-05-30 | RRR2170 | - | May 30, 10:10 UTC | May 30, 18:35 UTC | 8h 25m |
| 2026-05-29 | TARTN59 | - | May 29, 09:05 UTC | May 29, 12:20 UTC | 3h 15m |
| 2026-05-24 | RRR2887 | HAJ → BZZ | May 24, 12:15 UTC | May 24, 13:40 UTC | 1h 25m |
| 2026-05-24 | RRR2886 | BZZ → HAJ | May 24, 09:30 UTC | May 24, 10:55 UTC | 1h 25m |
| 2026-05-19 | TARTN27 | - | May 19, 14:20 UTC | May 19, 17:00 UTC | 2h 40m |
| 2026-05-19 | TARTN28 | - | May 19, 07:50 UTC | May 19, 11:50 UTC | 4h 0m |
| 2026-05-18 | TARTN17 | - | May 18, 13:50 UTC | May 18, 16:10 UTC | 2h 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 ZZ343 page for operator, model, and routing details .