sensors Mode-S transponder
760A0C
ICAO 24-bit transponder address · allocated to Pakistan
Currently assigned to AP-BPL · AIRBUS A-320
- Hex
- 760A0C
- Octal
- 35405014
- Decimal
- 7,735,820
- Country
- PK
- Tail
- AP-BPL
- Type
- A320
- Flights observed
- 135
- Distinct callsigns
- 20
- Country
- PK
- Last broadcast
- 2h ago
Last known position
Country allocation
The ICAO 24-bit address 760A0C 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 |
|---|---|---|---|
| FJL601 | Fly Jinnah | 12 | 2026-05-23 |
| FJL821 | Fly Jinnah | 11 | 2026-05-28 |
| FJL710 | Fly Jinnah | 9 | 2026-04-29 |
| FJL711 | Fly Jinnah | 8 | 2026-04-30 |
| FJL570 | Fly Jinnah | 7 | 2026-05-06 |
| FJL571 | Fly Jinnah | 6 | 2026-05-07 |
| FJL781 | Fly Jinnah | 5 | 2026-04-19 |
| FJL673 | Fly Jinnah | 5 | 2026-06-01 |
| FJL587 | Fly Jinnah | 5 | 2026-05-09 |
| FJL811 | Fly Jinnah | 4 | 2026-05-20 |
| FJL783 | Fly Jinnah | 4 | 2026-04-20 |
| FJL742 | Fly Jinnah | 4 | 2026-04-30 |
| FJL672 | Fly Jinnah | 4 | 2026-05-14 |
| FJL670 | Fly Jinnah | 4 | 2026-06-01 |
| FJL580 | Fly Jinnah | 4 | 2026-05-04 |
| FJL856 | Fly Jinnah | 3 | 2026-05-31 |
| FJL820 | Fly Jinnah | 3 | 2026-05-18 |
| FJL780 | Fly Jinnah | 3 | 2026-04-21 |
| FJL743 | Fly Jinnah | 3 | 2026-04-30 |
| FJL586 | Fly Jinnah | 3 | 2026-05-09 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | FJL600 | KHI → JED | Jun 2, 10:45 UTC | Jun 2, 17:45 UTC | 7h 0m |
| 2026-06-01 | FJL673 | ISB → KHI | Jun 1, 13:05 UTC | Jun 2, 13:00 UTC | 23h 55m |
| 2026-06-01 | FJL673 | ISB → KHI | Jun 1, 12:55 UTC | Jun 2, 10:55 UTC | 22h 0m |
| 2026-06-01 | FJL670 | KHI → ISB | Jun 1, 03:05 UTC | Jun 1, 13:10 UTC | 10h 5m |
| 2026-05-31 | FJL856 | LHE → UET | May 31, 12:05 UTC | Jun 1, 11:00 UTC | 22h 55m |
| 2026-05-31 | FJL856 | LHE → UET | May 31, 10:00 UTC | Jun 1, 05:25 UTC | 19h 25m |
| 2026-05-30 | FJL670 | KHI → ISB | May 30, 03:15 UTC | May 30, 15:05 UTC | 11h 50m |
| 2026-05-29 | FJL851D | - | May 29, 12:40 UTC | May 29, 12:45 UTC | 5m |
| 2026-05-29 | FJL851 | KHI → UET | May 29, 10:05 UTC | May 29, 10:15 UTC | 10m |
| 2026-05-28 | FJL821 | SKT → KHI | May 28, 05:35 UTC | May 28, 11:05 UTC | 5h 30m |
| 2026-05-27 | FJL856 | LHE → UET | May 27, 11:55 UTC | May 28, 11:00 UTC | 23h 5m |
| 2026-05-27 | FJL855 | UET → LHE | May 27, 10:15 UTC | May 27, 10:30 UTC | 15m |
| 2026-05-26 | FJL855 | UET → LHE | May 26, 12:30 UTC | May 27, 10:30 UTC | 22h 1m |
| 2026-05-25 | FJL821 | SKT → KHI | May 25, 17:05 UTC | May 26, 11:09 UTC | 18h 4m |
| 2026-05-25 | FJL821 | SKT → KHI | May 25, 14:40 UTC | May 26, 11:09 UTC | 20h 30m |
| 2026-05-25 | FJL821 | SKT → KHI | May 25, 11:20 UTC | May 26, 11:00 UTC | 23h 39m |
| 2026-05-25 | FJL821 | SKT → KHI | May 25, 09:25 UTC | May 26, 07:49 UTC | 22h 25m |
| 2026-05-25 | FJL670 | KHI → ISB | May 25, 03:10 UTC | May 25, 17:10 UTC | 14h 0m |
| 2026-05-24 | FJL865 | KHI → PEW | May 24, 11:05 UTC | May 25, 09:35 UTC | 22h 30m |
| 2026-05-24 | FJL865 | KHI → PEW | May 24, 10:55 UTC | May 25, 05:25 UTC | 18h 30m |
| 2026-05-24 | FJL821 | SKT → KHI | May 24, 07:20 UTC | May 25, 05:25 UTC | 22h 5m |
| 2026-05-23 | FJL601 | JED → KHI | May 23, 12:45 UTC | May 24, 06:00 UTC | 17h 16m |
| 2026-05-22 | FJL679 | ISB → KHI | May 22, 17:10 UTC | May 23, 07:40 UTC | 14h 29m |
| 2026-05-22 | FJL871 | MUX → KHI | May 22, 12:50 UTC | May 22, 12:55 UTC | 5m |
| 2026-05-22 | FJL870 | KHI → MUX | May 22, 11:45 UTC | May 22, 11:55 UTC | 10m |
| 2026-05-21 | FJL600 | KHI → JED | May 21, 12:35 UTC | May 21, 18:15 UTC | 5h 40m |
| 2026-05-21 | FJL810 | KHI → LYP | May 21, 11:05 UTC | May 21, 11:15 UTC | 10m |
| 2026-05-21 | FJL821 | SKT → KHI | May 21, 05:35 UTC | May 21, 07:45 UTC | 2h 10m |
| 2026-05-20 | FJL871 | MUX → KHI | May 20, 12:45 UTC | May 20, 12:55 UTC | 10m |
| 2026-05-20 | FJL870 | KHI → MUX | May 20, 11:30 UTC | May 20, 11:45 UTC | 15m |
| 2026-05-20 | FJL811 | LYP → KHI | May 20, 07:30 UTC | May 20, 07:45 UTC | 15m |
| 2026-05-20 | FJL810 | KHI → LYP | May 20, 05:45 UTC | May 20, 05:55 UTC | 10m |
| 2026-05-19 | FJL811 | LYP → KHI | May 19, 12:45 UTC | May 19, 13:00 UTC | 15m |
| 2026-05-19 | FJL821 | SKT → KHI | May 19, 07:30 UTC | May 19, 08:00 UTC | 30m |
| 2026-05-18 | FJL820 | KHI → SKT | May 18, 11:45 UTC | May 19, 06:10 UTC | 18h 24m |
| 2026-05-18 | FJL820 | KHI → SKT | May 18, 09:40 UTC | May 19, 06:10 UTC | 20h 29m |
| 2026-05-17 | FJL601 | JED → KHI | May 17, 17:55 UTC | May 18, 11:55 UTC | 18h 0m |
| 2026-05-17 | FJL601 | JED → KHI | May 17, 12:50 UTC | May 18, 09:45 UTC | 20h 55m |
| 2026-05-17 | FJL601 | JED → KHI | May 17, 10:55 UTC | May 18, 05:30 UTC | 18h 35m |
| 2026-05-17 | FJL601 | JED → KHI | May 17, 07:30 UTC | May 18, 05:30 UTC | 22h 0m |
| 2026-05-17 | FJL601 | JED → KHI | May 17, 05:35 UTC | May 18, 03:10 UTC | 21h 35m |
| 2026-05-16 | FJL811 | LYP → KHI | May 16, 12:40 UTC | May 17, 11:01 UTC | 22h 20m |
| 2026-05-15 | FJL821 | SKT → KHI | May 15, 17:05 UTC | May 16, 07:55 UTC | 14h 51m |
| 2026-05-15 | FJL673 | ISB → KHI | May 15, 11:55 UTC | May 16, 07:55 UTC | 20h 0m |
| 2026-05-15 | FJL673 | ISB → KHI | May 15, 09:45 UTC | May 16, 07:55 UTC | 22h 10m |
| 2026-05-14 | FJL673 | ISB → KHI | May 14, 22:30 UTC | May 15, 19:35 UTC | 21h 4m |
| 2026-05-14 | FJL672 | KHI → ISB | May 14, 12:30 UTC | May 15, 09:55 UTC | 21h 25m |
| 2026-05-14 | FJL672 | KHI → ISB | May 14, 05:30 UTC | May 14, 23:10 UTC | 17h 40m |
| 2026-05-14 | FJL672 | KHI → ISB | May 14, 03:05 UTC | May 14, 23:10 UTC | 20h 5m |
| 2026-05-13 | FJL672 | KHI → ISB | May 13, 13:45 UTC | May 14, 12:35 UTC | 22h 50m |
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-BPL page for operator, model, and routing details .