sensors Mode-S transponder
4D2078
ICAO 24-bit transponder address · allocated to Malta
Currently assigned to 9H-AKK · BOEING 747-400
- Hex
- 4D2078
- Octal
- 23220170
- Decimal
- 5,054,584
- Country
- MT
- Tail
- 9H-AKK
- Type
- B744
- Flights observed
- 34
- Distinct callsigns
- 18
- Country
- MT
- Last broadcast
- 14d ago
Last known position
Country allocation
The ICAO 24-bit address 4D2078 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 18 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| SVA3902 | Saudi Arabian Airlines | 6 | 2026-04-13 |
| SVA3041 | Saudi Arabian Airlines | 4 | 2026-05-05 |
| SVA925 | Saudi Arabian Airlines | 3 | 2026-05-10 |
| SVA3020 | Saudi Arabian Airlines | 3 | 2026-04-23 |
| SVA929 | Saudi Arabian Airlines | 2 | 2026-04-24 |
| SVA922 | Saudi Arabian Airlines | 2 | 2026-05-12 |
| SVA921 | Saudi Arabian Airlines | 2 | 2026-05-11 |
| SVA3042 | Saudi Arabian Airlines | 2 | 2026-05-05 |
| SVA985 | Saudi Arabian Airlines | 1 | 2026-05-10 |
| SVA984 | Saudi Arabian Airlines | 1 | 2026-05-10 |
| SVA932 | Saudi Arabian Airlines | 1 | 2026-04-22 |
| SVA931 | Saudi Arabian Airlines | 1 | 2026-04-21 |
| SVA930 | - | 1 | 2026-04-24 |
| SVA926 | Saudi Arabian Airlines | 1 | 2026-04-27 |
| SVA3940 | - | 1 | 2026-05-01 |
| SVA3021 | Saudi Arabian Airlines | 1 | 2026-04-23 |
| AAE44P | - | 1 | 2026-05-16 |
| AAE044P | - | 1 | 2026-05-14 |
Recent flights last 34
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-16 | AAE44P | - | May 16, 00:15 UTC | May 16, 00:30 UTC | 15m |
| 2026-05-14 | AAE044P | - | May 14, 08:10 UTC | May 14, 22:10 UTC | 14h 0m |
| 2026-05-12 | SVA922 | BRU → JED | May 12, 10:40 UTC | May 12, 13:05 UTC | 2h 25m |
| 2026-05-11 | SVA921 | RUH → LGG | May 11, 15:10 UTC | May 12, 05:55 UTC | 14h 46m |
| 2026-05-10 | SVA925 | RUH → FRA | May 10, 16:04 UTC | May 11, 11:30 UTC | 19h 25m |
| 2026-05-10 | SVA925 | RUH → FRA | May 10, 14:40 UTC | May 11, 11:30 UTC | 20h 50m |
| 2026-05-10 | SVA985 | HKG → RUH | May 10, 12:10 UTC | May 10, 12:19 UTC | 10m |
| 2026-05-10 | SVA984 | DMM → HKG | May 10, 01:20 UTC | May 10, 08:45 UTC | 7h 25m |
| 2026-05-05 | SVA3042 | MST → JED | May 5, 20:05 UTC | May 5, 23:40 UTC | 3h 35m |
| 2026-05-05 | SVA3041 | JED → KRF | May 5, 17:05 UTC | May 5, 17:55 UTC | 50m |
| 2026-05-03 | SVA3041 | JED → KRF | May 3, 06:10 UTC | May 3, 14:35 UTC | 8h 25m |
| 2026-05-02 | SVA3041 | JED → KRF | May 2, 05:55 UTC | May 2, 08:45 UTC | 2h 50m |
| 2026-05-01 | SVA3940 | - | May 1, 21:05 UTC | May 2, 01:10 UTC | 4h 5m |
| 2026-04-30 | SVA3042 | MST → JED | Apr 30, 10:50 UTC | Apr 30, 14:35 UTC | 3h 45m |
| 2026-04-29 | SVA3041 | JED → KRF | Apr 29, 10:50 UTC | Apr 29, 17:50 UTC | 7h 0m |
| 2026-04-27 | SVA926 | BRU → JED | Apr 27, 17:15 UTC | Apr 27, 19:50 UTC | 2h 35m |
| 2026-04-27 | SVA925 | RUH → FRA | Apr 27, 07:25 UTC | Apr 27, 11:40 UTC | 4h 15m |
| 2026-04-24 | SVA930 | - | Apr 24, 15:05 UTC | Apr 24, 18:35 UTC | 3h 30m |
| 2026-04-24 | SVA929 | RUH → FRA | Apr 24, 10:30 UTC | Apr 24, 11:05 UTC | 35m |
| 2026-04-23 | SVA929 | RUH → FRA | Apr 23, 14:45 UTC | Apr 24, 07:15 UTC | 16h 30m |
| 2026-04-23 | SVA3021 | HKG → HKG | Apr 23, 12:10 UTC | Apr 23, 12:25 UTC | 15m |
| 2026-04-23 | SVA3020 | RUH → HKG | Apr 23, 07:50 UTC | Apr 23, 08:35 UTC | 45m |
| 2026-04-23 | SVA3020 | RUH → HKG | Apr 23, 01:00 UTC | Apr 23, 06:05 UTC | 5h 5m |
| 2026-04-22 | SVA3020 | RUH → HKG | Apr 22, 08:05 UTC | Apr 23, 06:05 UTC | 22h 0m |
| 2026-04-22 | SVA932 | LGG → RUH | Apr 22, 06:40 UTC | Apr 23, 06:01 UTC | 23h 20m |
| 2026-04-21 | SVA931 | JED → LGG | Apr 21, 13:05 UTC | Apr 21, 16:50 UTC | 3h 45m |
| 2026-04-19 | SVA922 | BRU → JED | Apr 19, 10:10 UTC | Apr 19, 12:40 UTC | 2h 30m |
| 2026-04-19 | SVA921 | RUH → LGG | Apr 19, 02:15 UTC | Apr 19, 06:20 UTC | 4h 5m |
| 2026-04-13 | SVA3902 | JFK → BRU | Apr 13, 16:15 UTC | Apr 13, 17:20 UTC | 1h 5m |
| 2026-04-13 | SVA3902 | JFK → BRU | Apr 13, 15:50 UTC | Apr 13, 17:20 UTC | 1h 30m |
| 2026-04-13 | SVA3902 | JFK → BRU | Apr 13, 13:35 UTC | Apr 13, 16:15 UTC | 2h 40m |
| 2026-04-13 | SVA3902 | JFK → BRU | Apr 13, 08:45 UTC | Apr 13, 10:20 UTC | 1h 35m |
| 2026-04-13 | SVA3902 | JFK → BRU | Apr 13, 04:20 UTC | Apr 13, 05:35 UTC | 1h 15m |
| 2026-04-13 | SVA3902 | JFK → BRU | Apr 13, 03:55 UTC | Apr 13, 04:15 UTC | 20m |
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-AKK page for operator, model, and routing details .