sensors Mode-S transponder
71042E
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-AS84 · AIRBUS A-320
- Hex
- 71042E
- Octal
- 34202056
- Decimal
- 7,406,638
- Country
- SA
- Tail
- HZ-AS84
- Type
- A320
- Flights observed
- 36
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 4d ago
Last known position
Country allocation
The ICAO 24-bit address 71042E 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 |
|---|---|---|---|
| SVA570 | Saudi Arabian Airlines | 3 | 2026-05-15 |
| SVA634 | - | 2 | 2026-06-27 |
| SVA631 | - | 2 | 2026-07-09 |
| SVA573 | Saudi Arabian Airlines | 2 | 2026-06-12 |
| SVA571 | Saudi Arabian Airlines | 2 | 2026-04-28 |
| SVA1165 | Saudi Arabian Airlines | 2 | 2026-05-05 |
| SVA638 | - | 1 | 2026-06-27 |
| SVA637 | - | 1 | 2026-06-27 |
| SVA633 | - | 1 | 2026-06-27 |
| SVA632 | - | 1 | 2026-07-03 |
| SVA572 | Saudi Arabian Airlines | 1 | 2026-05-05 |
| SVA546 | Saudi Arabian Airlines | 1 | 2026-05-28 |
| SVA541 | Saudi Arabian Airlines | 1 | 2026-06-14 |
| SVA540 | Saudi Arabian Airlines | 1 | 2026-06-14 |
| SVA521 | Saudi Arabian Airlines | 1 | 2026-06-20 |
| SVA520 | - | 1 | 2026-06-20 |
| SVA410 | Saudi Arabian Airlines | 1 | 2026-04-23 |
| SVA266 | Saudi Arabian Airlines | 1 | 2026-04-23 |
| SVA265 | Saudi Arabian Airlines | 1 | 2026-04-23 |
| SVA261 | - | 1 | 2026-07-09 |
Recent flights last 36
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-09 | SVA260 | - | Jul 9, 19:35 UTC | Jul 9, 21:15 UTC | 1h 40m |
| 2026-07-09 | SVA261 | - | Jul 9, 10:45 UTC | Jul 9, 17:30 UTC | 6h 45m |
| 2026-07-09 | SVA631 | - | Jul 9, 08:55 UTC | Jul 9, 09:20 UTC | 25m |
| 2026-07-03 | SVA632 | - | Jul 3, 10:40 UTC | Jul 3, 10:50 UTC | 10m |
| 2026-07-03 | SVA631 | - | Jul 3, 08:40 UTC | Jul 3, 09:00 UTC | 20m |
| 2026-06-27 | SVA638 | - | Jun 27, 19:29 UTC | Jun 27, 19:39 UTC | 10m |
| 2026-06-27 | SVA637 | - | Jun 27, 17:39 UTC | Jun 27, 17:59 UTC | 20m |
| 2026-06-27 | SVA634 | - | Jun 27, 12:45 UTC | Jun 27, 12:55 UTC | 10m |
| 2026-06-27 | SVA633 | - | Jun 27, 10:50 UTC | Jun 27, 11:09 UTC | 20m |
| 2026-06-25 | SVA1167 | - | Jun 25, 02:05 UTC | Jun 25, 02:19 UTC | 15m |
| 2026-06-20 | SVA521 | BAH → RUH | Jun 20, 15:04 UTC | Jun 20, 15:19 UTC | 15m |
| 2026-06-20 | SVA520 | - | Jun 20, 13:19 UTC | Jun 20, 13:29 UTC | 10m |
| 2026-06-19 | SVA634 | AMM → RUH | Jun 19, 12:49 UTC | Jun 19, 13:04 UTC | 15m |
| 2026-06-18 | - | - | Jun 18, 04:05 UTC | Jun 18, 04:20 UTC | 15m |
| 2026-06-14 | SVA541 | DOH → RUH | Jun 14, 12:10 UTC | Jun 14, 12:50 UTC | 40m |
| 2026-06-14 | SVA540 | RUH → DOH | Jun 14, 10:15 UTC | Jun 14, 11:00 UTC | 45m |
| 2026-06-12 | SVA573 | AUH → RUH | Jun 12, 12:00 UTC | Jun 12, 12:20 UTC | 20m |
| 2026-06-05 | SVA196 | - | Jun 5, 12:35 UTC | Jun 5, 13:40 UTC | 1h 5m |
| 2026-06-05 | SVA195 | - | Jun 5, 08:45 UTC | Jun 5, 10:20 UTC | 1h 35m |
| 2026-06-04 | SVA1127 | DMM → JED | Jun 4, 01:30 UTC | Jun 4, 01:40 UTC | 10m |
| 2026-05-28 | SVA546 | JED → DOH | May 28, 11:00 UTC | May 28, 11:40 UTC | 40m |
| 2026-05-15 | SVA570 | RUH → AUH | May 15, 11:05 UTC | May 15, 11:35 UTC | 30m |
| 2026-05-09 | SVA1113 | DMM → JED | May 9, 11:35 UTC | May 9, 11:45 UTC | 10m |
| 2026-05-05 | SVA1165 | DMM → RUH | May 5, 18:20 UTC | May 5, 18:30 UTC | 10m |
| 2026-05-05 | SVA573 | AUH → RUH | May 5, 12:40 UTC | May 5, 13:35 UTC | 55m |
| 2026-05-05 | SVA572 | JED → AUH | May 5, 10:00 UTC | May 5, 10:30 UTC | 30m |
| 2026-04-28 | SVA571 | AUH → JED | Apr 28, 12:50 UTC | Apr 28, 13:45 UTC | 55m |
| 2026-04-28 | SVA570 | RUH → AUH | Apr 28, 10:05 UTC | Apr 28, 10:55 UTC | 50m |
| 2026-04-25 | SVA1105 | DMM → JED | Apr 25, 03:35 UTC | Apr 25, 03:45 UTC | 10m |
| 2026-04-23 | SVA410 | HBE → JED | Apr 23, 17:40 UTC | Apr 23, 18:05 UTC | 25m |
| 2026-04-23 | SVA266 | IST → JED | Apr 23, 09:15 UTC | Apr 23, 16:25 UTC | 7h 10m |
| 2026-04-23 | SVA265 | JED → IST | Apr 23, 05:55 UTC | Apr 23, 07:35 UTC | 1h 40m |
| 2026-04-17 | SVA1109 | DMM → JED | Apr 17, 09:20 UTC | Apr 17, 09:30 UTC | 10m |
| 2026-04-14 | SVA1165 | - | Apr 14, 18:10 UTC | Apr 14, 18:25 UTC | 15m |
| 2026-04-13 | SVA571 | - | Apr 13, 12:55 UTC | Apr 13, 13:55 UTC | 1h 0m |
| 2026-04-13 | SVA570 | RUH → AUH | Apr 13, 10:10 UTC | Apr 13, 11:15 UTC | 1h 5m |
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-AS84 page for operator, model, and routing details .