sensors Mode-S transponder
43EB4A
ICAO 24-bit transponder address · allocated to United Kingdom
Currently assigned to 2-MATO · BOMBARDIER BD-700 Global 5000/5500
- Hex
- 43EB4A
- Octal
- 20765512
- Decimal
- 4,451,146
- Country
- GB
- Tail
- 2-MATO
- Type
- GL5T
- Flights observed
- 54
- Distinct callsigns
- 17
- Country
- GB
- Last broadcast
- 6d ago
Last known position
Country allocation
The ICAO 24-bit address 43EB4A 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 17 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| VLZ93X | - | 5 | 2026-07-23 |
| VLZ88X | - | 4 | 2026-07-24 |
| VLZ86X | - | 4 | 2026-07-09 |
| VLZ85X | - | 4 | 2026-06-28 |
| VLZ78J | - | 4 | 2026-07-13 |
| VLZ73X | - | 4 | 2026-05-31 |
| VLZ69X | - | 4 | 2026-05-26 |
| VLZ95J | - | 3 | 2026-06-21 |
| VLZ93J | - | 3 | 2026-06-21 |
| VLZ90X | - | 3 | 2026-07-17 |
| VLZ87X | - | 3 | 2026-07-15 |
| VLZ64J | - | 3 | 2026-06-28 |
| VLZ96J | - | 2 | 2026-06-25 |
| VLZ92J | - | 2 | 2026-06-18 |
| VLZ75J | - | 2 | 2026-05-03 |
| VLZ69J | - | 2 | 2026-04-27 |
| VLZ01K | - | 2 | 2026-07-01 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-24 | VLZ88X | EDI → OXF | Jul 24, 19:00 UTC | Jul 24, 19:50 UTC | 50m |
| 2026-07-24 | VLZ88X | RKV → EDI | Jul 24, 16:25 UTC | Jul 24, 18:10 UTC | 1h 45m |
| 2026-07-23 | VLZ93X | - | Jul 23, 19:25 UTC | Jul 23, 22:00 UTC | 2h 35m |
| 2026-07-23 | VLZ93X | - | Jul 23, 17:20 UTC | Jul 23, 18:45 UTC | 1h 25m |
| 2026-07-20 | VLZ93X | - | Jul 20, 07:30 UTC | Jul 20, 08:45 UTC | 1h 15m |
| 2026-07-20 | VLZ93X | OXF → FAB | Jul 20, 05:50 UTC | Jul 20, 06:10 UTC | 20m |
| 2026-07-19 | VLZ93X | RKV → OXF | Jul 19, 12:15 UTC | Jul 19, 14:20 UTC | 2h 5m |
| 2026-07-19 | VLZ88X | EDI → RKV | Jul 19, 09:25 UTC | Jul 19, 11:20 UTC | 1h 55m |
| 2026-07-19 | VLZ88X | PIK → EDI | Jul 19, 06:20 UTC | Jul 19, 06:45 UTC | 25m |
| 2026-07-17 | VLZ90X | EDI → PIK | Jul 17, 16:40 UTC | Jul 17, 16:59 UTC | 20m |
| 2026-07-17 | VLZ90X | - | Jul 17, 14:44 UTC | Jul 17, 15:44 UTC | 1h 0m |
| 2026-07-17 | VLZ90X | OXF → FAB | Jul 17, 10:55 UTC | Jul 17, 11:20 UTC | 25m |
| 2026-07-15 | VLZ87X | - | Jul 15, 19:30 UTC | Jul 15, 20:05 UTC | 35m |
| 2026-07-15 | VLZ87X | - | Jul 15, 17:45 UTC | Jul 15, 18:45 UTC | 1h 0m |
| 2026-07-14 | VLZ87X | - | Jul 14, 08:55 UTC | Jul 14, 10:05 UTC | 1h 10m |
| 2026-07-13 | VLZ78J | - | Jul 13, 13:15 UTC | Jul 13, 15:40 UTC | 2h 25m |
| 2026-07-13 | VLZ78J | - | Jul 13, 09:50 UTC | Jul 13, 10:35 UTC | 45m |
| 2026-07-09 | VLZ86X | - | Jul 9, 14:50 UTC | Jul 9, 15:35 UTC | 45m |
| 2026-07-09 | VLZ86X | - | Jul 9, 12:25 UTC | Jul 9, 12:50 UTC | 25m |
| 2026-07-05 | VLZ86X | - | Jul 5, 13:10 UTC | Jul 5, 13:45 UTC | 35m |
| 2026-07-05 | VLZ86X | - | Jul 5, 10:15 UTC | Jul 5, 11:00 UTC | 45m |
| 2026-07-04 | VLZ78J | - | Jul 4, 15:35 UTC | Jul 4, 16:25 UTC | 50m |
| 2026-07-04 | VLZ78J | - | Jul 4, 12:00 UTC | Jul 4, 14:00 UTC | 2h 0m |
| 2026-07-01 | VLZ01K | - | Jul 1, 06:00 UTC | Jul 1, 07:10 UTC | 1h 10m |
| 2026-06-29 | VLZ01K | - | Jun 29, 13:54 UTC | Jun 29, 15:04 UTC | 1h 10m |
| 2026-06-28 | VLZ64J | IBZ → OXF | Jun 28, 10:24 UTC | Jun 28, 12:15 UTC | 1h 50m |
| 2026-06-28 | VLZ85X | - | Jun 28, 08:29 UTC | Jun 28, 08:55 UTC | 25m |
| 2026-06-27 | VLZ64J | IBZ → ALC | Jun 27, 19:24 UTC | Jun 27, 20:04 UTC | 40m |
| 2026-06-25 | VLZ64J | - | Jun 25, 13:20 UTC | Jun 25, 15:29 UTC | 2h 10m |
| 2026-06-25 | VLZ96J | - | Jun 25, 04:45 UTC | Jun 25, 12:44 UTC | 8h 0m |
| 2026-06-24 | VLZ96J | - | Jun 24, 05:54 UTC | Jun 24, 15:00 UTC | 9h 5m |
| 2026-06-22 | VLZ85X | - | Jun 22, 21:40 UTC | Jun 22, 22:19 UTC | 40m |
| 2026-06-22 | VLZ85X | IBZ → BFS | Jun 22, 18:09 UTC | Jun 22, 20:39 UTC | 2h 30m |
| 2026-06-22 | VLZ85X | - | Jun 22, 14:55 UTC | Jun 22, 16:54 UTC | 2h 0m |
| 2026-06-21 | VLZ93J | - | Jun 21, 15:09 UTC | Jun 21, 17:10 UTC | 2h 0m |
| 2026-06-21 | VLZ95J | BHX → RMI | Jun 21, 12:10 UTC | Jun 21, 14:05 UTC | 1h 55m |
| 2026-06-20 | VLZ95J | IAD → BHX | Jun 20, 16:55 UTC | Jun 20, 23:14 UTC | 6h 20m |
| 2026-06-19 | VLZ95J | - | Jun 19, 16:14 UTC | Jun 20, 01:05 UTC | 8h 50m |
| 2026-06-19 | VLZ93J | - | Jun 19, 13:20 UTC | Jun 19, 15:04 UTC | 1h 45m |
| 2026-06-19 | VLZ93J | - | Jun 19, 11:39 UTC | Jun 19, 11:54 UTC | 15m |
| 2026-06-18 | VLZ92J | IAD → OXF | Jun 18, 14:45 UTC | Jun 18, 21:15 UTC | 6h 30m |
| 2026-06-11 | VLZ92J | - | Jun 11, 09:45 UTC | Jun 11, 17:20 UTC | 7h 35m |
| 2026-05-31 | VLZ73X | BQH → OXF | May 31, 11:05 UTC | May 31, 11:40 UTC | 35m |
| 2026-05-31 | VLZ73X | BTS → BQH | May 31, 08:30 UTC | May 31, 10:20 UTC | 1h 50m |
| 2026-05-29 | VLZ73X | BQH → BTS | May 29, 11:55 UTC | May 29, 13:40 UTC | 1h 45m |
| 2026-05-29 | VLZ73X | - | May 29, 08:50 UTC | May 29, 09:15 UTC | 25m |
| 2026-05-26 | VLZ69X | ZRH → OXF | May 26, 12:05 UTC | May 26, 13:24 UTC | 1h 20m |
| 2026-05-26 | VLZ69X | - | May 26, 09:09 UTC | May 26, 10:50 UTC | 1h 40m |
| 2026-05-23 | VLZ69X | - | May 23, 09:40 UTC | May 23, 11:20 UTC | 1h 40m |
| 2026-05-23 | VLZ69X | - | May 23, 06:40 UTC | May 23, 07:55 UTC | 1h 15m |
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 2-MATO page for operator, model, and routing details .