sensors Mode-S transponder
710129
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-FAD · AIRBUS A-320
- Hex
- 710129
- Octal
- 34200451
- Decimal
- 7,405,865
- Country
- SA
- Tail
- HZ-FAD
- Type
- A320
- Flights observed
- 33
- Distinct callsigns
- 18
- Country
- SA
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 710129 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 18 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| FAD755 | Rog-Air | 6 | 2026-05-22 |
| FAD911 | - | 5 | 2026-07-13 |
| FAD461 | - | 4 | 2026-07-12 |
| FAD607 | Rog-Air | 3 | 2026-06-21 |
| FAD613 | Rog-Air | 2 | 2026-05-05 |
| FAD774 | Rog-Air | 1 | 2026-04-14 |
| FAD773 | Rog-Air | 1 | 2026-04-14 |
| FAD763 | Rog-Air | 1 | 2026-04-12 |
| FAD762 | Rog-Air | 1 | 2026-05-08 |
| FAD761 | Rog-Air | 1 | 2026-05-08 |
| FAD753 | Rog-Air | 1 | 2026-05-15 |
| FAD616 | - | 1 | 2026-06-26 |
| FAD615 | - | 1 | 2026-06-26 |
| FAD608 | Rog-Air | 1 | 2026-06-21 |
| FAD466 | Rog-Air | 1 | 2026-07-10 |
| FAD324 | Rog-Air | 1 | 2026-05-09 |
| FAD321 | - | 1 | 2026-07-07 |
| FAD186 | Rog-Air | 1 | 2026-04-19 |
Recent flights last 33
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | FAD911 | - | Jul 13, 05:55 UTC | Jul 13, 06:25 UTC | 30m |
| 2026-07-12 | FAD461 | - | Jul 12, 05:35 UTC | Jul 12, 05:45 UTC | 10m |
| 2026-07-10 | FAD466 | MED → DMM | Jul 10, 16:05 UTC | Jul 10, 22:15 UTC | 6h 11m |
| 2026-07-07 | FAD321 | - | Jul 7, 22:35 UTC | Jul 7, 22:45 UTC | 10m |
| 2026-06-26 | FAD616 | - | Jun 26, 23:39 UTC | Jun 27, 00:00 UTC | 20m |
| 2026-06-26 | FAD615 | - | Jun 26, 21:35 UTC | Jun 26, 22:05 UTC | 30m |
| 2026-06-21 | FAD608 | CAI → RUH | Jun 21, 13:04 UTC | Jun 21, 13:20 UTC | 15m |
| 2026-06-21 | FAD607 | RUH → CAI | Jun 21, 11:00 UTC | Jun 21, 11:20 UTC | 20m |
| 2026-06-19 | FAD607 | RUH → CAI | Jun 19, 10:44 UTC | Jun 19, 11:04 UTC | 20m |
| 2026-06-16 | FAD911 | - | Jun 16, 06:15 UTC | Jun 16, 06:35 UTC | 20m |
| 2026-06-14 | FAD461 | DMM → MED | Jun 14, 05:20 UTC | Jun 14, 16:50 UTC | 11h 30m |
| 2026-06-13 | FAD911 | - | Jun 13, 06:05 UTC | Jun 13, 06:30 UTC | 25m |
| 2026-06-11 | FAD461 | DMM → MED | Jun 11, 05:30 UTC | Jun 11, 05:40 UTC | 10m |
| 2026-06-09 | FAD911 | DMM → CAI | Jun 9, 06:15 UTC | Jun 9, 06:35 UTC | 20m |
| 2026-06-02 | FAD911 | DMM → CAI | Jun 2, 06:15 UTC | Jun 2, 06:35 UTC | 20m |
| 2026-06-01 | FAD461 | DMM → MED | Jun 1, 05:15 UTC | Jun 1, 05:30 UTC | 15m |
| 2026-05-22 | FAD755 | JED → CAI | May 22, 21:25 UTC | May 23, 07:10 UTC | 9h 44m |
| 2026-05-22 | FAD755 | JED → CAI | May 22, 06:45 UTC | May 22, 07:00 UTC | 15m |
| 2026-05-18 | FAD755 | JED → CAI | May 18, 06:50 UTC | May 18, 07:05 UTC | 15m |
| 2026-05-15 | FAD753 | JED → CAI | May 15, 05:10 UTC | May 15, 05:25 UTC | 15m |
| 2026-05-14 | FAD755 | JED → CAI | May 14, 06:50 UTC | May 14, 07:05 UTC | 15m |
| 2026-05-13 | FAD755 | JED → CAI | May 13, 07:25 UTC | May 13, 07:40 UTC | 15m |
| 2026-05-09 | FAD324 | DMM → JED | May 9, 23:20 UTC | May 9, 23:30 UTC | 10m |
| 2026-05-08 | FAD762 | CAI → JED | May 8, 19:55 UTC | May 8, 20:15 UTC | 20m |
| 2026-05-08 | FAD761 | JED → CAI | May 8, 17:45 UTC | May 8, 18:20 UTC | 35m |
| 2026-05-05 | FAD613 | RUH → CAI | May 5, 07:35 UTC | May 5, 08:00 UTC | 25m |
| 2026-04-28 | FAD613 | RUH → CAI | Apr 28, 07:30 UTC | Apr 28, 07:50 UTC | 20m |
| 2026-04-27 | FAD607 | RUH → CAI | Apr 27, 11:15 UTC | Apr 27, 11:40 UTC | 25m |
| 2026-04-19 | FAD186 | DMM → RUH | Apr 19, 18:35 UTC | Apr 19, 18:45 UTC | 10m |
| 2026-04-14 | FAD774 | ALY → JED | Apr 14, 07:25 UTC | Apr 14, 07:45 UTC | 20m |
| 2026-04-14 | FAD773 | JED → ALY | Apr 14, 05:30 UTC | Apr 14, 06:15 UTC | 45m |
| 2026-04-13 | FAD755 | - | Apr 13, 06:50 UTC | Apr 13, 07:05 UTC | 15m |
| 2026-04-12 | FAD763 | JED → CAI | Apr 12, 20:05 UTC | Apr 12, 20:15 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-FAD page for operator, model, and routing details .