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
- 160
- Distinct callsigns
- 20
- Country
- MT
- Last broadcast
- 1d 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 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| SVA798 | Saudi Arabian Airlines | 43 | 2026-06-21 |
| SVA9684 | - | 25 | 2026-05-19 |
| SVA799 | Saudi Arabian Airlines | 14 | 2026-06-29 |
| SVA5799 | - | 11 | 2026-05-21 |
| SVA3684 | Saudi Arabian Airlines | 10 | 2026-06-25 |
| SVA5798 | - | 9 | 2026-06-28 |
| SVA808 | - | 8 | 2026-06-22 |
| SVA809 | - | 7 | 2026-06-23 |
| SVA3686 | Saudi Arabian Airlines | 7 | 2026-06-06 |
| SVA351 | Saudi Arabian Airlines | 4 | 2026-05-12 |
| SVA9655 | - | 3 | 2026-06-05 |
| SVA5808 | - | 3 | 2026-06-19 |
| SVA5346 | - | 3 | 2026-06-08 |
| SVA341 | - | 3 | 2026-07-16 |
| SVA9637 | - | 2 | 2026-06-26 |
| SVA3645 | Saudi Arabian Airlines | 2 | 2026-04-21 |
| SVA9663 | - | 1 | 2026-06-02 |
| SVA9635 | - | 1 | 2026-06-07 |
| SVA9378 | - | 1 | 2026-06-09 |
| SVA5809 | Saudi Arabian Airlines | 1 | 2026-05-03 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-16 | SVA340 | ALG → JED | Jul 16, 14:50 UTC | Jul 16, 18:00 UTC | 3h 10m |
| 2026-07-16 | SVA341 | - | Jul 16, 12:25 UTC | Jul 16, 12:40 UTC | 15m |
| 2026-07-16 | SVA341 | - | Jul 16, 09:45 UTC | Jul 16, 11:45 UTC | 2h 0m |
| 2026-06-29 | SVA799 | DAC → MED | Jun 29, 10:29 UTC | Jun 29, 13:09 UTC | 2h 40m |
| 2026-06-28 | SVA5798 | - | Jun 28, 12:39 UTC | Jun 29, 08:14 UTC | 19h 35m |
| 2026-06-28 | SVA5798 | - | Jun 28, 10:35 UTC | Jun 29, 08:14 UTC | 21h 40m |
| 2026-06-28 | SVA5798 | - | Jun 28, 03:05 UTC | Jun 28, 08:25 UTC | 5h 20m |
| 2026-06-26 | SVA9637 | - | Jun 26, 05:19 UTC | Jun 26, 06:35 UTC | 1h 15m |
| 2026-06-25 | SVA9637 | - | Jun 25, 06:35 UTC | Jun 26, 06:29 UTC | 23h 55m |
| 2026-06-25 | SVA3684 | JED → HDY | Jun 25, 02:10 UTC | Jun 25, 06:44 UTC | 4h 35m |
| 2026-06-23 | SVA809 | - | Jun 23, 10:10 UTC | Jun 23, 10:49 UTC | 40m |
| 2026-06-23 | SVA809 | - | Jun 23, 08:04 UTC | Jun 23, 08:59 UTC | 55m |
| 2026-06-22 | SVA808 | - | Jun 22, 10:34 UTC | Jun 23, 05:39 UTC | 19h 5m |
| 2026-06-22 | SVA808 | DAC → DAC | Jun 22, 10:10 UTC | Jun 23, 05:39 UTC | 19h 30m |
| 2026-06-21 | SVA798 | MED → PEW | Jun 21, 12:35 UTC | Jun 22, 08:04 UTC | 19h 30m |
| 2026-06-21 | SVA798 | MED → PEW | Jun 21, 10:34 UTC | Jun 22, 08:04 UTC | 21h 30m |
| 2026-06-21 | SVA798 | MED → PEW | Jun 21, 10:25 UTC | Jun 22, 08:04 UTC | 21h 40m |
| 2026-06-21 | SVA5798 | - | Jun 21, 03:10 UTC | Jun 21, 08:20 UTC | 5h 10m |
| 2026-06-19 | SVA809 | - | Jun 19, 08:09 UTC | Jun 19, 10:54 UTC | 2h 45m |
| 2026-06-19 | SVA5808 | - | Jun 19, 00:34 UTC | Jun 19, 05:40 UTC | 5h 5m |
| 2026-06-17 | SVA799 | DAC → MED | Jun 17, 10:05 UTC | Jun 17, 15:00 UTC | 4h 55m |
| 2026-06-17 | SVA5796 | - | Jun 17, 02:50 UTC | Jun 17, 07:40 UTC | 4h 50m |
| 2026-06-15 | SVA799 | DAC → MED | Jun 15, 10:09 UTC | Jun 15, 12:55 UTC | 2h 45m |
| 2026-06-15 | SVA798 | MED → PEW | Jun 15, 03:15 UTC | Jun 15, 08:10 UTC | 4h 55m |
| 2026-06-13 | SVA809 | - | Jun 13, 08:40 UTC | Jun 13, 11:30 UTC | 2h 50m |
| 2026-06-13 | SVA5808 | - | Jun 13, 01:15 UTC | Jun 13, 06:25 UTC | 5h 9m |
| 2026-06-11 | SVA799 | DAC → MED | Jun 11, 10:15 UTC | Jun 11, 13:05 UTC | 2h 50m |
| 2026-06-10 | SVA5798 | - | Jun 10, 12:35 UTC | Jun 11, 08:00 UTC | 19h 25m |
| 2026-06-10 | SVA5798 | - | Jun 10, 10:35 UTC | Jun 11, 08:00 UTC | 21h 25m |
| 2026-06-10 | SVA799 | DAC → MED | Jun 10, 10:10 UTC | Jun 11, 08:00 UTC | 21h 50m |
| 2026-06-10 | SVA5798 | - | Jun 10, 03:05 UTC | Jun 10, 08:15 UTC | 5h 10m |
| 2026-06-09 | SVA9378 | - | Jun 9, 06:55 UTC | Jun 10, 06:05 UTC | 23h 10m |
| 2026-06-08 | SVA5346 | - | Jun 8, 12:35 UTC | Jun 9, 08:25 UTC | 19h 50m |
| 2026-06-08 | SVA5346 | - | Jun 8, 10:35 UTC | Jun 9, 08:25 UTC | 21h 50m |
| 2026-06-08 | SVA5346 | - | Jun 8, 10:05 UTC | Jun 9, 08:25 UTC | 22h 20m |
| 2026-06-08 | SVA5798 | - | Jun 8, 03:00 UTC | Jun 8, 08:00 UTC | 5h 0m |
| 2026-06-07 | SVA5798 | - | Jun 7, 06:35 UTC | Jun 8, 05:55 UTC | 23h 20m |
| 2026-06-07 | SVA9635 | - | Jun 7, 05:45 UTC | Jun 8, 03:15 UTC | 21h 30m |
| 2026-06-06 | SVA3686 | JED → HDY | Jun 6, 06:50 UTC | Jun 7, 06:30 UTC | 23h 40m |
| 2026-06-05 | SVA9655 | - | Jun 5, 15:40 UTC | Jun 6, 08:25 UTC | 16h 45m |
| 2026-06-05 | SVA9655 | - | Jun 5, 06:35 UTC | Jun 6, 04:45 UTC | 22h 10m |
| 2026-06-05 | SVA3684 | JED → HDY | Jun 5, 06:10 UTC | Jun 6, 04:30 UTC | 22h 20m |
| 2026-06-04 | SVA3684 | JED → HDY | Jun 4, 16:35 UTC | Jun 5, 16:30 UTC | 23h 55m |
| 2026-06-04 | SVA3684 | JED → HDY | Jun 4, 15:45 UTC | Jun 5, 08:25 UTC | 16h 40m |
| 2026-06-04 | SVA9655 | - | Jun 4, 06:35 UTC | Jun 5, 06:30 UTC | 23h 55m |
| 2026-06-04 | SVA3686 | JED → HDY | Jun 4, 06:10 UTC | Jun 4, 17:25 UTC | 11h 15m |
| 2026-06-03 | SVA3686 | JED → HDY | Jun 3, 17:05 UTC | Jun 4, 16:30 UTC | 23h 25m |
| 2026-06-03 | SVA3686 | JED → HDY | Jun 3, 15:55 UTC | Jun 4, 08:20 UTC | 16h 25m |
| 2026-06-03 | SVA3684 | JED → HDY | Jun 3, 04:00 UTC | Jun 3, 17:15 UTC | 13h 15m |
| 2026-06-02 | SVA3684 | JED → HDY | Jun 2, 16:35 UTC | Jun 3, 16:25 UTC | 23h 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-AZG page for operator, model, and routing details .