sensors Mode-S transponder
4D2011
ICAO 24-bit transponder address · allocated to Malta
Currently assigned to 9H-AZH · BOEING 777-200
- Hex
- 4D2011
- Octal
- 23220021
- Decimal
- 5,054,481
- Country
- MT
- Tail
- 9H-AZH
- Type
- B772
- Flights observed
- 94
- Distinct callsigns
- 15
- Country
- MT
- Last broadcast
- 9h ago
Current position
Country allocation
The ICAO 24-bit address 4D2011 falls within the block assigned to Malta (MT) by ICAO Annex 10, Volume III. Every aircraft registered in Malta 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 15 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| SVA808 | Saudi Arabian Airlines | 41 | 2026-05-29 |
| SVA9682 | - | 23 | 2026-04-22 |
| SVA809 | Saudi Arabian Airlines | 9 | 2026-05-29 |
| SVA5809 | Saudi Arabian Airlines | 7 | 2026-05-21 |
| SVA3682 | Saudi Arabian Airlines | 4 | 2026-06-02 |
| SVA9647 | - | 1 | 2026-06-01 |
| SVA9334 | - | 1 | 2026-04-27 |
| SVA799 | Saudi Arabian Airlines | 1 | 2026-05-31 |
| SVA798 | Saudi Arabian Airlines | 1 | 2026-05-02 |
| SVA5799 | - | 1 | 2026-05-03 |
| SVA5143 | - | 1 | 2026-04-28 |
| SVA3647 | Saudi Arabian Airlines | 1 | 2026-04-23 |
| SVA351 | Saudi Arabian Airlines | 1 | 2026-05-05 |
| SVA341 | Saudi Arabian Airlines | 1 | 2026-05-26 |
| SVA340 | Saudi Arabian Airlines | 1 | 2026-05-26 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | SVA3682 | JED → HDY | Jun 2, 12:05 UTC | Jun 3, 03:00 UTC | 14h 55m |
| 2026-06-02 | SVA3682 | JED → HDY | Jun 2, 02:20 UTC | Jun 3, 02:15 UTC | 23h 55m |
| 2026-06-02 | SVA3682 | JED → HDY | Jun 2, 00:00 UTC | Jun 2, 12:20 UTC | 12h 20m |
| 2026-06-01 | SVA9647 | - | Jun 1, 12:20 UTC | Jun 2, 12:15 UTC | 23h 55m |
| 2026-06-01 | SVA3682 | JED → HDY | Jun 1, 02:50 UTC | Jun 2, 00:20 UTC | 21h 30m |
| 2026-05-31 | SVA799 | DAC → MED | May 31, 10:00 UTC | Jun 1, 03:15 UTC | 17h 15m |
| 2026-05-29 | SVA809 | DAC → JED | May 29, 08:00 UTC | May 29, 10:50 UTC | 2h 50m |
| 2026-05-29 | SVA808 | RUH → DAC | May 29, 01:00 UTC | May 29, 06:15 UTC | 5h 15m |
| 2026-05-26 | SVA340 | ALG → JED | May 26, 14:55 UTC | May 26, 17:30 UTC | 2h 35m |
| 2026-05-26 | SVA341 | JED → ALG | May 26, 09:55 UTC | May 26, 12:05 UTC | 2h 10m |
| 2026-05-23 | SVA809 | DAC → JED | May 23, 07:35 UTC | May 23, 10:20 UTC | 2h 45m |
| 2026-05-22 | SVA808 | RUH → DAC | May 22, 10:20 UTC | May 23, 05:35 UTC | 19h 15m |
| 2026-05-22 | SVA808 | RUH → DAC | May 22, 09:45 UTC | May 23, 05:35 UTC | 19h 49m |
| 2026-05-22 | SVA808 | RUH → DAC | May 22, 07:40 UTC | May 23, 05:35 UTC | 21h 54m |
| 2026-05-21 | SVA808 | RUH → DAC | May 21, 10:20 UTC | May 22, 05:45 UTC | 19h 25m |
| 2026-05-21 | SVA5809 | DMM → JED | May 21, 08:20 UTC | May 22, 05:45 UTC | 21h 25m |
| 2026-05-21 | SVA5809 | DMM → JED | May 21, 07:55 UTC | May 22, 05:45 UTC | 21h 50m |
| 2026-05-20 | SVA808 | RUH → DAC | May 20, 10:20 UTC | May 21, 05:45 UTC | 19h 25m |
| 2026-05-20 | SVA5809 | DMM → JED | May 20, 09:45 UTC | May 21, 05:45 UTC | 20h 0m |
| 2026-05-20 | SVA5809 | DMM → JED | May 20, 07:40 UTC | May 21, 05:45 UTC | 22h 5m |
| 2026-05-19 | SVA808 | RUH → DAC | May 19, 10:35 UTC | May 20, 05:45 UTC | 19h 11m |
| 2026-05-19 | SVA808 | RUH → DAC | May 19, 08:30 UTC | May 20, 05:45 UTC | 21h 16m |
| 2026-05-18 | SVA808 | RUH → DAC | May 18, 10:25 UTC | May 19, 05:45 UTC | 19h 19m |
| 2026-05-18 | SVA808 | RUH → DAC | May 18, 08:20 UTC | May 19, 05:45 UTC | 21h 24m |
| 2026-05-18 | SVA808 | RUH → DAC | May 18, 08:05 UTC | May 19, 05:45 UTC | 21h 39m |
| 2026-05-17 | SVA808 | RUH → DAC | May 17, 10:20 UTC | May 18, 05:45 UTC | 19h 25m |
| 2026-05-17 | SVA808 | RUH → DAC | May 17, 09:50 UTC | May 18, 05:45 UTC | 19h 55m |
| 2026-05-17 | SVA808 | RUH → DAC | May 17, 07:40 UTC | May 18, 05:45 UTC | 22h 5m |
| 2026-05-17 | SVA808 | RUH → DAC | May 17, 02:20 UTC | May 17, 05:15 UTC | 2h 55m |
| 2026-05-15 | SVA809 | DAC → JED | May 15, 07:40 UTC | May 15, 10:45 UTC | 3h 5m |
| 2026-05-14 | SVA808 | RUH → DAC | May 14, 10:20 UTC | May 15, 05:20 UTC | 19h 0m |
| 2026-05-14 | SVA808 | RUH → DAC | May 14, 08:20 UTC | May 15, 05:20 UTC | 21h 0m |
| 2026-05-14 | SVA808 | RUH → DAC | May 14, 07:45 UTC | May 15, 05:20 UTC | 21h 35m |
| 2026-05-13 | SVA808 | RUH → DAC | May 13, 10:20 UTC | May 14, 05:20 UTC | 19h 0m |
| 2026-05-13 | SVA808 | RUH → DAC | May 13, 08:20 UTC | May 14, 05:20 UTC | 21h 0m |
| 2026-05-13 | SVA808 | RUH → DAC | May 13, 07:45 UTC | May 14, 05:20 UTC | 21h 35m |
| 2026-05-13 | SVA808 | RUH → DAC | May 13, 02:50 UTC | May 13, 05:40 UTC | 2h 50m |
| 2026-05-11 | SVA809 | DAC → JED | May 11, 08:00 UTC | May 11, 11:05 UTC | 3h 5m |
| 2026-05-10 | SVA808 | RUH → DAC | May 10, 10:19 UTC | May 11, 05:30 UTC | 19h 10m |
| 2026-05-10 | SVA809 | DAC → JED | May 10, 08:20 UTC | May 11, 05:30 UTC | 21h 10m |
| 2026-05-10 | SVA809 | DAC → JED | May 10, 08:00 UTC | May 11, 05:30 UTC | 21h 30m |
| 2026-05-09 | SVA808 | RUH → DAC | May 9, 10:20 UTC | May 10, 06:00 UTC | 19h 40m |
| 2026-05-09 | SVA5809 | DMM → JED | May 9, 09:45 UTC | May 10, 06:00 UTC | 20h 15m |
| 2026-05-09 | SVA808 | RUH → DAC | May 9, 06:35 UTC | May 9, 07:30 UTC | 55m |
| 2026-05-08 | SVA808 | RUH → DAC | May 8, 08:19 UTC | May 9, 07:30 UTC | 23h 10m |
| 2026-05-08 | SVA5809 | DMM → JED | May 8, 07:39 UTC | May 8, 08:40 UTC | 1h 0m |
| 2026-05-08 | SVA808 | RUH → DAC | May 8, 00:54 UTC | May 8, 05:49 UTC | 4h 55m |
| 2026-05-07 | SVA808 | RUH → DAC | May 7, 08:20 UTC | May 8, 05:49 UTC | 21h 29m |
| 2026-05-07 | SVA809 | DAC → JED | May 7, 07:30 UTC | May 8, 05:49 UTC | 22h 20m |
| 2026-05-07 | SVA808 | RUH → DAC | May 7, 00:45 UTC | May 7, 05:35 UTC | 4h 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 9H-AZH page for operator, model, and routing details .