sensors Mode-S transponder
761487
ICAO 24-bit transponder address · allocated to Pakistan
Currently assigned to AP-EDG · AIRBUS A-320
- Hex
- 761487
- Octal
- 35412207
- Decimal
- 7,738,503
- Country
- PK
- Tail
- AP-EDG
- Type
- A320
- Flights observed
- 75
- Distinct callsigns
- 20
- Country
- PK
- Last broadcast
- 2h ago
Last known position
Country allocation
The ICAO 24-bit address 761487 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 |
|---|---|---|---|
| ABQ475 | Airblue | 10 | 2026-05-15 |
| ABQ416 | Airblue | 8 | 2026-05-05 |
| ABQ478 | - | 6 | 2026-05-28 |
| ABQ4761 | - | 6 | 2026-05-04 |
| ABQ473 | Airblue | 6 | 2026-05-24 |
| ABQ479 | - | 5 | 2026-05-28 |
| ABQ417 | Airblue | 5 | 2026-04-30 |
| ABQ405 | Airblue | 5 | 2026-05-24 |
| ABQ474 | Airblue | 4 | 2026-05-27 |
| ABQ412 | Airblue | 4 | 2026-05-29 |
| ABQ4763 | - | 3 | 2026-05-07 |
| ABQ472 | Airblue | 2 | 2026-05-26 |
| ABQ471 | Airblue | 2 | 2026-05-11 |
| ABQ401 | Airblue | 2 | 2026-05-08 |
| ABQ811 | Airblue | 1 | 2026-05-10 |
| ABQ810 | Airblue | 1 | 2026-05-10 |
| ABQ485 | - | 1 | 2026-04-16 |
| ABQ484 | - | 1 | 2026-04-16 |
| ABQ4762 | Airblue | 1 | 2026-04-21 |
| ABQ4760 | Airblue | 1 | 2026-05-03 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | ABQ412 | LHE → SHJ | May 29, 19:15 UTC | May 30, 02:20 UTC | 7h 5m |
| 2026-05-28 | ABQ479 | - | May 28, 23:35 UTC | May 29, 02:25 UTC | 2h 50m |
| 2026-05-28 | ABQ478 | - | May 28, 18:00 UTC | May 28, 18:30 UTC | 30m |
| 2026-05-27 | ABQ474 | LHE → RUH | May 27, 17:05 UTC | May 28, 02:35 UTC | 9h 30m |
| 2026-05-26 | ABQ472 | LHE → JED | May 26, 21:49 UTC | May 27, 06:09 UTC | 8h 20m |
| 2026-05-24 | ABQ473 | JED → LHE | May 24, 18:40 UTC | May 25, 06:20 UTC | 11h 40m |
| 2026-05-24 | ABQ405 | LHE → KHI | May 24, 12:10 UTC | May 24, 16:20 UTC | 4h 10m |
| 2026-05-23 | ABQ479 | - | May 23, 23:25 UTC | May 24, 02:10 UTC | 2h 45m |
| 2026-05-23 | ABQ478 | - | May 23, 17:55 UTC | May 23, 18:30 UTC | 36m |
| 2026-05-22 | ABQ405 | LHE → KHI | May 22, 14:35 UTC | May 22, 18:40 UTC | 4h 5m |
| 2026-05-21 | ABQ479 | - | May 21, 23:55 UTC | May 22, 03:00 UTC | 3h 5m |
| 2026-05-21 | ABQ478 | - | May 21, 22:15 UTC | May 21, 22:25 UTC | 10m |
| 2026-05-21 | ABQ478 | - | May 21, 18:40 UTC | May 21, 19:10 UTC | 30m |
| 2026-05-15 | ABQ475 | RUH → LHE | May 15, 17:10 UTC | May 16, 02:35 UTC | 9h 25m |
| 2026-05-15 | ABQ473 | JED → LHE | May 15, 03:20 UTC | May 15, 15:05 UTC | 11h 44m |
| 2026-05-14 | ABQ473 | JED → LHE | May 14, 18:40 UTC | May 15, 15:05 UTC | 20h 24m |
| 2026-05-14 | ABQ405 | LHE → KHI | May 14, 12:10 UTC | May 14, 16:10 UTC | 4h 0m |
| 2026-05-12 | ABQ412 | LHE → SHJ | May 12, 19:20 UTC | May 13, 02:20 UTC | 7h 0m |
| 2026-05-12 | ABQ405 | LHE → KHI | May 12, 12:20 UTC | May 12, 16:15 UTC | 3h 55m |
| 2026-05-12 | ABQ473 | JED → LHE | May 12, 06:40 UTC | May 12, 09:35 UTC | 2h 55m |
| 2026-05-11 | ABQ471 | JED → LHE | May 11, 01:25 UTC | May 11, 18:30 UTC | 17h 6m |
| 2026-05-10 | ABQ471 | JED → LHE | May 10, 22:45 UTC | May 11, 18:30 UTC | 19h 46m |
| 2026-05-10 | ABQ810 | MUX → DXB | May 10, 16:14 UTC | May 10, 16:20 UTC | 5m |
| 2026-05-10 | ABQ811 | DXB → MUX | May 10, 14:45 UTC | May 10, 14:54 UTC | 10m |
| 2026-05-09 | ABQ479 | - | May 9, 23:35 UTC | May 10, 08:20 UTC | 8h 45m |
| 2026-05-09 | ABQ478 | - | May 9, 21:50 UTC | May 9, 22:00 UTC | 10m |
| 2026-05-09 | ABQ475 | RUH → LHE | May 9, 03:30 UTC | May 9, 18:50 UTC | 15h 20m |
| 2026-05-08 | ABQ401 | LHE → KHI | May 8, 12:55 UTC | May 9, 03:35 UTC | 14h 40m |
| 2026-05-07 | ABQ401 | LHE → KHI | May 7, 22:05 UTC | May 8, 18:50 UTC | 20h 45m |
| 2026-05-07 | ABQ4763 | - | May 7, 19:15 UTC | May 8, 16:35 UTC | 21h 20m |
| 2026-05-07 | ABQ4763 | - | May 7, 05:40 UTC | May 7, 22:05 UTC | 16h 25m |
| 2026-05-07 | ABQ473 | JED → LHE | May 7, 02:55 UTC | May 7, 22:05 UTC | 19h 10m |
| 2026-05-05 | ABQ416 | LHE → DXB | May 5, 12:55 UTC | May 5, 13:15 UTC | 20m |
| 2026-05-04 | ABQ474 | LHE → RUH | May 4, 17:40 UTC | May 5, 10:50 UTC | 17h 11m |
| 2026-05-04 | ABQ474 | LHE → RUH | May 4, 06:20 UTC | May 5, 02:50 UTC | 20h 31m |
| 2026-05-04 | ABQ4761 | - | May 4, 03:49 UTC | May 5, 02:50 UTC | 23h 1m |
| 2026-05-04 | ABQ4761 | - | May 4, 03:24 UTC | May 4, 18:00 UTC | 14h 35m |
| 2026-05-03 | ABQ4761 | - | May 3, 21:54 UTC | May 4, 18:00 UTC | 20h 5m |
| 2026-05-03 | ABQ4761 | - | May 3, 19:50 UTC | May 4, 18:00 UTC | 22h 10m |
| 2026-05-03 | ABQ4761 | - | May 3, 19:34 UTC | May 4, 17:45 UTC | 22h 10m |
| 2026-05-03 | ABQ4760 | LHE → MED | May 3, 02:25 UTC | May 3, 22:54 UTC | 20h 29m |
| 2026-05-02 | ABQ479 | - | May 2, 23:50 UTC | May 3, 22:54 UTC | 23h 4m |
| 2026-05-02 | ABQ478 | - | May 2, 19:05 UTC | May 2, 22:25 UTC | 3h 20m |
| 2026-05-01 | ABQ405 | LHE → KHI | May 1, 14:15 UTC | May 1, 17:50 UTC | 3h 35m |
| 2026-04-30 | ABQ417 | DXB → LHE | Apr 30, 14:50 UTC | Apr 30, 15:20 UTC | 30m |
| 2026-04-30 | ABQ416 | LHE → DXB | Apr 30, 10:30 UTC | Apr 30, 13:15 UTC | 2h 45m |
| 2026-04-29 | ABQ416 | LHE → DXB | Apr 29, 16:15 UTC | Apr 30, 13:15 UTC | 20h 59m |
| 2026-04-29 | ABQ416 | LHE → DXB | Apr 29, 12:45 UTC | Apr 30, 10:45 UTC | 21h 59m |
| 2026-04-27 | ABQ475 | RUH → LHE | Apr 27, 23:40 UTC | Apr 28, 16:15 UTC | 16h 35m |
| 2026-04-27 | ABQ475 | RUH → LHE | Apr 27, 20:20 UTC | Apr 28, 16:15 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-EDG page for operator, model, and routing details .