sensors Mode-S transponder
4D2012
ICAO 24-bit transponder address · allocated to Malta
Currently assigned to 9H-AZG · BOEING 777-200
- Hex
- 4D2012
- Octal
- 23220022
- Decimal
- 5,054,482
- Country
- MT
- Tail
- 9H-AZG
- Type
- B772
- Flights observed
- 107
- Distinct callsigns
- 13
- Country
- MT
- Last broadcast
- 11h ago
Last known position
Country allocation
The ICAO 24-bit address 4D2012 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 13 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| SVA798 | Saudi Arabian Airlines | 39 | 2026-05-27 |
| SVA9684 | - | 25 | 2026-05-19 |
| SVA5799 | - | 11 | 2026-05-21 |
| SVA799 | Saudi Arabian Airlines | 9 | 2026-05-27 |
| SVA808 | Saudi Arabian Airlines | 6 | 2026-05-16 |
| SVA351 | Saudi Arabian Airlines | 4 | 2026-05-12 |
| SVA809 | Saudi Arabian Airlines | 3 | 2026-05-30 |
| SVA3686 | Saudi Arabian Airlines | 3 | 2026-06-02 |
| SVA3684 | Saudi Arabian Airlines | 2 | 2026-06-01 |
| SVA3645 | Saudi Arabian Airlines | 2 | 2026-04-21 |
| SVA5809 | Saudi Arabian Airlines | 1 | 2026-05-03 |
| SVA5808 | - | 1 | 2026-05-30 |
| SVA341 | Saudi Arabian Airlines | 1 | 2026-05-23 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | SVA3686 | JED → HDY | Jun 2, 03:50 UTC | Jun 2, 16:35 UTC | 12h 45m |
| 2026-06-01 | SVA3686 | JED → HDY | Jun 1, 16:00 UTC | Jun 2, 06:40 UTC | 14h 40m |
| 2026-06-01 | SVA3686 | JED → HDY | Jun 1, 06:45 UTC | Jun 2, 06:30 UTC | 23h 45m |
| 2026-06-01 | SVA3684 | JED → HDY | Jun 1, 04:35 UTC | Jun 2, 04:25 UTC | 23h 50m |
| 2026-06-01 | SVA3684 | JED → HDY | Jun 1, 04:25 UTC | Jun 1, 16:25 UTC | 12h 0m |
| 2026-05-30 | SVA809 | DAC → JED | May 30, 09:35 UTC | May 30, 12:25 UTC | 2h 50m |
| 2026-05-30 | SVA5808 | - | May 30, 04:20 UTC | May 30, 07:10 UTC | 2h 50m |
| 2026-05-27 | SVA799 | DAC → MED | May 27, 10:05 UTC | May 27, 13:10 UTC | 3h 5m |
| 2026-05-27 | SVA798 | MED → PEW | May 27, 05:09 UTC | May 27, 08:00 UTC | 2h 50m |
| 2026-05-25 | SVA799 | DAC → MED | May 25, 09:55 UTC | May 25, 12:50 UTC | 2h 55m |
| 2026-05-24 | SVA798 | MED → PEW | May 24, 12:35 UTC | May 25, 08:10 UTC | 19h 35m |
| 2026-05-24 | SVA798 | MED → PEW | May 24, 10:35 UTC | May 25, 08:10 UTC | 21h 35m |
| 2026-05-24 | SVA798 | MED → PEW | May 24, 10:10 UTC | May 25, 08:10 UTC | 22h 0m |
| 2026-05-23 | SVA798 | MED → PEW | May 23, 15:00 UTC | May 24, 08:20 UTC | 17h 20m |
| 2026-05-23 | SVA341 | JED → ALG | May 23, 09:35 UTC | May 23, 11:55 UTC | 2h 20m |
| 2026-05-21 | SVA5799 | - | May 21, 10:15 UTC | May 21, 13:20 UTC | 3h 5m |
| 2026-05-20 | SVA798 | MED → PEW | May 20, 12:00 UTC | May 21, 07:50 UTC | 19h 50m |
| 2026-05-19 | SVA9684 | - | May 19, 11:10 UTC | May 19, 11:35 UTC | 25m |
| 2026-05-18 | SVA5799 | - | May 18, 12:35 UTC | May 19, 11:35 UTC | 22h 59m |
| 2026-05-18 | SVA5799 | - | May 18, 10:05 UTC | May 18, 13:05 UTC | 3h 0m |
| 2026-05-17 | SVA798 | MED → PEW | May 17, 12:35 UTC | May 18, 07:55 UTC | 19h 20m |
| 2026-05-17 | SVA798 | MED → PEW | May 17, 10:35 UTC | May 18, 07:55 UTC | 21h 20m |
| 2026-05-17 | SVA5799 | - | May 17, 10:10 UTC | May 18, 05:50 UTC | 19h 40m |
| 2026-05-17 | SVA798 | MED → PEW | May 17, 03:05 UTC | May 17, 07:45 UTC | 4h 40m |
| 2026-05-16 | SVA798 | MED → PEW | May 16, 10:35 UTC | May 17, 07:45 UTC | 21h 10m |
| 2026-05-16 | SVA798 | MED → PEW | May 16, 08:36 UTC | May 17, 07:45 UTC | 23h 10m |
| 2026-05-16 | SVA809 | DAC → JED | May 16, 08:01 UTC | May 17, 05:45 UTC | 21h 44m |
| 2026-05-16 | SVA808 | RUH → DAC | May 16, 03:20 UTC | May 16, 06:06 UTC | 2h 46m |
| 2026-05-14 | SVA5799 | - | May 14, 10:05 UTC | May 14, 13:10 UTC | 3h 5m |
| 2026-05-13 | SVA798 | MED → PEW | May 13, 12:35 UTC | May 14, 07:20 UTC | 18h 45m |
| 2026-05-13 | SVA798 | MED → PEW | May 13, 10:35 UTC | May 14, 07:20 UTC | 20h 45m |
| 2026-05-13 | SVA5799 | - | May 13, 10:15 UTC | May 14, 07:20 UTC | 21h 5m |
| 2026-05-12 | SVA798 | MED → PEW | May 12, 13:15 UTC | May 13, 07:35 UTC | 18h 20m |
| 2026-05-12 | SVA351 | JED → ALG | May 12, 07:15 UTC | May 12, 10:25 UTC | 3h 10m |
| 2026-05-11 | SVA351 | JED → ALG | May 11, 12:35 UTC | May 12, 10:25 UTC | 21h 51m |
| 2026-05-11 | SVA351 | JED → ALG | May 11, 10:35 UTC | May 12, 10:25 UTC | 23h 51m |
| 2026-05-11 | SVA5799 | - | May 11, 10:05 UTC | May 12, 08:30 UTC | 22h 26m |
| 2026-05-10 | SVA798 | MED → PEW | May 10, 12:34 UTC | May 11, 07:50 UTC | 19h 15m |
| 2026-05-10 | SVA798 | MED → PEW | May 10, 10:35 UTC | May 11, 07:50 UTC | 21h 15m |
| 2026-05-10 | SVA798 | MED → PEW | May 10, 10:00 UTC | May 11, 07:50 UTC | 21h 50m |
| 2026-05-09 | SVA798 | MED → PEW | May 9, 13:05 UTC | May 10, 07:55 UTC | 18h 50m |
| 2026-05-09 | SVA798 | MED → PEW | May 9, 08:35 UTC | May 10, 07:55 UTC | 23h 20m |
| 2026-05-09 | SVA351 | JED → ALG | May 9, 07:20 UTC | May 10, 05:55 UTC | 22h 35m |
| 2026-05-07 | SVA5799 | - | May 7, 10:00 UTC | May 7, 11:00 UTC | 1h 0m |
| 2026-05-07 | SVA798 | MED → PEW | May 7, 03:05 UTC | May 7, 07:50 UTC | 4h 45m |
| 2026-05-06 | SVA798 | MED → PEW | May 6, 10:35 UTC | May 7, 07:50 UTC | 21h 15m |
| 2026-05-06 | SVA5799 | DAC → DAC | May 6, 09:50 UTC | May 7, 07:50 UTC | 22h 0m |
| 2026-05-06 | SVA798 | MED → PEW | May 6, 03:00 UTC | May 6, 07:35 UTC | 4h 35m |
| 2026-05-04 | SVA5799 | - | May 4, 10:00 UTC | May 4, 10:55 UTC | 55m |
| 2026-05-04 | SVA798 | MED → PEW | May 4, 03:15 UTC | May 4, 07:50 UTC | 4h 35m |
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-AZG page for operator, model, and routing details .