sensors Mode-S transponder

406832

ICAO 24-bit transponder address · allocated to United Kingdom

Currently assigned to G-VWAG · AIRBUS A-330-300

Hex
406832
Octal
20064062
Decimal
4,220,978
Country
GB
Tail
G-VWAG
Type
A333
No current signal · last broadcast 1d ago
Flights observed
82
Distinct callsigns
20
Country
GB
Last broadcast
1d ago

Last known position

Most recent position reported by Mode-S 406832.

Country allocation

The ICAO 24-bit address 406832 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 20 distinct

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-05-27 VIR6J MIA → LHR May 27, 22:20 UTCMay 28, 06:25 UTC8h 5m
2026-05-27 VIR5C LHR → MIA May 27, 11:10 UTCMay 27, 19:55 UTC8h 45m
2026-05-27 VIR130C TPA → LHR May 27, 00:14 UTCMay 27, 08:45 UTC8h 31m
2026-05-26 VIR129R LHR → TPA May 26, 12:24 UTCMay 26, 21:29 UTC9h 5m
2026-05-26 VIR130C TPA → LHR May 26, 00:14 UTCMay 26, 08:45 UTC8h 30m
2026-05-25 VIR129R LHR → TPA May 25, 12:20 UTCMay 25, 21:09 UTC8h 49m
2026-05-25 VIR808P LHR → MAN May 25, 08:45 UTCMay 25, 09:30 UTC45m
2026-05-24 VIR110 ATL → MAN May 24, 23:00 UTCMay 25, 06:15 UTC7h 15m
2026-05-24 VIR109V MAN → ATL May 24, 10:35 UTCMay 24, 19:00 UTC8h 25m
2026-05-24 VIR128K JFK → MAN May 24, 01:10 UTCMay 24, 07:15 UTC6h 5m
2026-05-23 VIR127C MAN → JFK May 23, 14:10 UTCMay 23, 21:15 UTC7h 5m
2026-05-23 VIR110 ATL → MAN May 23, 00:05 UTCMay 23, 07:15 UTC7h 9m
2026-05-22 VIR109V MAN → ATL May 22, 12:20 UTCMay 22, 21:00 UTC8h 40m
2026-05-22 VIR110 ATL → MAN May 22, 00:15 UTCMay 22, 07:25 UTC7h 10m
2026-05-21 VIR109V MAN → ATL May 21, 12:15 UTCMay 21, 20:40 UTC8h 25m
2026-05-21 VIR128K JFK → MAN May 21, 02:25 UTCMay 21, 08:25 UTC6h 0m
2026-05-20 VIR127C MAN → JFK May 20, 14:10 UTCMay 20, 21:15 UTC7h 5m
2026-05-20 VIR110 ATL → MAN May 20, 00:10 UTCMay 20, 07:40 UTC7h 31m
2026-05-19 VIR109V MAN → ATL May 19, 12:45 UTCMay 19, 21:00 UTC8h 15m
2026-05-19 VIR809P MAN → LHR May 19, 09:45 UTCMay 19, 10:20 UTC35m
2026-05-18 VIR6J MIA → LHR May 18, 22:30 UTCMay 19, 06:40 UTC8h 10m
2026-05-18 VIR5C LHR → MIA May 18, 10:25 UTCMay 18, 19:10 UTC8h 44m
2026-05-17 VIR92MC MCO → LHR May 17, 20:25 UTCMay 18, 04:11 UTC7h 46m
2026-05-17 VIR91U LHR → MCO May 17, 07:30 UTCMay 17, 16:25 UTC8h 55m
2026-05-16 VIR92MC MCO → LHR May 16, 20:00 UTCMay 17, 04:00 UTC8h 0m
2026-05-16 VIR91U LHR → MCO May 16, 07:31 UTCMay 16, 16:20 UTC8h 50m
2026-05-15 VIR92MC MCO → LHR May 15, 20:20 UTCMay 16, 03:50 UTC7h 30m
2026-05-15 VIR91U LHR → MCO May 15, 07:35 UTCMay 15, 16:20 UTC8h 44m
2026-05-14 VIR92MC MCO → LHR May 14, 20:05 UTCMay 15, 03:45 UTC7h 40m
2026-05-14 VIR91U LHR → MCO May 14, 07:25 UTCMay 14, 16:25 UTC9h 0m
2026-05-13 VIR92MC MCO → LHR May 13, 20:05 UTCMay 14, 04:05 UTC8h 0m
2026-05-13 VIR91U LHR → MCO May 13, 07:20 UTCMay 13, 16:25 UTC9h 5m
2026-05-12 VIR92MC MCO → LHR May 12, 19:55 UTCMay 13, 03:40 UTC7h 45m
2026-05-12 VIR91U LHR → MCO May 12, 07:15 UTCMay 12, 16:35 UTC9h 20m
2026-05-10 VIR92MC MCO → LHR May 10, 20:00 UTCMay 11, 04:00 UTC8h 0m
2026-05-10 VIR91U LHR → MCO May 10, 07:19 UTCMay 10, 16:10 UTC8h 50m
2026-05-09 VIR92MC MCO → LHR May 9, 20:05 UTCMay 10, 04:09 UTC8h 5m
2026-05-09 VIR91U LHR → MCO May 9, 07:20 UTCMay 9, 16:20 UTC9h 0m
2026-05-08 VIR92MC MCO → LHR May 8, 20:10 UTCMay 9, 04:00 UTC7h 50m
2026-05-08 VIR91U LHR → MCO May 8, 07:20 UTCMay 8, 16:35 UTC9h 15m
2026-05-07 VIR92MC MCO → LHR May 7, 20:05 UTCMay 8, 03:44 UTC7h 40m
2026-05-07 VIR91U LHR → MCO May 7, 07:15 UTCMay 7, 16:15 UTC9h 1m
2026-05-06 VIR92MC MCO → LHR May 6, 20:20 UTCMay 7, 04:20 UTC8h 0m
2026-05-06 VIR91U LHR → MCO May 6, 07:20 UTCMay 6, 16:15 UTC8h 55m
2026-05-05 VIR130A TPA → LHR May 5, 20:50 UTCMay 6, 05:05 UTC8h 15m
2026-05-04 VIR129R LHR → TPA May 4, 12:50 UTCMay 4, 21:35 UTC8h 46m
2026-05-04 VIR129R LHR → TPA May 4, 12:30 UTCMay 4, 12:45 UTC15m
2026-05-04 VIR808P LHR → MAN May 4, 08:50 UTCMay 4, 09:40 UTC50m
2026-05-03 VIR110 ATL → MAN May 3, 22:30 UTCMay 4, 05:50 UTC7h 20m
2026-05-03 VIR109V MAN → ATL May 3, 10:40 UTCMay 3, 19:00 UTC8h 20m

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-VWAG page for operator, model, and routing details .

Mode-S 406832 frequently asked

What is Mode-S code 406832?
406832 is an ICAO 24-bit transponder address. Allocated to United Kingdom. Assigned to G-VWAG.
Where is Mode-S 406832 registered?
Mode-S code 406832 is allocated to United Kingdom (GB). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 406832 broadcasting right now?
No active broadcast right now. Last signal was 1d ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 406832, octal 20064062, decimal 4,220,978.
What flights does 406832 operate?
Mode-S 406832 has broadcast 20 distinct callsigns, including VIR91U, VIR92MC, VIR5C, VIR127C, VIR110.