sensors Mode-S transponder
400A75
ICAO 24-bit transponder address · allocated to United Kingdom
Currently assigned to G-RAFK · BEECH 200 Super King Air
- Hex
- 400A75
- Octal
- 20005165
- Decimal
- 4,196,981
- Country
- GB
- Tail
- G-RAFK
- Type
- BE20
- Flights observed
- 62
- Distinct callsigns
- 1
- Country
- GB
- Last broadcast
- 1h ago
Current position
Country allocation
The ICAO 24-bit address 400A75 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 |
|---|---|---|---|
| REV1FK | - | 62 | 2026-07-14 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | REV1FK | - | Jul 14, 08:40 UTC | Jul 14, 09:15 UTC | 35m |
| 2026-07-14 | REV1FK | - | Jul 14, 08:00 UTC | Jul 14, 08:35 UTC | 35m |
| 2026-07-13 | REV1FK | EXT → BHX | Jul 13, 13:25 UTC | Jul 13, 14:20 UTC | 55m |
| 2026-07-08 | REV1FK | - | Jul 8, 12:15 UTC | Jul 8, 13:15 UTC | 1h 0m |
| 2026-07-06 | REV1FK | - | Jul 6, 12:00 UTC | Jul 6, 14:40 UTC | 2h 40m |
| 2026-07-05 | REV1FK | - | Jul 5, 14:35 UTC | Jul 5, 18:10 UTC | 3h 35m |
| 2026-06-24 | REV1FK | - | Jun 24, 13:44 UTC | Jun 24, 17:29 UTC | 3h 45m |
| 2026-06-24 | REV1FK | - | Jun 24, 08:30 UTC | Jun 24, 10:35 UTC | 2h 5m |
| 2026-06-23 | REV1FK | ORK → BHX | Jun 23, 12:55 UTC | Jun 23, 14:35 UTC | 1h 40m |
| 2026-06-23 | REV1FK | ORK → ORK | Jun 23, 07:40 UTC | Jun 23, 11:24 UTC | 3h 45m |
| 2026-06-22 | REV1FK | ORK → ORK | Jun 22, 13:39 UTC | Jun 22, 15:59 UTC | 2h 20m |
| 2026-06-22 | REV1FK | - | Jun 22, 08:19 UTC | Jun 22, 11:44 UTC | 3h 25m |
| 2026-06-21 | REV1FK | - | Jun 21, 12:55 UTC | Jun 21, 15:54 UTC | 3h 0m |
| 2026-06-21 | REV1FK | - | Jun 21, 07:09 UTC | Jun 21, 10:34 UTC | 3h 25m |
| 2026-06-20 | REV1FK | - | Jun 20, 15:14 UTC | Jun 20, 15:34 UTC | 20m |
| 2026-06-15 | REV1FK | - | Jun 15, 14:00 UTC | Jun 15, 14:20 UTC | 20m |
| 2026-06-13 | REV1FK | - | Jun 13, 13:55 UTC | Jun 13, 17:25 UTC | 3h 30m |
| 2026-06-10 | REV1FK | EMA → BHX | Jun 10, 18:30 UTC | Jun 10, 19:00 UTC | 30m |
| 2026-06-10 | REV1FK | EMA → EMA | Jun 10, 17:25 UTC | Jun 10, 17:35 UTC | 10m |
| 2026-06-10 | REV1FK | BHX → EMA | Jun 10, 14:35 UTC | Jun 10, 14:55 UTC | 20m |
| 2026-06-04 | REV1FK | - | Jun 4, 13:50 UTC | Jun 4, 14:50 UTC | 1h 0m |
| 2026-06-04 | REV1FK | - | Jun 4, 10:35 UTC | Jun 4, 11:25 UTC | 50m |
| 2026-05-30 | REV1FK | - | May 30, 13:45 UTC | May 30, 17:05 UTC | 3h 20m |
| 2026-05-30 | REV1FK | - | May 30, 08:10 UTC | May 30, 11:45 UTC | 3h 35m |
| 2026-05-29 | REV1FK | - | May 29, 14:10 UTC | May 29, 17:40 UTC | 3h 30m |
| 2026-05-28 | REV1FK | ORK → BHX | May 28, 19:15 UTC | May 28, 20:25 UTC | 1h 10m |
| 2026-05-28 | REV1FK | ORK → ORK | May 28, 17:35 UTC | May 28, 18:05 UTC | 30m |
| 2026-05-25 | REV1FK | ORK → ORK | May 25, 14:05 UTC | May 25, 14:40 UTC | 35m |
| 2026-05-25 | REV1FK | BHX → ORK | May 25, 08:00 UTC | May 25, 12:10 UTC | 4h 10m |
| 2026-05-24 | REV1FK | BHX → BHX | May 24, 13:20 UTC | May 24, 15:20 UTC | 2h 0m |
| 2026-05-24 | REV1FK | BHX → BHX | May 24, 07:50 UTC | May 24, 11:15 UTC | 3h 25m |
| 2026-05-23 | REV1FK | - | May 23, 12:20 UTC | May 23, 14:25 UTC | 2h 5m |
| 2026-05-23 | REV1FK | - | May 23, 07:40 UTC | May 23, 10:35 UTC | 2h 55m |
| 2026-05-22 | REV1FK | - | May 22, 14:40 UTC | May 22, 17:00 UTC | 2h 20m |
| 2026-05-22 | REV1FK | - | May 22, 09:25 UTC | May 22, 12:40 UTC | 3h 15m |
| 2026-05-12 | REV1FK | EMA → BHX | May 12, 13:05 UTC | May 12, 14:10 UTC | 1h 5m |
| 2026-05-12 | REV1FK | - | May 12, 06:10 UTC | May 12, 09:30 UTC | 3h 20m |
| 2026-05-09 | REV1FK | - | May 9, 12:10 UTC | May 9, 13:55 UTC | 1h 45m |
| 2026-05-09 | REV1FK | - | May 9, 07:00 UTC | May 9, 10:35 UTC | 3h 35m |
| 2026-05-04 | REV1FK | - | May 4, 11:05 UTC | May 4, 12:15 UTC | 1h 10m |
| 2026-05-01 | REV1FK | - | May 1, 11:10 UTC | May 1, 11:25 UTC | 15m |
| 2026-05-01 | REV1FK | - | May 1, 07:15 UTC | May 1, 10:30 UTC | 3h 15m |
| 2026-04-30 | REV1FK | - | Apr 30, 13:00 UTC | Apr 30, 16:10 UTC | 3h 10m |
| 2026-04-30 | REV1FK | - | Apr 30, 08:30 UTC | Apr 30, 11:35 UTC | 3h 5m |
| 2026-04-29 | REV1FK | - | Apr 29, 14:10 UTC | Apr 29, 16:30 UTC | 2h 20m |
| 2026-04-29 | REV1FK | - | Apr 29, 09:05 UTC | Apr 29, 11:45 UTC | 2h 40m |
| 2026-04-28 | REV1FK | EMA → BHX | Apr 28, 11:35 UTC | Apr 28, 12:05 UTC | 30m |
| 2026-04-27 | REV1FK | - | Apr 27, 13:30 UTC | Apr 27, 16:25 UTC | 2h 55m |
| 2026-04-27 | REV1FK | - | Apr 27, 08:30 UTC | Apr 27, 11:50 UTC | 3h 20m |
| 2026-04-26 | REV1FK | - | Apr 26, 14:10 UTC | Apr 26, 16:20 UTC | 2h 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.
Prefer a tail-number view? See the G-RAFK page for operator, model, and routing details .