sensors Mode-S transponder
424509
ICAO 24-bit transponder address · allocated to United Kingdom
Currently assigned to VQ-BXF · DASSAULT Falcon 8X
- Hex
- 424509
- Octal
- 20442411
- Decimal
- 4,343,049
- Country
- GB
- Tail
- VQ-BXF
- Type
- FA8X
- Flights observed
- 55
- Distinct callsigns
- 1
- Country
- GB
- Last broadcast
- 11d ago
Last known position
Country allocation
The ICAO 24-bit address 424509 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 |
|---|---|---|---|
| PEX28F | - | 55 | 2026-07-06 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-06 | PEX28F | RTM → KJK | Jul 6, 07:15 UTC | Jul 6, 07:40 UTC | 25m |
| 2026-07-02 | PEX28F | - | Jul 2, 16:35 UTC | Jul 2, 17:20 UTC | 45m |
| 2026-07-02 | PEX28F | - | Jul 2, 14:50 UTC | Jul 2, 15:30 UTC | 40m |
| 2026-06-28 | PEX28F | ABZ → RTM | Jun 28, 18:19 UTC | Jun 28, 19:29 UTC | 1h 10m |
| 2026-06-28 | PEX28F | RTM → ABZ | Jun 28, 16:25 UTC | Jun 28, 17:34 UTC | 1h 10m |
| 2026-06-24 | PEX28F | - | Jun 24, 17:05 UTC | Jun 24, 17:50 UTC | 45m |
| 2026-06-24 | PEX28F | - | Jun 24, 14:00 UTC | Jun 24, 15:49 UTC | 1h 50m |
| 2026-06-23 | PEX28F | - | Jun 23, 11:24 UTC | Jun 23, 11:59 UTC | 35m |
| 2026-06-22 | PEX28F | - | Jun 22, 06:29 UTC | Jun 22, 07:19 UTC | 50m |
| 2026-06-21 | PEX28F | - | Jun 21, 12:24 UTC | Jun 21, 13:20 UTC | 55m |
| 2026-06-21 | PEX28F | RTM → LTN | Jun 21, 10:14 UTC | Jun 21, 11:05 UTC | 50m |
| 2026-06-18 | PEX28F | - | Jun 18, 11:15 UTC | Jun 18, 11:55 UTC | 40m |
| 2026-06-17 | PEX28F | - | Jun 17, 14:05 UTC | Jun 17, 21:10 UTC | 7h 5m |
| 2026-06-15 | PEX28F | - | Jun 15, 08:20 UTC | Jun 15, 15:30 UTC | 7h 10m |
| 2026-06-15 | PEX28F | RTM → LTN | Jun 15, 05:40 UTC | Jun 15, 06:30 UTC | 50m |
| 2026-06-11 | PEX28F | - | Jun 11, 17:15 UTC | Jun 11, 17:55 UTC | 40m |
| 2026-06-11 | PEX28F | - | Jun 11, 07:55 UTC | Jun 11, 16:40 UTC | 8h 45m |
| 2026-06-08 | PEX28F | - | Jun 8, 07:05 UTC | Jun 8, 15:20 UTC | 8h 15m |
| 2026-06-07 | PEX28F | RTM → LTN | Jun 7, 16:35 UTC | Jun 7, 17:20 UTC | 45m |
| 2026-06-07 | PEX28F | - | Jun 7, 11:40 UTC | Jun 7, 12:20 UTC | 40m |
| 2026-06-07 | PEX28F | - | Jun 7, 08:40 UTC | Jun 7, 10:35 UTC | 1h 55m |
| 2026-06-07 | PEX28F | - | Jun 7, 06:50 UTC | Jun 7, 07:20 UTC | 30m |
| 2026-06-05 | PEX28F | - | Jun 5, 11:10 UTC | Jun 5, 11:40 UTC | 30m |
| 2026-06-05 | PEX28F | - | Jun 5, 08:20 UTC | Jun 5, 10:05 UTC | 1h 45m |
| 2026-06-04 | PEX28F | RTM → LTN | Jun 4, 16:25 UTC | Jun 4, 17:10 UTC | 45m |
| 2026-06-02 | PEX28F | FAB → RTM | Jun 2, 14:15 UTC | Jun 2, 15:05 UTC | 50m |
| 2026-06-02 | PEX28F | - | Jun 2, 08:10 UTC | Jun 2, 13:40 UTC | 5h 30m |
| 2026-05-31 | PEX28F | - | May 31, 21:10 UTC | Jun 1, 00:05 UTC | 2h 55m |
| 2026-05-31 | PEX28F | RTM → SEN | May 31, 19:05 UTC | May 31, 19:40 UTC | 35m |
| 2026-05-22 | PEX28F | - | May 22, 15:40 UTC | May 22, 16:30 UTC | 50m |
| 2026-05-22 | PEX28F | - | May 22, 13:10 UTC | May 22, 14:30 UTC | 1h 20m |
| 2026-05-19 | PEX28F | - | May 19, 14:50 UTC | May 19, 16:05 UTC | 1h 15m |
| 2026-05-19 | PEX28F | RTM → FAB | May 19, 13:30 UTC | May 19, 14:20 UTC | 50m |
| 2026-05-18 | PEX28F | - | May 18, 13:10 UTC | May 18, 13:50 UTC | 40m |
| 2026-05-18 | PEX28F | - | May 18, 10:30 UTC | May 18, 12:00 UTC | 1h 30m |
| 2026-05-17 | PEX28F | - | May 17, 14:40 UTC | May 17, 16:10 UTC | 1h 30m |
| 2026-05-17 | PEX28F | RTM → LCY | May 17, 13:10 UTC | May 17, 13:45 UTC | 35m |
| 2026-05-09 | PEX28F | - | May 9, 12:00 UTC | May 9, 12:45 UTC | 45m |
| 2026-05-09 | PEX28F | - | May 9, 00:35 UTC | May 9, 11:20 UTC | 10h 45m |
| 2026-05-05 | PEX28F | - | May 5, 17:05 UTC | May 6, 03:50 UTC | 10h 45m |
| 2026-05-04 | PEX28F | RTM → FAB | May 4, 16:05 UTC | May 4, 16:50 UTC | 45m |
| 2026-04-28 | PEX28F | LCY → RTM | Apr 28, 16:35 UTC | Apr 28, 17:15 UTC | 40m |
| 2026-04-28 | PEX28F | - | Apr 28, 14:15 UTC | Apr 28, 15:20 UTC | 1h 5m |
| 2026-04-27 | PEX28F | - | Apr 27, 07:30 UTC | Apr 27, 08:45 UTC | 1h 15m |
| 2026-04-27 | PEX28F | RTM → FAB | Apr 27, 05:25 UTC | Apr 27, 06:20 UTC | 55m |
| 2026-04-22 | PEX28F | - | Apr 22, 16:40 UTC | Apr 22, 17:20 UTC | 40m |
| 2026-04-20 | PEX28F | RTM → LCY | Apr 20, 17:05 UTC | Apr 20, 17:50 UTC | 45m |
| 2026-04-17 | PEX28F | LCY → RTM | Apr 17, 16:20 UTC | Apr 17, 17:00 UTC | 40m |
| 2026-04-17 | PEX28F | - | Apr 17, 13:20 UTC | Apr 17, 15:15 UTC | 1h 54m |
| 2026-04-17 | PEX28F | - | Apr 17, 07:20 UTC | Apr 17, 09:10 UTC | 1h 50m |
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-BXF page for operator, model, and routing details .