sensors Mode-S transponder
710138
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-AS65 · AIRBUS A-320
- Hex
- 710138
- Octal
- 34200470
- Decimal
- 7,405,880
- Country
- SA
- Tail
- HZ-AS65
- Type
- A320
- Flights observed
- 43
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 3h ago
Last known position
Country allocation
The ICAO 24-bit address 710138 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 |
|---|---|---|---|
| SVA632 | - | 3 | 2026-06-24 |
| SVA631 | - | 3 | 2026-07-19 |
| SVA638 | - | 2 | 2026-07-15 |
| SVA637 | - | 2 | 2026-07-15 |
| SVA635 | Saudi Arabian Airlines | 2 | 2026-06-30 |
| SVA634 | - | 2 | 2026-07-15 |
| SVA633 | - | 2 | 2026-07-15 |
| SVA627 | - | 2 | 2026-07-02 |
| SVA572 | - | 2 | 2026-07-08 |
| SVA9060 | - | 1 | 2026-06-19 |
| SVA628 | Saudi Arabian Airlines | 1 | 2026-06-05 |
| SVA593 | - | 1 | 2026-07-14 |
| SVA573 | - | 1 | 2026-07-08 |
| SVA569 | - | 1 | 2026-07-03 |
| SVA568 | - | 1 | 2026-07-03 |
| SVA541 | Saudi Arabian Airlines | 1 | 2026-07-14 |
| SVA411 | Saudi Arabian Airlines | 1 | 2026-06-12 |
| SVA410 | Saudi Arabian Airlines | 1 | 2026-06-12 |
| SVA241 | - | 1 | 2026-07-13 |
| SVA240 | - | 1 | 2026-07-13 |
Recent flights last 43
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-19 | SVA631 | - | Jul 19, 08:05 UTC | Jul 19, 08:25 UTC | 20m |
| 2026-07-17 | SVA1165 | - | Jul 17, 18:10 UTC | Jul 17, 18:25 UTC | 15m |
| 2026-07-17 | SVA1160 | - | Jul 17, 16:44 UTC | Jul 17, 16:55 UTC | 10m |
| 2026-07-15 | SVA638 | - | Jul 15, 19:20 UTC | Jul 15, 19:55 UTC | 35m |
| 2026-07-15 | SVA637 | - | Jul 15, 17:20 UTC | Jul 15, 17:55 UTC | 35m |
| 2026-07-15 | SVA634 | - | Jul 15, 12:35 UTC | Jul 15, 13:05 UTC | 30m |
| 2026-07-15 | SVA633 | - | Jul 15, 10:45 UTC | Jul 15, 11:20 UTC | 35m |
| 2026-07-14 | SVA541 | DOH → RUH | Jul 14, 12:15 UTC | Jul 15, 11:20 UTC | 23h 4m |
| 2026-07-14 | SVA593 | - | Jul 14, 01:30 UTC | Jul 14, 11:05 UTC | 9h 35m |
| 2026-07-13 | SVA240 | - | Jul 13, 15:55 UTC | Jul 13, 22:20 UTC | 6h 25m |
| 2026-07-13 | SVA241 | - | Jul 13, 12:25 UTC | Jul 13, 14:05 UTC | 1h 40m |
| 2026-07-10 | SVA1296 | - | Jul 10, 19:55 UTC | Jul 10, 20:10 UTC | 15m |
| 2026-07-10 | SVA1297 | - | Jul 10, 18:20 UTC | Jul 10, 18:30 UTC | 10m |
| 2026-07-08 | SVA1161 | - | Jul 8, 22:20 UTC | Jul 8, 22:30 UTC | 10m |
| 2026-07-08 | SVA573 | - | Jul 8, 11:45 UTC | Jul 8, 12:10 UTC | 25m |
| 2026-07-08 | SVA572 | - | Jul 8, 09:00 UTC | Jul 8, 10:00 UTC | 1h 0m |
| 2026-07-05 | SVA1290 | - | Jul 5, 12:00 UTC | Jul 5, 12:20 UTC | 20m |
| 2026-07-05 | SVA1291 | - | Jul 5, 10:30 UTC | Jul 5, 10:45 UTC | 15m |
| 2026-07-03 | SVA569 | - | Jul 3, 11:55 UTC | Jul 3, 12:50 UTC | 55m |
| 2026-07-03 | SVA568 | - | Jul 3, 01:20 UTC | Jul 3, 09:55 UTC | 8h 35m |
| 2026-07-02 | SVA627 | - | Jul 2, 23:25 UTC | Jul 2, 23:45 UTC | 20m |
| 2026-06-30 | SVA635 | JED → AMM | Jun 30, 16:15 UTC | Jun 30, 16:35 UTC | 20m |
| 2026-06-29 | SVA638 | - | Jun 29, 19:29 UTC | Jun 30, 16:35 UTC | 21h 5m |
| 2026-06-29 | SVA637 | - | Jun 29, 17:45 UTC | Jun 29, 18:05 UTC | 20m |
| 2026-06-29 | SVA634 | - | Jun 29, 12:39 UTC | Jun 29, 12:49 UTC | 10m |
| 2026-06-29 | SVA633 | - | Jun 29, 10:59 UTC | Jun 29, 11:10 UTC | 10m |
| 2026-06-24 | SVA632 | - | Jun 24, 10:39 UTC | Jun 24, 10:55 UTC | 15m |
| 2026-06-24 | SVA631 | - | Jun 24, 08:45 UTC | Jun 24, 08:55 UTC | 10m |
| 2026-06-19 | SVA9060 | - | Jun 19, 03:29 UTC | Jun 19, 04:39 UTC | 1h 10m |
| 2026-06-17 | SVA572 | - | Jun 17, 14:15 UTC | Jun 18, 09:30 UTC | 19h 15m |
| 2026-06-17 | SVA196 | - | Jun 17, 12:25 UTC | Jun 18, 09:30 UTC | 21h 5m |
| 2026-06-17 | SVA195 | - | Jun 17, 08:10 UTC | Jun 17, 10:15 UTC | 2h 5m |
| 2026-06-12 | SVA410 | HBE → JED | Jun 12, 17:40 UTC | Jun 12, 18:10 UTC | 30m |
| 2026-06-12 | SVA411 | JED → HBE | Jun 12, 07:30 UTC | Jun 12, 16:05 UTC | 8h 35m |
| 2026-06-05 | SVA632 | AMM → JED | Jun 5, 10:45 UTC | Jun 5, 11:05 UTC | 20m |
| 2026-06-05 | SVA628 | AMM → JED | Jun 5, 01:25 UTC | Jun 5, 09:00 UTC | 7h 35m |
| 2026-06-04 | SVA627 | JED → AMM | Jun 4, 17:50 UTC | Jun 4, 23:50 UTC | 6h 0m |
| 2026-06-04 | SVA635 | JED → AMM | Jun 4, 16:10 UTC | Jun 4, 16:20 UTC | 10m |
| 2026-06-04 | SVA632 | AMM → JED | Jun 4, 10:45 UTC | Jun 4, 11:05 UTC | 20m |
| 2026-06-04 | SVA631 | JED → AMM | Jun 4, 08:40 UTC | Jun 4, 08:55 UTC | 15m |
| 2026-05-13 | SVA1131 | DMM → RUH | May 13, 22:20 UTC | May 13, 22:30 UTC | 10m |
| 2026-04-13 | SVA1169 | - | Apr 13, 20:10 UTC | Apr 13, 20:20 UTC | 10m |
| 2026-04-13 | SVA1163 | - | Apr 13, 16:10 UTC | Apr 13, 16:20 UTC | 10m |
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-AS65 page for operator, model, and routing details .