sensors Mode-S transponder
4056A2
ICAO 24-bit transponder address · allocated to United Kingdom
Currently assigned to G-RAJV · BOMBARDIER BD-700 Global 6000/6500
- Hex
- 4056A2
- Octal
- 20053242
- Decimal
- 4,216,482
- Country
- GB
- Tail
- G-RAJV
- Type
- GLEX
- Flights observed
- 66
- Distinct callsigns
- 3
- Country
- GB
- Last broadcast
- 13h ago
Last known position
Country allocation
The ICAO 24-bit address 4056A2 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 3 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | VCG1JV | - | Jul 17, 13:10 UTC | Jul 17, 13:29 UTC | 20m |
| 2026-07-16 | VCG2JV | - | Jul 16, 17:40 UTC | Jul 17, 00:50 UTC | 7h 10m |
| 2026-07-16 | VCG1JV | - | Jul 16, 14:05 UTC | Jul 16, 14:35 UTC | 30m |
| 2026-07-15 | VCG2JV | - | Jul 15, 23:25 UTC | Jul 16, 00:20 UTC | 55m |
| 2026-07-15 | VCG1JV | - | Jul 15, 15:55 UTC | Jul 15, 17:25 UTC | 1h 30m |
| 2026-07-14 | VCG2JV | - | Jul 14, 19:40 UTC | Jul 14, 20:30 UTC | 50m |
| 2026-07-14 | VCG1JV | AUS → DFW | Jul 14, 14:50 UTC | Jul 14, 15:40 UTC | 50m |
| 2026-07-13 | VCG2JV | DFW → AUS | Jul 13, 20:40 UTC | Jul 13, 21:25 UTC | 45m |
| 2026-07-13 | VCG1JV | SFO → DFW | Jul 13, 16:25 UTC | Jul 13, 19:35 UTC | 3h 10m |
| 2026-07-12 | VCG1JV | - | Jul 12, 14:45 UTC | Jul 12, 19:45 UTC | 5h 0m |
| 2026-07-09 | VCG1JV | - | Jul 9, 18:35 UTC | Jul 10, 03:15 UTC | 8h 40m |
| 2026-07-08 | VCG1JV | - | Jul 8, 12:20 UTC | Jul 8, 18:55 UTC | 6h 35m |
| 2026-07-06 | VCG1JV | - | Jul 6, 08:45 UTC | Jul 6, 16:05 UTC | 7h 20m |
| 2026-06-29 | VCG2JV | - | Jun 29, 16:35 UTC | Jun 29, 18:55 UTC | 2h 20m |
| 2026-06-29 | VCG1JV | - | Jun 29, 12:45 UTC | Jun 29, 12:55 UTC | 10m |
| 2026-06-29 | VCG1JV | - | Jun 29, 10:10 UTC | Jun 29, 12:24 UTC | 2h 15m |
| 2026-06-26 | VCG1JV | - | Jun 26, 02:44 UTC | Jun 26, 10:10 UTC | 7h 25m |
| 2026-06-25 | VCG1JV | - | Jun 25, 06:55 UTC | Jun 25, 14:39 UTC | 7h 45m |
| 2026-06-23 | VCG2JV | - | Jun 23, 19:50 UTC | Jun 23, 20:10 UTC | 20m |
| 2026-06-23 | VCG1JV | BOM → FAB | Jun 23, 09:24 UTC | Jun 23, 19:10 UTC | 9h 45m |
| 2026-06-22 | VCG2JV | - | Jun 22, 18:30 UTC | Jun 22, 19:40 UTC | 1h 10m |
| 2026-06-22 | VCG2JV | - | Jun 22, 17:04 UTC | Jun 22, 17:20 UTC | 15m |
| 2026-06-21 | VCG1JV | NCE → DXB | Jun 21, 22:10 UTC | Jun 22, 04:30 UTC | 6h 20m |
| 2026-06-18 | VCG3JV | - | Jun 18, 19:15 UTC | Jun 18, 20:55 UTC | 1h 40m |
| 2026-06-18 | VCG2JV | NCE → LTN | Jun 18, 14:05 UTC | Jun 18, 15:50 UTC | 1h 45m |
| 2026-06-18 | VCG1JV | - | Jun 18, 10:35 UTC | Jun 18, 12:05 UTC | 1h 30m |
| 2026-06-15 | VCG2JV | - | Jun 15, 21:14 UTC | Jun 15, 21:45 UTC | 30m |
| 2026-06-15 | VCG1JV | IAD → MAN | Jun 15, 14:40 UTC | Jun 15, 20:45 UTC | 6h 5m |
| 2026-06-14 | VCG1JV | MAN → IAD | Jun 14, 09:05 UTC | Jun 14, 16:00 UTC | 6h 55m |
| 2026-06-13 | VCG1JV | - | Jun 13, 14:40 UTC | Jun 13, 15:15 UTC | 35m |
| 2026-06-11 | VCG2JV | BCN → LTN | Jun 11, 12:15 UTC | Jun 11, 14:15 UTC | 2h 0m |
| 2026-06-11 | VCG1JV | - | Jun 11, 09:30 UTC | Jun 11, 11:00 UTC | 1h 30m |
| 2026-06-08 | VCG3JV | - | Jun 8, 18:25 UTC | Jun 8, 18:55 UTC | 30m |
| 2026-06-08 | VCG2JV | - | Jun 8, 15:55 UTC | Jun 8, 17:45 UTC | 1h 50m |
| 2026-06-08 | VCG1JV | - | Jun 8, 13:35 UTC | Jun 8, 15:04 UTC | 1h 30m |
| 2026-05-30 | VCG1JV | ATH → LTN | May 30, 14:30 UTC | May 30, 17:45 UTC | 3h 15m |
| 2026-05-29 | VCG1JV | - | May 29, 20:10 UTC | May 29, 23:10 UTC | 3h 0m |
| 2026-05-21 | VCG2JV | - | May 21, 17:25 UTC | May 21, 17:35 UTC | 10m |
| 2026-05-21 | VCG1JV | - | May 21, 12:00 UTC | May 21, 16:40 UTC | 4h 40m |
| 2026-05-18 | VCG1JV | - | May 18, 08:45 UTC | May 18, 12:30 UTC | 3h 45m |
| 2026-05-14 | VCG1JV | - | May 14, 18:00 UTC | May 14, 19:35 UTC | 1h 35m |
| 2026-05-13 | VCG1JV | - | May 13, 09:05 UTC | May 13, 12:20 UTC | 3h 15m |
| 2026-05-12 | VCG2JV | - | May 12, 13:51 UTC | May 12, 14:40 UTC | 50m |
| 2026-05-12 | VCG1JV | LTN → NHT | May 12, 12:50 UTC | May 12, 13:05 UTC | 15m |
| 2026-05-11 | VCG1JV | - | May 11, 19:15 UTC | May 11, 20:30 UTC | 1h 15m |
| 2026-05-10 | VCG2JV | - | May 10, 10:10 UTC | May 10, 11:50 UTC | 1h 40m |
| 2026-05-10 | VCG1JV | - | May 10, 06:40 UTC | May 10, 08:20 UTC | 1h 40m |
| 2026-05-07 | VCG1JV | - | May 7, 14:20 UTC | May 7, 19:15 UTC | 4h 55m |
| 2026-05-06 | VCG1JV | - | May 6, 18:55 UTC | May 7, 18:30 UTC | 23h 36m |
| 2026-05-06 | VCG1JV | - | May 6, 17:00 UTC | May 7, 16:30 UTC | 23h 30m |
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-RAJV page for operator, model, and routing details .