sensors Mode-S transponder
4077D4
ICAO 24-bit transponder address · allocated to United Kingdom
Currently assigned to G-VRNB · AIRBUS A-350-1000
- Hex
- 4077D4
- Octal
- 20073724
- Decimal
- 4,224,980
- Country
- GB
- Tail
- G-VRNB
- Type
- A35K
- Flights observed
- 152
- Distinct callsigns
- 20
- Country
- GB
- Last broadcast
- 1d ago
Current position
Country allocation
The ICAO 24-bit address 4077D4 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
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| VIR104L | - | 14 | 2026-07-06 |
| VIR7B | - | 13 | 2026-06-30 |
| VIR103M | - | 13 | 2026-07-06 |
| VIR3N | - | 12 | 2026-07-12 |
| VIR4C | - | 11 | 2026-07-12 |
| VIR8Y | - | 10 | 2026-06-30 |
| VIR359 | Virgin Atlantic Airways | 10 | 2026-05-12 |
| VIR10H | - | 8 | 2026-07-05 |
| VIR45W | Virgin Atlantic Airways | 6 | 2026-05-14 |
| VIR153 | Virgin Atlantic Airways | 6 | 2026-05-28 |
| VIR154 | Virgin Atlantic Airways | 5 | 2026-05-29 |
| VIR117F | Virgin Atlantic Airways | 5 | 2026-04-20 |
| VIR303 | - | 4 | 2026-06-29 |
| VIR302 | - | 4 | 2026-06-29 |
| VIR20V | - | 4 | 2026-07-04 |
| VIR19Z | - | 4 | 2026-07-03 |
| VIR118 | Virgin Atlantic Airways | 4 | 2026-04-21 |
| VIR358 | Virgin Atlantic Airways | 3 | 2026-04-16 |
| VIR129R | Virgin Atlantic Airways | 3 | 2026-04-13 |
| VIR9J | - | 2 | 2026-07-07 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-12 | VIR4C | JFK → LHR | Jul 12, 22:45 UTC | Jul 13, 05:10 UTC | 6h 25m |
| 2026-07-12 | VIR3N | - | Jul 12, 13:35 UTC | Jul 12, 15:05 UTC | 1h 30m |
| 2026-07-12 | VIR3N | - | Jul 12, 08:25 UTC | Jul 12, 09:40 UTC | 1h 15m |
| 2026-07-11 | VIR4C | JFK → LHR | Jul 11, 23:55 UTC | Jul 12, 06:05 UTC | 6h 10m |
| 2026-07-11 | VIR3N | LHR → JFK | Jul 11, 07:45 UTC | Jul 11, 14:45 UTC | 7h 0m |
| 2026-07-10 | VIR4C | JFK → LHR | Jul 10, 23:05 UTC | Jul 11, 05:15 UTC | 6h 10m |
| 2026-07-10 | VIR3N | LHR → JFK | Jul 10, 07:50 UTC | Jul 10, 15:00 UTC | 7h 10m |
| 2026-07-09 | VIR4C | JFK → LHR | Jul 9, 22:35 UTC | Jul 10, 05:05 UTC | 6h 30m |
| 2026-07-09 | VIR3N | LHR → JFK | Jul 9, 07:50 UTC | Jul 9, 14:45 UTC | 6h 55m |
| 2026-07-08 | VIR4C | - | Jul 8, 22:40 UTC | Jul 9, 05:10 UTC | 6h 30m |
| 2026-07-08 | VIR3N | - | Jul 8, 07:40 UTC | Jul 8, 14:20 UTC | 6h 40m |
| 2026-07-07 | VIR4C | JFK → LHR | Jul 7, 22:30 UTC | Jul 8, 05:05 UTC | 6h 35m |
| 2026-07-07 | VIR9J | - | Jul 7, 10:50 UTC | Jul 7, 17:50 UTC | 7h 0m |
| 2026-07-06 | VIR104L | ATL → LHR | Jul 6, 22:30 UTC | Jul 7, 06:00 UTC | 7h 30m |
| 2026-07-06 | VIR103M | - | Jul 6, 11:00 UTC | Jul 6, 19:20 UTC | 8h 20m |
| 2026-07-05 | VIR10H | JFK → LHR | Jul 5, 23:15 UTC | Jul 6, 05:10 UTC | 5h 55m |
| 2026-07-05 | VIR3N | - | Jul 5, 07:45 UTC | Jul 5, 14:50 UTC | 7h 5m |
| 2026-07-04 | VIR20V | - | Jul 4, 01:35 UTC | Jul 4, 11:15 UTC | 9h 40m |
| 2026-07-03 | VIR19Z | - | Jul 3, 12:55 UTC | Jul 3, 23:15 UTC | 10h 20m |
| 2026-07-03 | VIR138M | JFK → LHR | Jul 3, 04:10 UTC | Jul 3, 10:15 UTC | 6h 5m |
| 2026-07-02 | VIR137Y | LHR → JFK | Jul 2, 17:55 UTC | Jul 3, 01:05 UTC | 7h 10m |
| 2026-07-02 | VIR20V | SFO → LHR | Jul 2, 01:40 UTC | Jul 2, 11:05 UTC | 9h 25m |
| 2026-07-01 | VIR19Z | - | Jul 1, 13:10 UTC | Jul 1, 23:10 UTC | 10h 0m |
| 2026-06-30 | VIR8Y | - | Jun 30, 23:00 UTC | Jul 1, 08:15 UTC | 9h 15m |
| 2026-06-30 | VIR7B | - | Jun 30, 09:20 UTC | Jun 30, 19:45 UTC | 10h 25m |
| 2026-06-29 | VIR303 | DEL → LHR | Jun 29, 20:59 UTC | Jun 30, 05:35 UTC | 8h 36m |
| 2026-06-29 | VIR302 | - | Jun 29, 10:04 UTC | Jun 29, 17:49 UTC | 7h 45m |
| 2026-06-28 | VIR303 | - | Jun 28, 21:14 UTC | Jun 29, 05:50 UTC | 8h 35m |
| 2026-06-28 | VIR302 | - | Jun 28, 10:15 UTC | Jun 28, 18:05 UTC | 7h 50m |
| 2026-06-27 | VIR853P | MLA → LHR | Jun 27, 12:25 UTC | Jun 27, 15:10 UTC | 2h 45m |
| 2026-06-02 | VIR852P | LHR → LHR | Jun 2, 14:10 UTC | Jun 2, 16:40 UTC | 2h 30m |
| 2026-06-02 | VIR116 | ATL → LHR | Jun 2, 03:45 UTC | Jun 2, 10:45 UTC | 7h 0m |
| 2026-06-01 | VIR862P | PBI → ATL | Jun 1, 21:40 UTC | Jun 1, 22:55 UTC | 1h 15m |
| 2026-06-01 | VIR697 | - | Jun 1, 10:25 UTC | Jun 1, 18:40 UTC | 8h 15m |
| 2026-06-01 | VIR861P | - | Jun 1, 07:00 UTC | Jun 1, 07:30 UTC | 30m |
| 2026-05-30 | VIR303 | DEL → LHR | May 30, 21:05 UTC | May 30, 22:10 UTC | 1h 5m |
| 2026-05-30 | VIR302 | LHR → DEL | May 30, 10:50 UTC | May 30, 18:25 UTC | 7h 35m |
| 2026-05-29 | VIR104L | ATL → LHR | May 29, 22:30 UTC | May 30, 05:50 UTC | 7h 20m |
| 2026-05-29 | VIR103M | LHR → ATL | May 29, 10:45 UTC | May 29, 18:45 UTC | 8h 1m |
| 2026-05-29 | VIR154 | JFK → LHR | May 29, 01:35 UTC | May 29, 08:00 UTC | 6h 25m |
| 2026-05-28 | VIR153 | LHR → JFK | May 28, 20:25 UTC | May 28, 22:00 UTC | 1h 35m |
| 2026-05-28 | VIR153 | LHR → JFK | May 28, 15:30 UTC | May 28, 16:45 UTC | 1h 15m |
| 2026-05-28 | VIR20V | SFO → LHR | May 28, 02:05 UTC | May 28, 12:10 UTC | 10h 5m |
| 2026-05-27 | VIR19Z | LHR → SFO | May 27, 13:15 UTC | May 27, 23:35 UTC | 10h 20m |
| 2026-05-26 | VIR8Y | LAX → LHR | May 26, 23:05 UTC | May 27, 08:55 UTC | 9h 51m |
| 2026-05-26 | VIR7B | LHR → LAX | May 26, 10:05 UTC | May 26, 20:40 UTC | 10h 35m |
| 2026-05-25 | VIR104L | ATL → LHR | May 25, 23:54 UTC | May 26, 07:34 UTC | 7h 40m |
| 2026-05-25 | VIR103M | LHR → ATL | May 25, 10:45 UTC | May 25, 19:15 UTC | 8h 30m |
| 2026-05-25 | VIR10H | JFK → LHR | May 25, 01:55 UTC | May 25, 06:45 UTC | 4h 50m |
| 2026-05-24 | VIR3N | LHR → JFK | May 24, 07:35 UTC | May 24, 14:25 UTC | 6h 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 G-VRNB page for operator, model, and routing details .