sensors Mode-S transponder
7114EF
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-ASAL · AIRBUS A-321neo
- Hex
- 7114EF
- Octal
- 34212357
- Decimal
- 7,410,927
- Country
- SA
- Tail
- HZ-ASAL
- Type
- A21N
- Flights observed
- 118
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 3h ago
Last known position
Country allocation
The ICAO 24-bit address 7114EF falls within the block assigned to Saudi Arabia (SA) by ICAO Annex 10, Volume III. Every aircraft registered in Saudi Arabia 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 |
|---|---|---|---|
| SVA259 | - | 11 | 2026-06-14 |
| SVA261 | - | 9 | 2026-07-13 |
| SVA713 | Saudi Arabian Airlines | 7 | 2026-05-16 |
| SVA258 | Saudi Arabian Airlines | 7 | 2026-06-14 |
| SVA275 | - | 6 | 2026-07-03 |
| SVA265 | - | 6 | 2026-07-13 |
| SVA260 | - | 6 | 2026-07-13 |
| SVA380 | - | 5 | 2026-06-22 |
| SVA263 | Saudi Arabian Airlines | 5 | 2026-05-29 |
| SVA267 | Saudi Arabian Airlines | 4 | 2026-07-06 |
| SVA264 | Saudi Arabian Airlines | 4 | 2026-05-29 |
| SVA167 | Saudi Arabian Airlines | 4 | 2026-06-04 |
| SVA391 | Saudi Arabian Airlines | 3 | 2026-06-07 |
| SVA266 | Saudi Arabian Airlines | 3 | 2026-04-25 |
| SVA195 | - | 3 | 2026-07-05 |
| SVA712 | Saudi Arabian Airlines | 2 | 2026-05-10 |
| SVA589 | Saudi Arabian Airlines | 2 | 2026-06-17 |
| SVA568 | - | 2 | 2026-06-28 |
| SVA318 | - | 2 | 2026-06-19 |
| SVA317 | Saudi Arabian Airlines | 2 | 2026-06-22 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | SVA332 | - | Jul 14, 08:45 UTC | Jul 14, 09:15 UTC | 30m |
| 2026-07-13 | SVA260 | - | Jul 13, 19:50 UTC | Jul 14, 07:15 UTC | 11h 25m |
| 2026-07-13 | SVA261 | - | Jul 13, 09:05 UTC | Jul 13, 18:00 UTC | 8h 55m |
| 2026-07-13 | SVA265 | - | Jul 13, 05:20 UTC | Jul 13, 07:20 UTC | 2h 0m |
| 2026-07-10 | SVA260 | - | Jul 10, 19:50 UTC | Jul 10, 21:35 UTC | 1h 45m |
| 2026-07-10 | SVA261 | - | Jul 10, 07:50 UTC | Jul 10, 17:45 UTC | 9h 55m |
| 2026-07-09 | SVA202 | - | Jul 9, 14:35 UTC | Jul 10, 04:40 UTC | 14h 5m |
| 2026-07-08 | SVA201 | - | Jul 8, 19:55 UTC | Jul 9, 12:20 UTC | 16h 25m |
| 2026-07-08 | SVA261 | - | Jul 8, 16:05 UTC | Jul 8, 18:10 UTC | 2h 5m |
| 2026-07-07 | SVA261 | - | Jul 7, 19:50 UTC | Jul 8, 18:10 UTC | 22h 20m |
| 2026-07-07 | SVA261 | - | Jul 7, 16:00 UTC | Jul 7, 17:55 UTC | 1h 55m |
| 2026-07-06 | SVA261 | - | Jul 6, 17:50 UTC | Jul 7, 17:45 UTC | 23h 55m |
| 2026-07-06 | SVA268 | IST → JED | Jul 6, 16:55 UTC | Jul 6, 18:50 UTC | 1h 55m |
| 2026-07-06 | SVA267 | RUH → IST | Jul 6, 04:55 UTC | Jul 6, 14:25 UTC | 9h 30m |
| 2026-07-05 | SVA196 | - | Jul 5, 12:35 UTC | Jul 6, 01:35 UTC | 13h 0m |
| 2026-07-05 | SVA195 | - | Jul 5, 08:30 UTC | Jul 5, 10:20 UTC | 1h 50m |
| 2026-07-04 | SVA195 | ATH → ATH | Jul 4, 12:45 UTC | Jul 5, 10:20 UTC | 21h 35m |
| 2026-07-04 | SVA191 | - | Jul 4, 08:35 UTC | Jul 4, 10:30 UTC | 1h 55m |
| 2026-07-03 | SVA278 | IST → JED | Jul 3, 15:45 UTC | Jul 3, 17:30 UTC | 1h 45m |
| 2026-07-03 | SVA275 | - | Jul 3, 11:50 UTC | Jul 3, 13:55 UTC | 2h 5m |
| 2026-07-02 | SVA275 | - | Jul 2, 15:50 UTC | Jul 3, 13:55 UTC | 22h 5m |
| 2026-07-02 | SVA275 | - | Jul 2, 11:40 UTC | Jul 2, 13:35 UTC | 1h 55m |
| 2026-07-01 | SVA275 | - | Jul 1, 15:50 UTC | Jul 2, 13:35 UTC | 21h 45m |
| 2026-07-01 | SVA278 | IST → JED | Jul 1, 15:35 UTC | Jul 2, 13:35 UTC | 22h 0m |
| 2026-07-01 | SVA275 | - | Jul 1, 11:40 UTC | Jul 1, 13:35 UTC | 1h 55m |
| 2026-06-30 | SVA275 | - | Jun 30, 15:40 UTC | Jul 1, 13:35 UTC | 21h 55m |
| 2026-06-29 | SVA260 | - | Jun 29, 19:39 UTC | Jun 30, 13:35 UTC | 17h 55m |
| 2026-06-29 | SVA261 | - | Jun 29, 15:39 UTC | Jun 29, 17:34 UTC | 1h 55m |
| 2026-06-28 | SVA569 | DXB → JED | Jun 28, 11:50 UTC | Jun 28, 12:44 UTC | 55m |
| 2026-06-28 | SVA568 | - | Jun 28, 08:55 UTC | Jun 28, 10:04 UTC | 1h 10m |
| 2026-06-24 | SVA319 | MED → CAI | Jun 24, 02:54 UTC | Jun 24, 12:30 UTC | 9h 35m |
| 2026-06-22 | SVA380 | - | Jun 22, 19:00 UTC | Jun 23, 06:19 UTC | 11h 20m |
| 2026-06-22 | SVA381 | MED → CAI | Jun 22, 08:15 UTC | Jun 22, 17:25 UTC | 9h 10m |
| 2026-06-22 | SVA317 | MED → CAI | Jun 22, 06:05 UTC | Jun 22, 06:19 UTC | 15m |
| 2026-06-20 | SVA317 | MED → CAI | Jun 20, 06:05 UTC | Jun 20, 11:49 UTC | 5h 45m |
| 2026-06-19 | SVA318 | - | Jun 19, 06:49 UTC | Jun 19, 07:04 UTC | 15m |
| 2026-06-18 | SVA1124 | - | Jun 18, 17:50 UTC | Jun 18, 18:05 UTC | 15m |
| 2026-06-17 | SVA589 | DXB → JED | Jun 17, 13:40 UTC | Jun 17, 14:35 UTC | 55m |
| 2026-06-14 | SVA380 | CAI → MED | Jun 14, 18:25 UTC | Jun 14, 18:40 UTC | 15m |
| 2026-06-14 | SVA258 | IST → MED | Jun 14, 10:40 UTC | Jun 14, 16:25 UTC | 5h 45m |
| 2026-06-14 | SVA259 | - | Jun 14, 07:05 UTC | Jun 14, 09:10 UTC | 2h 5m |
| 2026-06-13 | SVA259 | - | Jun 13, 11:50 UTC | Jun 14, 09:10 UTC | 21h 20m |
| 2026-06-13 | SVA259 | - | Jun 13, 10:50 UTC | Jun 14, 09:10 UTC | 22h 20m |
| 2026-06-12 | SVA259 | - | Jun 12, 18:30 UTC | Jun 13, 09:20 UTC | 14h 49m |
| 2026-06-12 | SVA258 | IST → MED | Jun 12, 10:35 UTC | Jun 12, 16:25 UTC | 5h 50m |
| 2026-06-12 | SVA259 | - | Jun 12, 06:50 UTC | Jun 12, 09:00 UTC | 2h 10m |
| 2026-06-07 | SVA380 | CAI → MED | Jun 7, 18:50 UTC | Jun 8, 12:40 UTC | 17h 50m |
| 2026-06-07 | SVA258 | IST → MED | Jun 7, 10:50 UTC | Jun 7, 17:10 UTC | 6h 20m |
| 2026-06-07 | SVA259 | MED → IST | Jun 7, 03:20 UTC | Jun 7, 09:15 UTC | 5h 55m |
| 2026-06-07 | SVA391 | MED → CAI | Jun 7, 01:20 UTC | Jun 7, 01:35 UTC | 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 HZ-ASAL page for operator, model, and routing details .