sensors Mode-S transponder
7114F2
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-ASAJ · AIRBUS A-321neo
- Hex
- 7114F2
- Octal
- 34212362
- Decimal
- 7,410,930
- Country
- SA
- Tail
- HZ-ASAJ
- Type
- A21N
- Flights observed
- 163
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- Jul 26, 06:55 UTC
Last known position
Country allocation
The ICAO 24-bit address 7114F2 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 |
|---|---|---|---|
| SVA712 | Saudi Arabian Airlines | 8 | 2026-07-25 |
| SVA263 | - | 8 | 2026-06-21 |
| SVA315 | Saudi Arabian Airlines | 7 | 2026-06-06 |
| SVA713 | Saudi Arabian Airlines | 6 | 2026-07-26 |
| SVA261 | - | 6 | 2026-07-01 |
| SVA260 | - | 6 | 2026-07-20 |
| SVA252 | Saudi Arabian Airlines | 6 | 2026-06-06 |
| SVA380 | Saudi Arabian Airlines | 5 | 2026-06-18 |
| SVA3712 | Saudi Arabian Airlines | 5 | 2026-04-21 |
| SVA268 | - | 5 | 2026-07-15 |
| SVA267 | - | 5 | 2026-07-15 |
| SVA265 | - | 5 | 2026-07-01 |
| SVA251 | Saudi Arabian Airlines | 5 | 2026-06-06 |
| SVA319 | - | 4 | 2026-07-19 |
| SVA316 | Saudi Arabian Airlines | 4 | 2026-06-18 |
| SVA264 | Saudi Arabian Airlines | 4 | 2026-06-15 |
| SVA196 | - | 4 | 2026-07-10 |
| SVA318 | - | 3 | 2026-06-28 |
| SVA278 | Saudi Arabian Airlines | 3 | 2026-07-05 |
| SVA275 | - | 3 | 2026-07-05 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | SVA713 | CCJ → RUH | Jul 26, 05:45 UTC | Jul 26, 06:55 UTC | 1h 11m |
| 2026-07-25 | SVA712 | MED → KHI | Jul 25, 20:05 UTC | Jul 26, 04:00 UTC | 7h 55m |
| 2026-07-25 | SVA637 | RUH → AMM | Jul 25, 12:45 UTC | Jul 25, 18:35 UTC | 5h 50m |
| 2026-07-25 | SVA633 | RUH → AMM | Jul 25, 10:40 UTC | Jul 25, 11:10 UTC | 30m |
| 2026-07-24 | SVA206 | FCO → RUH | Jul 24, 07:15 UTC | Jul 24, 10:30 UTC | 3h 15m |
| 2026-07-24 | SVA209 | RUH → FCO | Jul 24, 01:35 UTC | Jul 24, 05:05 UTC | 3h 30m |
| 2026-07-23 | SVA208 | - | Jul 23, 15:00 UTC | Jul 23, 18:15 UTC | 3h 15m |
| 2026-07-23 | SVA207 | - | Jul 23, 08:50 UTC | Jul 23, 12:20 UTC | 3h 30m |
| 2026-07-22 | SVA334 | - | Jul 22, 19:50 UTC | Jul 22, 20:35 UTC | 45m |
| 2026-07-22 | SVA333 | - | Jul 22, 17:45 UTC | Jul 22, 18:30 UTC | 45m |
| 2026-07-22 | SVA537 | SLL → RUH | Jul 22, 13:35 UTC | Jul 22, 13:45 UTC | 10m |
| 2026-07-20 | SVA260 | - | Jul 20, 19:45 UTC | Jul 20, 21:35 UTC | 1h 50m |
| 2026-07-20 | SVA204 | - | Jul 20, 07:55 UTC | Jul 20, 17:40 UTC | 9h 45m |
| 2026-07-20 | SVA203 | JED → FCO | Jul 20, 02:05 UTC | Jul 20, 05:05 UTC | 3h 0m |
| 2026-07-19 | SVA319 | - | Jul 19, 12:05 UTC | Jul 19, 12:20 UTC | 15m |
| 2026-07-18 | SVA568 | - | Jul 18, 09:15 UTC | Jul 19, 04:20 UTC | 19h 5m |
| 2026-07-17 | SVA206 | - | Jul 17, 07:20 UTC | Jul 17, 09:50 UTC | 2h 30m |
| 2026-07-17 | SVA209 | - | Jul 17, 01:35 UTC | Jul 17, 04:49 UTC | 3h 15m |
| 2026-07-15 | SVA268 | - | Jul 15, 16:40 UTC | Jul 15, 18:40 UTC | 2h 0m |
| 2026-07-15 | SVA267 | - | Jul 15, 04:45 UTC | Jul 15, 14:20 UTC | 9h 35m |
| 2026-07-14 | SVA712 | - | Jul 14, 22:45 UTC | Jul 15, 02:45 UTC | 4h 0m |
| 2026-07-13 | SVA597 | - | Jul 13, 09:45 UTC | Jul 13, 10:35 UTC | 50m |
| 2026-07-13 | SVA596 | - | Jul 13, 06:50 UTC | Jul 13, 08:05 UTC | 1h 15m |
| 2026-07-10 | SVA196 | - | Jul 10, 14:30 UTC | Jul 10, 14:45 UTC | 15m |
| 2026-07-10 | SVA196 | - | Jul 10, 12:45 UTC | Jul 10, 14:25 UTC | 1h 40m |
| 2026-07-10 | SVA195 | - | Jul 10, 08:10 UTC | Jul 10, 10:30 UTC | 2h 20m |
| 2026-07-08 | SVA208 | FCO → RUH | Jul 8, 14:30 UTC | Jul 8, 17:55 UTC | 3h 25m |
| 2026-07-08 | SVA207 | - | Jul 8, 09:05 UTC | Jul 8, 12:15 UTC | 3h 10m |
| 2026-07-07 | SVA319 | - | Jul 7, 06:45 UTC | Jul 7, 12:30 UTC | 5h 45m |
| 2026-07-07 | SVA335 | - | Jul 7, 04:15 UTC | Jul 7, 04:30 UTC | 15m |
| 2026-07-05 | SVA278 | IST → JED | Jul 5, 15:40 UTC | Jul 5, 17:35 UTC | 1h 55m |
| 2026-07-05 | SVA275 | - | Jul 5, 11:40 UTC | Jul 5, 13:45 UTC | 2h 5m |
| 2026-07-04 | - | - | Jul 4, 18:30 UTC | Jul 4, 18:40 UTC | 10m |
| 2026-07-03 | SVA334 | - | Jul 3, 19:45 UTC | Jul 3, 20:25 UTC | 40m |
| 2026-07-03 | SVA272 | - | Jul 3, 10:55 UTC | Jul 3, 18:15 UTC | 7h 20m |
| 2026-07-03 | SVA273 | - | Jul 3, 07:20 UTC | Jul 3, 08:55 UTC | 1h 35m |
| 2026-07-02 | SVA273 | - | Jul 2, 12:35 UTC | Jul 3, 08:55 UTC | 20h 20m |
| 2026-07-02 | SVA273 | - | Jul 2, 11:40 UTC | Jul 3, 08:55 UTC | 21h 15m |
| 2026-07-01 | SVA260 | - | Jul 1, 19:40 UTC | Jul 2, 09:35 UTC | 13h 55m |
| 2026-07-01 | SVA261 | - | Jul 1, 09:05 UTC | Jul 1, 17:45 UTC | 8h 40m |
| 2026-07-01 | SVA265 | - | Jul 1, 05:25 UTC | Jul 1, 07:25 UTC | 2h 0m |
| 2026-06-29 | SVA196 | - | Jun 29, 12:49 UTC | Jun 29, 14:50 UTC | 2h 0m |
| 2026-06-29 | SVA195 | - | Jun 29, 08:44 UTC | Jun 29, 10:29 UTC | 1h 45m |
| 2026-06-28 | SVA318 | - | Jun 28, 06:40 UTC | Jun 28, 12:35 UTC | 5h 55m |
| 2026-06-27 | SVA260 | IST → JED | Jun 27, 19:34 UTC | Jun 28, 04:40 UTC | 9h 5m |
| 2026-06-27 | SVA261 | JED → IST | Jun 27, 15:39 UTC | Jun 27, 17:44 UTC | 2h 5m |
| 2026-06-24 | SVA1169 | DMM → RUH | Jun 24, 20:40 UTC | Jun 24, 20:54 UTC | 15m |
| 2026-06-24 | SVA1173 | DMM → RUH | Jun 24, 12:14 UTC | Jun 24, 12:25 UTC | 10m |
| 2026-06-24 | SVA1141 | - | Jun 24, 08:30 UTC | Jun 24, 08:39 UTC | 10m |
| 2026-06-23 | SVA1169 | DMM → RUH | Jun 23, 20:19 UTC | Jun 23, 20:34 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-ASAJ page for operator, model, and routing details .