sensors Mode-S transponder
43F6C6
ICAO 24-bit transponder address · allocated to United Kingdom
Currently assigned to 2-REDY · SOCATA TBM-900/910/930/940
- Hex
- 43F6C6
- Octal
- 20773306
- Decimal
- 4,454,086
- Country
- GB
- Tail
- 2-REDY
- Type
- TBM9
- Flights observed
- 56
- Distinct callsigns
- 1
- Country
- GB
- Last broadcast
- 6d ago
Last known position
Country allocation
The ICAO 24-bit address 43F6C6 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 1 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| 2REDY | - | 56 | 2026-07-12 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-12 | 2REDY | SEN → GCI | Jul 12, 13:50 UTC | Jul 12, 14:50 UTC | 1h 0m |
| 2026-07-12 | 2REDY | - | Jul 12, 11:45 UTC | Jul 12, 12:40 UTC | 55m |
| 2026-07-08 | 2REDY | - | Jul 8, 14:45 UTC | Jul 8, 15:35 UTC | 50m |
| 2026-07-07 | 2REDY | - | Jul 7, 13:45 UTC | Jul 7, 14:10 UTC | 25m |
| 2026-07-07 | 2REDY | GCI → OXF | Jul 7, 06:35 UTC | Jul 7, 07:25 UTC | 50m |
| 2026-07-06 | 2REDY | BOH → GCI | Jul 6, 14:05 UTC | Jul 6, 14:35 UTC | 30m |
| 2026-07-06 | 2REDY | - | Jul 6, 12:25 UTC | Jul 6, 13:10 UTC | 45m |
| 2026-07-03 | 2REDY | GCI → SEN | Jul 3, 08:35 UTC | Jul 3, 09:30 UTC | 55m |
| 2026-06-30 | 2REDY | - | Jun 30, 15:45 UTC | Jun 30, 16:30 UTC | 45m |
| 2026-06-30 | 2REDY | GCI → OXF | Jun 30, 08:15 UTC | Jun 30, 09:05 UTC | 50m |
| 2026-06-22 | 2REDY | - | Jun 22, 18:04 UTC | Jun 22, 18:54 UTC | 50m |
| 2026-06-21 | 2REDY | - | Jun 21, 14:40 UTC | Jun 21, 15:19 UTC | 40m |
| 2026-06-21 | 2REDY | - | Jun 21, 13:20 UTC | Jun 21, 13:50 UTC | 30m |
| 2026-06-21 | 2REDY | - | Jun 21, 11:10 UTC | Jun 21, 11:30 UTC | 20m |
| 2026-06-21 | 2REDY | - | Jun 21, 08:40 UTC | Jun 21, 10:40 UTC | 2h 0m |
| 2026-06-21 | 2REDY | - | Jun 21, 07:14 UTC | Jun 21, 08:04 UTC | 50m |
| 2026-06-18 | 2REDY | - | Jun 18, 17:15 UTC | Jun 18, 19:10 UTC | 1h 55m |
| 2026-06-18 | 2REDY | OXF → SEN | Jun 18, 13:55 UTC | Jun 18, 14:20 UTC | 25m |
| 2026-06-17 | 2REDY | CER → OXF | Jun 17, 16:45 UTC | Jun 17, 17:40 UTC | 55m |
| 2026-06-17 | 2REDY | - | Jun 17, 15:20 UTC | Jun 17, 16:00 UTC | 40m |
| 2026-06-17 | 2REDY | - | Jun 17, 13:50 UTC | Jun 17, 14:40 UTC | 50m |
| 2026-06-17 | 2REDY | - | Jun 17, 11:45 UTC | Jun 17, 12:10 UTC | 25m |
| 2026-06-17 | 2REDY | BOH → GCI | Jun 17, 09:25 UTC | Jun 17, 10:00 UTC | 35m |
| 2026-06-16 | 2REDY | GCI → BOH | Jun 16, 09:00 UTC | Jun 16, 09:30 UTC | 30m |
| 2026-06-10 | 2REDY | - | Jun 10, 18:45 UTC | Jun 10, 19:40 UTC | 55m |
| 2026-06-09 | 2REDY | - | Jun 9, 08:10 UTC | Jun 9, 08:55 UTC | 45m |
| 2026-06-02 | 2REDY | - | Jun 2, 17:50 UTC | Jun 2, 18:45 UTC | 55m |
| 2026-06-02 | 2REDY | - | Jun 2, 08:45 UTC | Jun 2, 09:40 UTC | 55m |
| 2026-05-27 | 2REDY | - | May 27, 18:45 UTC | May 27, 19:40 UTC | 55m |
| 2026-05-27 | 2REDY | - | May 27, 10:30 UTC | May 27, 11:30 UTC | 1h 0m |
| 2026-05-26 | 2REDY | SEN → GCI | May 26, 14:55 UTC | May 26, 15:49 UTC | 55m |
| 2026-05-26 | 2REDY | - | May 26, 07:10 UTC | May 26, 08:04 UTC | 55m |
| 2026-05-21 | 2REDY | - | May 21, 09:45 UTC | May 21, 10:40 UTC | 55m |
| 2026-05-20 | 2REDY | - | May 20, 14:25 UTC | May 20, 17:20 UTC | 2h 55m |
| 2026-05-19 | 2REDY | - | May 19, 16:10 UTC | May 19, 18:40 UTC | 2h 30m |
| 2026-05-19 | 2REDY | - | May 19, 09:20 UTC | May 19, 10:20 UTC | 1h 0m |
| 2026-05-16 | 2REDY | - | May 16, 08:01 UTC | May 16, 08:55 UTC | 55m |
| 2026-05-14 | 2REDY | - | May 14, 08:30 UTC | May 14, 09:35 UTC | 1h 5m |
| 2026-05-12 | 2REDY | - | May 12, 15:10 UTC | May 12, 15:55 UTC | 45m |
| 2026-05-12 | 2REDY | - | May 12, 08:35 UTC | May 12, 09:25 UTC | 50m |
| 2026-05-08 | 2REDY | - | May 8, 13:40 UTC | May 8, 14:30 UTC | 50m |
| 2026-05-08 | 2REDY | SEN → OXF | May 8, 12:34 UTC | May 8, 13:05 UTC | 30m |
| 2026-05-07 | 2REDY | - | May 7, 14:30 UTC | May 7, 15:00 UTC | 30m |
| 2026-05-06 | 2REDY | - | May 6, 17:55 UTC | May 6, 18:25 UTC | 30m |
| 2026-05-06 | 2REDY | GCI → SEN | May 6, 10:50 UTC | May 6, 11:45 UTC | 55m |
| 2026-04-27 | 2REDY | - | Apr 27, 08:25 UTC | Apr 27, 10:45 UTC | 2h 20m |
| 2026-04-23 | 2REDY | GCI → CEQ | Apr 23, 11:05 UTC | Apr 23, 13:10 UTC | 2h 5m |
| 2026-04-22 | 2REDY | - | Apr 22, 16:10 UTC | Apr 22, 17:00 UTC | 50m |
| 2026-04-22 | 2REDY | - | Apr 22, 10:35 UTC | Apr 22, 11:05 UTC | 30m |
| 2026-04-22 | 2REDY | GCI → SEN | Apr 22, 08:55 UTC | Apr 22, 10:00 UTC | 1h 5m |
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 2-REDY page for operator, model, and routing details .