sensors Mode-S transponder
7609D5
ICAO 24-bit transponder address · allocated to Pakistan
Currently assigned to AP-BNU · AIRBUS A-320
- Hex
- 7609D5
- Octal
- 35404725
- Decimal
- 7,735,765
- Country
- PK
- Tail
- AP-BNU
- Type
- A320
- Flights observed
- 71
- Distinct callsigns
- 20
- Country
- PK
- Last broadcast
- 23d ago
Last known position
Country allocation
The ICAO 24-bit address 7609D5 falls within the block assigned to Pakistan (PK) by ICAO Annex 10, Volume III. Every aircraft registered in Pakistan 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 |
|---|---|---|---|
| ABQ812 | Airblue | 10 | 2026-05-06 |
| ABQ813 | Airblue | 9 | 2026-05-04 |
| ABQ873 | Airblue | 8 | 2026-05-06 |
| ABQ817 | Airblue | 4 | 2026-05-02 |
| ABQ816 | Airblue | 4 | 2026-05-01 |
| ABQ811 | Airblue | 4 | 2026-04-29 |
| ABQ877 | Airblue | 3 | 2026-04-30 |
| ABQ876 | Airblue | 3 | 2026-04-30 |
| ABQ872 | Airblue | 3 | 2026-05-05 |
| ABQ810 | Airblue | 3 | 2026-04-28 |
| ABQ475 | Airblue | 3 | 2026-04-24 |
| ABQ474 | Airblue | 3 | 2026-04-24 |
| ABQ473 | Airblue | 3 | 2026-04-17 |
| ABQ479 | - | 2 | 2026-04-25 |
| ABQ478 | - | 2 | 2026-04-25 |
| ABQ416 | - | 2 | 2026-04-17 |
| ABQ472 | Airblue | 1 | 2026-04-16 |
| ABQ430 | Airblue | 1 | 2026-04-23 |
| ABQ417 | Airblue | 1 | 2026-04-17 |
| ABQ410 | Airblue | 1 | 2026-04-26 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-07 | ABQ171 | JED → KHI | May 7, 02:50 UTC | May 7, 03:10 UTC | 20m |
| 2026-05-06 | ABQ812 | MUX → SHJ | May 6, 09:35 UTC | May 6, 09:50 UTC | 15m |
| 2026-05-06 | ABQ873 | JED → MUX | May 6, 06:45 UTC | May 6, 06:55 UTC | 10m |
| 2026-05-06 | ABQ873 | JED → MUX | May 6, 03:55 UTC | May 6, 05:00 UTC | 1h 5m |
| 2026-05-05 | ABQ872 | MUX → JED | May 5, 20:01 UTC | May 5, 20:10 UTC | 10m |
| 2026-05-04 | ABQ813 | SHJ → MUX | May 4, 16:20 UTC | May 4, 16:30 UTC | 10m |
| 2026-05-04 | ABQ813 | SHJ → MUX | May 4, 14:10 UTC | May 4, 14:35 UTC | 25m |
| 2026-05-04 | ABQ812 | MUX → SHJ | May 4, 11:55 UTC | May 4, 12:20 UTC | 25m |
| 2026-05-04 | ABQ812 | MUX → SHJ | May 4, 09:45 UTC | May 4, 09:55 UTC | 10m |
| 2026-05-04 | ABQ873 | JED → MUX | May 4, 07:10 UTC | May 4, 07:20 UTC | 10m |
| 2026-05-04 | ABQ873 | JED → MUX | May 4, 04:24 UTC | May 4, 05:30 UTC | 1h 5m |
| 2026-05-03 | ABQ872 | MUX → JED | May 3, 20:05 UTC | May 3, 20:15 UTC | 10m |
| 2026-05-03 | ABQ813 | SHJ → MUX | May 3, 16:40 UTC | May 3, 16:55 UTC | 15m |
| 2026-05-03 | ABQ813 | SHJ → MUX | May 3, 14:25 UTC | May 3, 14:55 UTC | 30m |
| 2026-05-03 | ABQ812 | MUX → SHJ | May 3, 12:00 UTC | May 3, 12:25 UTC | 25m |
| 2026-05-03 | ABQ812 | MUX → SHJ | May 3, 09:45 UTC | May 3, 09:50 UTC | 5m |
| 2026-05-02 | ABQ817 | DXB → MUX | May 2, 03:35 UTC | May 2, 03:45 UTC | 10m |
| 2026-05-02 | ABQ817 | DXB → MUX | May 2, 01:35 UTC | May 2, 02:00 UTC | 25m |
| 2026-05-01 | ABQ816 | MUX → DXB | May 1, 23:00 UTC | May 1, 23:40 UTC | 40m |
| 2026-05-01 | ABQ816 | MUX → DXB | May 1, 20:55 UTC | May 1, 21:10 UTC | 15m |
| 2026-05-01 | ABQ813 | SHJ → MUX | May 1, 16:20 UTC | May 1, 16:30 UTC | 10m |
| 2026-05-01 | ABQ813 | SHJ → MUX | May 1, 14:20 UTC | May 1, 14:45 UTC | 25m |
| 2026-05-01 | ABQ812 | MUX → SHJ | May 1, 11:50 UTC | May 1, 12:10 UTC | 20m |
| 2026-05-01 | ABQ812 | MUX → SHJ | May 1, 09:35 UTC | May 1, 09:45 UTC | 10m |
| 2026-04-30 | ABQ877 | MED → MUX | Apr 30, 17:45 UTC | Apr 30, 17:55 UTC | 10m |
| 2026-04-30 | ABQ876 | MUX → MED | Apr 30, 09:35 UTC | Apr 30, 16:00 UTC | 6h 26m |
| 2026-04-30 | ABQ876 | MUX → MED | Apr 30, 07:25 UTC | Apr 30, 07:35 UTC | 10m |
| 2026-04-30 | ABQ817 | DXB → MUX | Apr 30, 04:15 UTC | Apr 30, 04:25 UTC | 10m |
| 2026-04-30 | ABQ817 | DXB → MUX | Apr 30, 02:10 UTC | Apr 30, 02:40 UTC | 30m |
| 2026-04-29 | ABQ816 | MUX → DXB | Apr 29, 23:40 UTC | Apr 30, 00:10 UTC | 30m |
| 2026-04-29 | ABQ816 | MUX → DXB | Apr 29, 21:35 UTC | Apr 29, 21:45 UTC | 10m |
| 2026-04-29 | ABQ811 | DXB → MUX | Apr 29, 04:20 UTC | Apr 29, 04:29 UTC | 10m |
| 2026-04-29 | ABQ811 | DXB → MUX | Apr 29, 02:15 UTC | Apr 29, 02:40 UTC | 25m |
| 2026-04-28 | ABQ810 | MUX → DXB | Apr 28, 23:20 UTC | Apr 28, 23:45 UTC | 25m |
| 2026-04-28 | ABQ810 | MUX → DXB | Apr 28, 21:05 UTC | Apr 28, 21:15 UTC | 10m |
| 2026-04-28 | ABQ877 | MED → MUX | Apr 28, 18:25 UTC | Apr 28, 18:35 UTC | 10m |
| 2026-04-28 | ABQ877 | MED → MUX | Apr 28, 09:35 UTC | Apr 28, 16:40 UTC | 7h 5m |
| 2026-04-28 | ABQ876 | MUX → MED | Apr 28, 07:25 UTC | Apr 28, 07:30 UTC | 5m |
| 2026-04-27 | ABQ813 | SHJ → MUX | Apr 27, 16:00 UTC | Apr 27, 16:20 UTC | 20m |
| 2026-04-27 | ABQ813 | SHJ → MUX | Apr 27, 13:55 UTC | Apr 27, 14:20 UTC | 25m |
| 2026-04-27 | ABQ812 | MUX → SHJ | Apr 27, 11:30 UTC | Apr 27, 12:05 UTC | 35m |
| 2026-04-27 | ABQ812 | MUX → SHJ | Apr 27, 09:30 UTC | Apr 27, 09:35 UTC | 5m |
| 2026-04-27 | ABQ811 | DXB → MUX | Apr 27, 01:50 UTC | Apr 27, 02:20 UTC | 30m |
| 2026-04-26 | ABQ410 | LHE → DXB | Apr 26, 23:50 UTC | Apr 27, 00:15 UTC | 25m |
| 2026-04-25 | ABQ479 | - | Apr 25, 23:30 UTC | Apr 26, 01:10 UTC | 1h 40m |
| 2026-04-25 | ABQ478 | - | Apr 25, 20:00 UTC | Apr 25, 21:30 UTC | 1h 30m |
| 2026-04-24 | ABQ478 | - | Apr 24, 23:45 UTC | Apr 25, 21:30 UTC | 21h 45m |
| 2026-04-24 | ABQ475 | RUH → LHE | Apr 24, 19:35 UTC | Apr 25, 00:50 UTC | 5h 15m |
| 2026-04-24 | ABQ475 | RUH → LHE | Apr 24, 01:20 UTC | Apr 25, 00:50 UTC | 23h 30m |
| 2026-04-24 | ABQ474 | LHE → RUH | Apr 24, 00:50 UTC | Apr 24, 20:45 UTC | 19h 55m |
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 AP-BNU page for operator, model, and routing details .