sensors Mode-S transponder
71145E
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-FBR · AIRBUS A-320neo
- Hex
- 71145E
- Octal
- 34212136
- Decimal
- 7,410,782
- Country
- SA
- Tail
- HZ-FBR
- Type
- A20N
- Flights observed
- 75
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 6d ago
Last known position
Country allocation
The ICAO 24-bit address 71145E 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 |
|---|---|---|---|
| FAD574 | - | 7 | 2026-07-07 |
| FAD573 | Rog-Air | 7 | 2026-07-07 |
| FAD771 | Rog-Air | 6 | 2026-06-13 |
| FAD661 | - | 4 | 2026-07-08 |
| FAD605 | - | 4 | 2026-06-26 |
| FAD811 | Rog-Air | 3 | 2026-04-19 |
| FAD772 | Rog-Air | 3 | 2026-06-13 |
| FAD665 | - | 3 | 2026-07-04 |
| FAD656 | - | 3 | 2026-07-10 |
| FAD653 | - | 3 | 2026-07-06 |
| FAD591 | - | 3 | 2026-07-04 |
| FAD812 | - | 2 | 2026-04-15 |
| FAD655 | - | 2 | 2026-07-10 |
| FAD651 | Rog-Air | 2 | 2026-06-04 |
| FAD616 | - | 2 | 2026-07-11 |
| FAD615 | - | 2 | 2026-07-11 |
| FAD607 | Rog-Air | 2 | 2026-05-21 |
| FAD511 | - | 2 | 2026-06-28 |
| FAD505 | - | 2 | 2026-06-30 |
| FAD776 | - | 1 | 2026-04-19 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-11 | FAD616 | - | Jul 11, 23:30 UTC | Jul 12, 00:10 UTC | 40m |
| 2026-07-11 | FAD615 | - | Jul 11, 14:25 UTC | Jul 11, 22:20 UTC | 7h 55m |
| 2026-07-11 | FAD543 | - | Jul 11, 11:30 UTC | Jul 11, 11:55 UTC | 25m |
| 2026-07-10 | FAD656 | - | Jul 10, 11:35 UTC | Jul 11, 11:30 UTC | 23h 56m |
| 2026-07-10 | FAD656 | - | Jul 10, 08:55 UTC | Jul 10, 12:15 UTC | 3h 20m |
| 2026-07-10 | FAD655 | - | Jul 10, 03:45 UTC | Jul 10, 06:50 UTC | 3h 5m |
| 2026-07-08 | FAD661 | - | Jul 8, 23:15 UTC | Jul 9, 05:30 UTC | 6h 15m |
| 2026-07-08 | FAD506 | - | Jul 8, 09:40 UTC | Jul 8, 10:25 UTC | 45m |
| 2026-07-07 | FAD574 | - | Jul 7, 18:05 UTC | Jul 8, 08:20 UTC | 14h 15m |
| 2026-07-07 | FAD573 | RUH → IST | Jul 7, 03:35 UTC | Jul 7, 16:20 UTC | 12h 45m |
| 2026-07-06 | FAD653 | - | Jul 6, 22:05 UTC | Jul 7, 01:20 UTC | 3h 15m |
| 2026-07-05 | FAD592 | - | Jul 5, 20:25 UTC | Jul 5, 23:00 UTC | 2h 35m |
| 2026-07-04 | FAD591 | - | Jul 4, 23:35 UTC | Jul 5, 18:40 UTC | 19h 5m |
| 2026-07-04 | FAD591 | - | Jul 4, 21:35 UTC | Jul 5, 18:40 UTC | 21h 5m |
| 2026-07-04 | FAD591 | - | Jul 4, 20:55 UTC | Jul 5, 18:40 UTC | 21h 45m |
| 2026-07-04 | FAD665 | - | Jul 4, 05:35 UTC | Jul 5, 05:30 UTC | 23h 55m |
| 2026-07-04 | FAD665 | - | Jul 4, 04:35 UTC | Jul 5, 03:30 UTC | 22h 55m |
| 2026-07-03 | FAD665 | - | Jul 3, 23:35 UTC | Jul 4, 23:30 UTC | 23h 55m |
| 2026-07-03 | FAD661 | - | Jul 3, 23:05 UTC | Jul 4, 21:30 UTC | 22h 25m |
| 2026-07-02 | FAD574 | - | Jul 2, 18:15 UTC | Jul 2, 20:10 UTC | 1h 55m |
| 2026-07-02 | FAD573 | RUH → IST | Jul 2, 09:05 UTC | Jul 2, 16:05 UTC | 7h 0m |
| 2026-07-01 | FAD574 | - | Jul 1, 18:10 UTC | Jul 2, 07:45 UTC | 13h 35m |
| 2026-07-01 | FAD573 | RUH → IST | Jul 1, 09:05 UTC | Jul 1, 16:05 UTC | 7h 0m |
| 2026-06-30 | FAD574 | - | Jun 30, 18:05 UTC | Jul 1, 08:00 UTC | 13h 55m |
| 2026-06-30 | FAD573 | RUH → IST | Jun 30, 09:15 UTC | Jun 30, 16:00 UTC | 6h 45m |
| 2026-06-30 | FAD505 | - | Jun 30, 06:35 UTC | Jun 30, 07:55 UTC | 1h 20m |
| 2026-06-29 | FAD656 | - | Jun 29, 02:45 UTC | Jun 29, 06:05 UTC | 3h 20m |
| 2026-06-28 | FAD655 | - | Jun 28, 18:05 UTC | Jun 29, 01:00 UTC | 6h 55m |
| 2026-06-28 | FAD511 | - | Jun 28, 15:09 UTC | Jun 28, 16:35 UTC | 1h 25m |
| 2026-06-27 | FAD511 | - | Jun 27, 19:34 UTC | Jun 28, 16:35 UTC | 21h 0m |
| 2026-06-27 | FAD574 | - | Jun 27, 18:39 UTC | Jun 28, 16:35 UTC | 21h 55m |
| 2026-06-27 | FAD573 | RUH → IST | Jun 27, 03:09 UTC | Jun 27, 16:30 UTC | 13h 20m |
| 2026-06-26 | FAD653 | - | Jun 26, 10:55 UTC | Jun 27, 01:19 UTC | 14h 25m |
| 2026-06-26 | FAD605 | - | Jun 26, 09:05 UTC | Jun 26, 09:24 UTC | 20m |
| 2026-06-20 | FAD574 | - | Jun 20, 18:14 UTC | Jun 20, 20:14 UTC | 2h 0m |
| 2026-06-20 | FAD573 | RUH → IST | Jun 20, 09:09 UTC | Jun 20, 16:00 UTC | 6h 50m |
| 2026-06-20 | FAD505 | - | Jun 20, 06:19 UTC | Jun 20, 07:39 UTC | 1h 20m |
| 2026-06-13 | FAD428 | HOF → MED | Jun 13, 18:25 UTC | Jun 13, 18:45 UTC | 20m |
| 2026-06-13 | FAD427 | MED → HOF | Jun 13, 17:10 UTC | Jun 13, 17:25 UTC | 15m |
| 2026-06-13 | FAD772 | CAI → MED | Jun 13, 07:25 UTC | Jun 13, 07:40 UTC | 15m |
| 2026-06-13 | FAD771 | MED → CAI | Jun 13, 05:10 UTC | Jun 13, 05:30 UTC | 20m |
| 2026-06-12 | FAD771 | MED → CAI | Jun 12, 07:15 UTC | Jun 13, 05:30 UTC | 22h 14m |
| 2026-06-12 | FAD771 | MED → CAI | Jun 12, 05:05 UTC | Jun 12, 05:25 UTC | 20m |
| 2026-06-11 | FAD771 | MED → CAI | Jun 11, 07:35 UTC | Jun 12, 05:25 UTC | 21h 51m |
| 2026-06-11 | FAD771 | MED → CAI | Jun 11, 07:25 UTC | Jun 12, 05:25 UTC | 22h 1m |
| 2026-06-11 | FAD771 | MED → CAI | Jun 11, 05:15 UTC | Jun 11, 05:40 UTC | 25m |
| 2026-06-08 | FAD772 | CAI → MED | Jun 8, 07:25 UTC | Jun 8, 07:35 UTC | 10m |
| 2026-06-04 | FAD651 | RUH → ISB | Jun 4, 21:35 UTC | Jun 5, 06:15 UTC | 8h 40m |
| 2026-06-02 | FAD616 | CAI → RUH | Jun 2, 00:00 UTC | Jun 2, 00:15 UTC | 15m |
| 2026-06-01 | FAD615 | RUH → CAI | Jun 1, 13:05 UTC | Jun 1, 22:35 UTC | 9h 30m |
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-FBR page for operator, model, and routing details .