sensors Mode-S transponder
43A8F4
ICAO 24-bit transponder address · allocated to United Kingdom
- Hex
- 43A8F4
- Octal
- 20724364
- Decimal
- 4,434,164
- Country
- GB
- Flights observed
- 34
- Distinct callsigns
- 20
- Country
- GB
- Last broadcast
- 5h ago
Last known position
Country allocation
The ICAO 24-bit address 43A8F4 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 |
|---|---|---|---|
| TKJ8JC | Tarkim Havacilik | 3 | 2026-05-27 |
| TKJ4DR | Tarkim Havacilik | 2 | 2026-05-08 |
| TKJ9ZE | Tarkim Havacilik | 1 | 2026-05-05 |
| TKJ9NC | - | 1 | 2026-04-17 |
| TKJ9CL | Tarkim Havacilik | 1 | 2026-06-03 |
| TKJ8UT | Tarkim Havacilik | 1 | 2026-05-03 |
| TKJ8PU | Tarkim Havacilik | 1 | 2026-05-18 |
| TKJ8FD | Tarkim Havacilik | 1 | 2026-05-24 |
| TKJ8CQ | Tarkim Havacilik | 1 | 2026-05-31 |
| TKJ8AH | - | 1 | 2026-04-19 |
| TKJ7XM | - | 1 | 2026-06-01 |
| TKJ7UN | Tarkim Havacilik | 1 | 2026-05-05 |
| TKJ7RA | - | 1 | 2026-06-03 |
| TKJ7EZ | - | 1 | 2026-04-17 |
| TKJ6YR | - | 1 | 2026-05-07 |
| TKJ6YK | Tarkim Havacilik | 1 | 2026-06-03 |
| TKJ5NH | Tarkim Havacilik | 1 | 2026-05-28 |
| TKJ57D | Tarkim Havacilik | 1 | 2026-05-28 |
| TKJ4LV | - | 1 | 2026-05-10 |
| TKJ4CS | Tarkim Havacilik | 1 | 2026-05-30 |
Recent flights last 34
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-03 | TKJ9CL | SAW → STR | Jun 3, 17:15 UTC | Jun 3, 17:40 UTC | 25m |
| 2026-06-03 | TKJ7RA | - | Jun 3, 12:40 UTC | Jun 3, 13:35 UTC | 55m |
| 2026-06-03 | TKJ6YK | DUS → SAW | Jun 3, 07:50 UTC | Jun 3, 08:25 UTC | 35m |
| 2026-06-01 | TKJ7XM | - | Jun 1, 09:10 UTC | Jun 1, 09:40 UTC | 30m |
| 2026-05-31 | TKJ8CQ | STR → SAW | May 31, 19:20 UTC | May 31, 19:40 UTC | 20m |
| 2026-05-31 | TKJ2FM | - | May 31, 00:45 UTC | May 31, 13:25 UTC | 12h 40m |
| 2026-05-30 | TKJ4CS | SAW → ARN | May 30, 22:35 UTC | May 30, 23:20 UTC | 45m |
| 2026-05-28 | TKJ5NH | AYT → SAW | May 28, 15:30 UTC | May 28, 16:15 UTC | 45m |
| 2026-05-28 | TKJ57D | SAW → AYT | May 28, 13:15 UTC | May 28, 14:05 UTC | 50m |
| 2026-05-28 | TKJ12M | ADB → SAW | May 28, 11:05 UTC | May 28, 11:55 UTC | 50m |
| 2026-05-27 | TKJ8JC | YEI → DIY | May 27, 14:10 UTC | May 27, 14:30 UTC | 20m |
| 2026-05-27 | TKJ8JC | YEI → DIY | May 27, 13:15 UTC | May 27, 13:40 UTC | 25m |
| 2026-05-24 | TKJ8FD | SAW → SJJ | May 24, 14:15 UTC | May 24, 16:55 UTC | 2h 40m |
| 2026-05-21 | TKJ8JC | YEI → DIY | May 21, 14:05 UTC | May 21, 14:25 UTC | 20m |
| 2026-05-18 | TKJ8PU | BJV → SAW | May 18, 14:25 UTC | May 18, 15:05 UTC | 40m |
| 2026-05-18 | TKJ2DZ | SAW → BEG | May 18, 02:55 UTC | May 18, 03:25 UTC | 30m |
| 2026-05-10 | TKJ4LV | - | May 10, 10:05 UTC | May 10, 10:24 UTC | 20m |
| 2026-05-10 | TKJ29V | - | May 10, 08:25 UTC | May 10, 08:45 UTC | 20m |
| 2026-05-10 | TKJ1VY | - | May 10, 06:25 UTC | May 10, 06:40 UTC | 15m |
| 2026-05-10 | TKJ35V | - | May 10, 04:45 UTC | May 10, 05:14 UTC | 30m |
| 2026-05-08 | TKJ4DR | ESB → ERZ | May 8, 11:05 UTC | May 9, 05:30 UTC | 18h 25m |
| 2026-05-08 | TKJ4DR | ESB → ERZ | May 8, 10:44 UTC | May 9, 05:30 UTC | 18h 45m |
| 2026-05-07 | TKJ6YR | - | May 7, 11:25 UTC | May 7, 13:05 UTC | 1h 40m |
| 2026-05-05 | TKJ9ZE | MUC → SAW | May 5, 11:50 UTC | May 5, 13:45 UTC | 1h 55m |
| 2026-05-05 | TKJ7UN | SAW → MUC | May 5, 07:45 UTC | May 5, 10:05 UTC | 2h 20m |
| 2026-05-03 | TKJ8UT | ECN → ESB | May 3, 20:20 UTC | May 3, 21:20 UTC | 1h 0m |
| 2026-05-01 | TKJ3300 | - | May 1, 18:35 UTC | May 1, 19:35 UTC | 1h 0m |
| 2026-04-25 | TKJ214 | RUH → SAW | Apr 25, 10:35 UTC | Apr 26, 04:40 UTC | 18h 5m |
| 2026-04-23 | TKJ3NX | - | Apr 23, 05:05 UTC | Apr 23, 05:20 UTC | 15m |
| 2026-04-19 | TKJ8AH | - | Apr 19, 17:05 UTC | Apr 19, 18:45 UTC | 1h 40m |
| 2026-04-17 | TKJ23P | - | Apr 17, 18:45 UTC | Apr 17, 19:10 UTC | 25m |
| 2026-04-17 | TKJ7EZ | - | Apr 17, 10:45 UTC | Apr 17, 10:55 UTC | 10m |
| 2026-04-17 | TKJ9NC | - | Apr 17, 09:20 UTC | Apr 17, 09:35 UTC | 15m |
| 2026-04-17 | TKJ3ZK | - | Apr 17, 02:00 UTC | Apr 17, 02:10 UTC | 10m |
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.