sensors Mode-S transponder
400299
ICAO 24-bit transponder address · allocated to United Kingdom
Currently assigned to VP-COR · GULFSTREAM G700
- Hex
- 400299
- Octal
- 20001231
- Decimal
- 4,194,969
- Country
- GB
- Tail
- VP-COR
- Type
- GA7C
- Flights observed
- 50
- Distinct callsigns
- 1
- Country
- GB
- Last broadcast
- 3d ago
Last known position
Country allocation
The ICAO 24-bit address 400299 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 |
|---|---|---|---|
| VPCOR | - | 50 | 2026-07-20 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-20 | VPCOR | - | Jul 20, 19:55 UTC | Jul 20, 20:30 UTC | 35m |
| 2026-07-20 | VPCOR | - | Jul 20, 14:25 UTC | Jul 20, 18:20 UTC | 3h 55m |
| 2026-07-19 | VPCOR | - | Jul 19, 14:30 UTC | Jul 19, 14:45 UTC | 15m |
| 2026-07-12 | VPCOR | - | Jul 12, 10:40 UTC | Jul 12, 19:05 UTC | 8h 25m |
| 2026-07-10 | VPCOR | - | Jul 10, 13:05 UTC | Jul 10, 14:35 UTC | 1h 30m |
| 2026-07-10 | VPCOR | - | Jul 10, 07:15 UTC | Jul 10, 08:45 UTC | 1h 30m |
| 2026-07-05 | VPCOR | - | Jul 5, 16:55 UTC | Jul 5, 17:15 UTC | 20m |
| 2026-07-05 | VPCOR | - | Jul 5, 12:20 UTC | Jul 5, 14:15 UTC | 1h 55m |
| 2026-06-28 | VPCOR | - | Jun 28, 10:00 UTC | Jun 28, 10:19 UTC | 20m |
| 2026-06-28 | VPCOR | - | Jun 28, 01:25 UTC | Jun 28, 08:55 UTC | 7h 30m |
| 2026-06-20 | VPCOR | ANC → EWR | Jun 20, 17:34 UTC | Jun 20, 23:34 UTC | 6h 0m |
| 2026-06-19 | VPCOR | HKG → ANC | Jun 19, 04:10 UTC | Jun 19, 13:59 UTC | 9h 50m |
| 2026-06-15 | VPCOR | - | Jun 15, 03:10 UTC | Jun 15, 03:19 UTC | 10m |
| 2026-06-15 | VPCOR | - | Jun 15, 01:59 UTC | Jun 15, 02:30 UTC | 30m |
| 2026-06-13 | VPCOR | HKG → TSA | Jun 13, 02:15 UTC | Jun 13, 03:30 UTC | 1h 15m |
| 2026-06-13 | VPCOR | - | Jun 13, 00:45 UTC | Jun 13, 01:10 UTC | 25m |
| 2026-06-12 | VPCOR | - | Jun 12, 14:20 UTC | Jun 12, 18:01 UTC | 3h 40m |
| 2026-06-11 | VPCOR | - | Jun 11, 18:15 UTC | Jun 11, 19:10 UTC | 55m |
| 2026-06-11 | VPCOR | - | Jun 11, 12:30 UTC | Jun 11, 13:40 UTC | 1h 10m |
| 2026-06-11 | VPCOR | - | Jun 11, 07:15 UTC | Jun 11, 08:10 UTC | 55m |
| 2026-06-10 | VPCOR | - | Jun 10, 01:20 UTC | Jun 10, 08:25 UTC | 7h 5m |
| 2026-06-03 | VPCOR | - | Jun 3, 16:40 UTC | Jun 4, 01:20 UTC | 8h 40m |
| 2026-06-03 | VPCOR | - | Jun 3, 15:20 UTC | Jun 3, 15:30 UTC | 10m |
| 2026-05-31 | VPCOR | - | May 31, 18:10 UTC | May 31, 18:25 UTC | 15m |
| 2026-05-31 | VPCOR | - | May 31, 16:10 UTC | May 31, 16:55 UTC | 45m |
| 2026-05-31 | VPCOR | - | May 31, 14:40 UTC | May 31, 15:30 UTC | 50m |
| 2026-05-28 | VPCOR | BUD → PRG | May 28, 13:50 UTC | May 28, 14:40 UTC | 50m |
| 2026-05-28 | VPCOR | - | May 28, 09:10 UTC | May 28, 12:25 UTC | 3h 15m |
| 2026-05-27 | VPCOR | - | May 27, 02:04 UTC | May 27, 02:29 UTC | 25m |
| 2026-05-25 | VPCOR | - | May 25, 05:15 UTC | May 25, 06:00 UTC | 45m |
| 2026-05-23 | VPCOR | - | May 23, 02:50 UTC | May 23, 10:05 UTC | 7h 15m |
| 2026-05-22 | VPCOR | EWR → ANC | May 22, 19:35 UTC | May 23, 01:55 UTC | 6h 20m |
| 2026-05-14 | VPCOR | - | May 14, 15:01 UTC | May 14, 17:25 UTC | 2h 25m |
| 2026-05-14 | VPCOR | HKG → FAR | May 14, 01:25 UTC | May 14, 14:15 UTC | 12h 50m |
| 2026-05-11 | VPCOR | HND → HKG | May 11, 15:55 UTC | May 11, 20:00 UTC | 4h 6m |
| 2026-05-11 | VPCOR | - | May 11, 03:10 UTC | May 11, 14:50 UTC | 11h 40m |
| 2026-05-10 | VPCOR | - | May 10, 14:30 UTC | May 10, 16:14 UTC | 1h 45m |
| 2026-05-07 | VPCOR | - | May 7, 14:55 UTC | May 7, 19:30 UTC | 4h 35m |
| 2026-05-05 | VPCOR | - | May 5, 17:50 UTC | May 5, 18:20 UTC | 30m |
| 2026-05-05 | VPCOR | - | May 5, 07:10 UTC | May 5, 17:00 UTC | 9h 50m |
| 2026-05-04 | VPCOR | - | May 4, 07:45 UTC | May 4, 08:05 UTC | 20m |
| 2026-04-30 | VPCOR | - | Apr 30, 07:40 UTC | Apr 30, 10:20 UTC | 2h 40m |
| 2026-04-29 | VPCOR | - | Apr 29, 06:15 UTC | Apr 29, 06:29 UTC | 15m |
| 2026-04-27 | VPCOR | - | Apr 27, 08:00 UTC | Apr 27, 08:25 UTC | 25m |
| 2026-04-27 | VPCOR | - | Apr 27, 07:00 UTC | Apr 27, 07:30 UTC | 30m |
| 2026-04-25 | VPCOR | HKG → TSA | Apr 25, 02:40 UTC | Apr 25, 03:50 UTC | 1h 10m |
| 2026-04-24 | VPCOR | - | Apr 24, 10:25 UTC | Apr 24, 13:20 UTC | 2h 55m |
| 2026-04-23 | VPCOR | - | Apr 23, 06:15 UTC | Apr 23, 06:30 UTC | 15m |
| 2026-04-15 | VPCOR | - | Apr 15, 23:25 UTC | Apr 15, 23:40 UTC | 15m |
| 2026-04-12 | VPCOR | - | Apr 12, 17:15 UTC | Apr 12, 20:15 UTC | 3h 0m |
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 VP-COR page for operator, model, and routing details .