sensors Mode-S transponder
711105
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-FAS · AIRBUS A-320neo
- Hex
- 711105
- Octal
- 34210405
- Decimal
- 7,409,925
- Country
- SA
- Tail
- HZ-FAS
- Type
- A20N
- Flights observed
- 41
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address 711105 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 |
|---|---|---|---|
| FAD513 | - | 4 | 2026-07-06 |
| FAD613 | - | 3 | 2026-07-11 |
| FAD762 | Rog-Air | 2 | 2026-04-22 |
| FAD755 | Rog-Air | 2 | 2026-04-24 |
| FAD616 | - | 2 | 2026-06-30 |
| FAD615 | - | 2 | 2026-06-30 |
| FAD514 | - | 2 | 2026-07-06 |
| FAD505 | Rog-Air | 2 | 2026-04-27 |
| FAD761 | Rog-Air | 1 | 2026-04-22 |
| FAD756 | Rog-Air | 1 | 2026-04-21 |
| FAD754 | - | 1 | 2026-06-21 |
| FAD753 | - | 1 | 2026-06-21 |
| FAD742 | - | 1 | 2026-06-23 |
| FAD741 | - | 1 | 2026-06-22 |
| FAD614 | - | 1 | 2026-07-11 |
| FAD607 | - | 1 | 2026-07-10 |
| FAD606 | Rog-Air | 1 | 2026-05-09 |
| FAD605 | Rog-Air | 1 | 2026-05-09 |
| FAD578 | - | 1 | 2026-07-12 |
| FAD577 | - | 1 | 2026-07-11 |
Recent flights last 41
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-12 | FAD578 | - | Jul 12, 09:20 UTC | Jul 12, 10:55 UTC | 1h 35m |
| 2026-07-11 | FAD577 | - | Jul 11, 16:35 UTC | Jul 12, 07:55 UTC | 15h 20m |
| 2026-07-11 | FAD259 | - | Jul 11, 14:55 UTC | Jul 11, 15:05 UTC | 10m |
| 2026-07-11 | FAD614 | - | Jul 11, 09:30 UTC | Jul 11, 09:40 UTC | 10m |
| 2026-07-11 | FAD613 | - | Jul 11, 07:25 UTC | Jul 11, 07:50 UTC | 25m |
| 2026-07-10 | FAD613 | - | Jul 10, 13:00 UTC | Jul 11, 07:50 UTC | 18h 50m |
| 2026-07-10 | FAD607 | - | Jul 10, 10:50 UTC | Jul 10, 11:10 UTC | 20m |
| 2026-07-07 | FAD562 | - | Jul 7, 10:25 UTC | Jul 7, 11:00 UTC | 35m |
| 2026-07-06 | FAD514 | - | Jul 6, 20:00 UTC | Jul 7, 08:55 UTC | 12h 55m |
| 2026-07-06 | FAD513 | - | Jul 6, 10:30 UTC | Jul 6, 18:15 UTC | 7h 45m |
| 2026-07-06 | FAD561 | - | Jul 6, 08:25 UTC | Jul 6, 08:50 UTC | 25m |
| 2026-07-04 | FAD514 | - | Jul 4, 19:40 UTC | Jul 4, 20:35 UTC | 55m |
| 2026-07-04 | FAD513 | - | Jul 4, 16:40 UTC | Jul 4, 18:00 UTC | 1h 20m |
| 2026-07-03 | FAD513 | - | Jul 3, 19:20 UTC | Jul 4, 18:00 UTC | 22h 40m |
| 2026-07-03 | FAD513 | - | Jul 3, 11:35 UTC | Jul 3, 17:50 UTC | 6h 15m |
| 2026-07-02 | FAD512 | - | Jul 2, 18:00 UTC | Jul 3, 09:35 UTC | 15h 35m |
| 2026-07-02 | FAD511 | - | Jul 2, 15:20 UTC | Jul 2, 16:45 UTC | 1h 25m |
| 2026-06-30 | FAD616 | - | Jun 30, 23:35 UTC | Jun 30, 23:55 UTC | 20m |
| 2026-06-30 | FAD615 | - | Jun 30, 21:30 UTC | Jun 30, 22:10 UTC | 40m |
| 2026-06-24 | FAD616 | - | Jun 24, 23:40 UTC | Jun 24, 23:59 UTC | 20m |
| 2026-06-24 | FAD615 | - | Jun 24, 22:00 UTC | Jun 24, 22:29 UTC | 30m |
| 2026-06-23 | FAD742 | - | Jun 23, 07:55 UTC | Jun 23, 08:20 UTC | 25m |
| 2026-06-22 | FAD741 | - | Jun 22, 18:44 UTC | Jun 23, 06:24 UTC | 11h 40m |
| 2026-06-21 | FAD754 | - | Jun 21, 07:00 UTC | Jun 21, 07:14 UTC | 15m |
| 2026-06-21 | FAD753 | - | Jun 21, 05:00 UTC | Jun 21, 05:30 UTC | 30m |
| 2026-06-19 | FAD317 | JED → DMM | Jun 19, 17:04 UTC | Jun 19, 17:19 UTC | 15m |
| 2026-06-18 | FAD430 | - | Jun 18, 09:55 UTC | Jun 18, 10:10 UTC | 15m |
| 2026-05-09 | FAD606 | CAI → RUH | May 9, 11:30 UTC | May 9, 11:40 UTC | 10m |
| 2026-05-09 | FAD605 | RUH → CAI | May 9, 09:15 UTC | May 9, 09:50 UTC | 35m |
| 2026-04-27 | FAD506 | DXB → RUH | Apr 27, 09:25 UTC | Apr 27, 10:30 UTC | 1h 5m |
| 2026-04-27 | FAD505 | RUH → DXB | Apr 27, 06:35 UTC | Apr 27, 07:45 UTC | 1h 10m |
| 2026-04-26 | FAD505 | RUH → DXB | Apr 26, 10:05 UTC | Apr 27, 07:45 UTC | 21h 40m |
| 2026-04-26 | FAD613 | RUH → CAI | Apr 26, 08:00 UTC | Apr 26, 08:25 UTC | 25m |
| 2026-04-24 | FAD755 | JED → CAI | Apr 24, 06:45 UTC | Apr 24, 07:00 UTC | 15m |
| 2026-04-22 | FAD762 | CAI → JED | Apr 22, 19:10 UTC | Apr 22, 19:25 UTC | 15m |
| 2026-04-22 | FAD761 | JED → CAI | Apr 22, 08:05 UTC | Apr 22, 17:40 UTC | 9h 35m |
| 2026-04-21 | FAD756 | CAI → JED | Apr 21, 09:05 UTC | Apr 21, 09:15 UTC | 10m |
| 2026-04-21 | FAD755 | JED → CAI | Apr 21, 06:50 UTC | Apr 21, 07:05 UTC | 15m |
| 2026-04-20 | FAD318 | DMM → JED | Apr 20, 18:40 UTC | Apr 20, 18:50 UTC | 10m |
| 2026-04-13 | FAD310 | - | Apr 13, 12:55 UTC | Apr 13, 13:10 UTC | 15m |
| 2026-04-12 | FAD762 | CAI → JED | Apr 12, 19:00 UTC | Apr 12, 19:15 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-FAS page for operator, model, and routing details .