sensors Mode-S transponder
7609F0
ICAO 24-bit transponder address · allocated to Pakistan
Currently assigned to AP-BOP · AIRBUS A-320
- Hex
- 7609F0
- Octal
- 35404760
- Decimal
- 7,735,792
- Country
- PK
- Tail
- AP-BOP
- Type
- A320
- Flights observed
- 123
- Distinct callsigns
- 20
- Country
- PK
- Last broadcast
- 3h ago
Last known position
Country allocation
The ICAO 24-bit address 7609F0 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 | 13 | 2026-05-13 |
| FJL670 | Fly Jinnah | 9 | 2026-05-28 |
| FJL855 | Fly Jinnah | 8 | 2026-05-24 |
| FJL780 | Fly Jinnah | 6 | 2026-04-25 |
| FJL605 | Fly Jinnah | 6 | 2026-04-30 |
| FJL871 | Fly Jinnah | 5 | 2026-05-29 |
| FJL847 | Fly Jinnah | 5 | 2026-05-28 |
| FJL581 | Fly Jinnah | 5 | 2026-04-16 |
| FJL870 | Fly Jinnah | 4 | 2026-05-29 |
| FJL866 | Fly Jinnah | 4 | 2026-05-16 |
| FJL856 | Fly Jinnah | 4 | 2026-05-22 |
| FJL811 | - | 4 | 2026-05-30 |
| FJL781 | Fly Jinnah | 4 | 2026-04-28 |
| FJL857 | Fly Jinnah | 3 | 2026-05-10 |
| FJL580 | Fly Jinnah | 3 | 2026-04-16 |
| FJL849 | Fly Jinnah | 2 | 2026-05-25 |
| FJL711 | Fly Jinnah | 2 | 2026-04-26 |
| FJL710 | Fly Jinnah | 2 | 2026-04-23 |
| FJL701 | Fly Jinnah | 2 | 2026-04-27 |
| FJL679 | Fly Jinnah | 2 | 2026-05-05 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | FJL811 | - | May 30, 13:40 UTC | May 30, 13:50 UTC | 10m |
| 2026-05-30 | FJL820 | KHI → SKT | May 30, 05:40 UTC | May 30, 12:15 UTC | 6h 35m |
| 2026-05-29 | FJL871 | MUX → KHI | May 29, 13:15 UTC | May 29, 13:20 UTC | 5m |
| 2026-05-29 | FJL870 | KHI → MUX | May 29, 12:05 UTC | May 29, 12:20 UTC | 15m |
| 2026-05-28 | FJL847 | LHE → KHI | May 28, 13:25 UTC | May 28, 13:55 UTC | 30m |
| 2026-05-28 | FJL670 | KHI → ISB | May 28, 03:00 UTC | May 28, 11:40 UTC | 8h 40m |
| 2026-05-27 | FJL847 | LHE → KHI | May 27, 13:15 UTC | May 28, 11:40 UTC | 22h 25m |
| 2026-05-27 | FJL842 | KHI → LHE | May 27, 11:35 UTC | May 27, 11:45 UTC | 10m |
| 2026-05-26 | FJL847 | LHE → KHI | May 26, 13:19 UTC | May 27, 11:45 UTC | 22h 26m |
| 2026-05-26 | FJL670 | KHI → ISB | May 26, 03:09 UTC | May 26, 11:50 UTC | 8h 40m |
| 2026-05-25 | FJL670 | KHI → ISB | May 25, 12:55 UTC | May 26, 11:50 UTC | 22h 54m |
| 2026-05-25 | FJL672 | KHI → ISB | May 25, 10:45 UTC | May 26, 05:25 UTC | 18h 39m |
| 2026-05-25 | FJL849 | LHE → KHI | May 25, 06:10 UTC | May 26, 05:25 UTC | 23h 14m |
| 2026-05-25 | FJL849 | LHE → KHI | May 25, 05:50 UTC | May 26, 03:19 UTC | 21h 29m |
| 2026-05-24 | FJL855 | UET → LHE | May 24, 10:20 UTC | May 25, 04:20 UTC | 18h 0m |
| 2026-05-24 | FJL855 | UET → LHE | May 24, 03:05 UTC | May 24, 12:35 UTC | 9h 30m |
| 2026-05-23 | FJL845 | LHE → KHI | May 23, 16:25 UTC | May 24, 12:35 UTC | 20h 10m |
| 2026-05-23 | FJL670 | KHI → ISB | May 23, 03:05 UTC | May 23, 14:40 UTC | 11h 35m |
| 2026-05-22 | FJL856 | LHE → UET | May 22, 12:25 UTC | May 23, 11:40 UTC | 23h 14m |
| 2026-05-22 | FJL855 | UET → LHE | May 22, 10:55 UTC | May 22, 11:05 UTC | 10m |
| 2026-05-21 | FJL847 | LHE → KHI | May 21, 13:25 UTC | May 22, 11:05 UTC | 21h 40m |
| 2026-05-21 | FJL670 | KHI → ISB | May 21, 03:05 UTC | May 21, 11:40 UTC | 8h 35m |
| 2026-05-20 | FJL856 | LHE → UET | May 20, 12:10 UTC | May 21, 11:40 UTC | 23h 30m |
| 2026-05-20 | FJL855 | UET → LHE | May 20, 03:10 UTC | May 20, 10:50 UTC | 7h 41m |
| 2026-05-19 | FJL847 | LHE → KHI | May 19, 13:20 UTC | May 20, 10:50 UTC | 21h 31m |
| 2026-05-18 | FJL675 | ISB → KHI | May 18, 17:15 UTC | May 19, 11:40 UTC | 18h 24m |
| 2026-05-18 | FJL675 | ISB → KHI | May 18, 15:00 UTC | May 19, 11:40 UTC | 20h 39m |
| 2026-05-17 | FJL856 | LHE → UET | May 17, 12:01 UTC | May 17, 12:25 UTC | 25m |
| 2026-05-16 | FJL855 | UET → LHE | May 16, 16:55 UTC | May 17, 10:30 UTC | 17h 35m |
| 2026-05-16 | FJL855 | UET → LHE | May 16, 14:51 UTC | May 17, 10:30 UTC | 19h 40m |
| 2026-05-16 | FJL866 | PEW → KHI | May 16, 11:35 UTC | May 17, 05:25 UTC | 17h 50m |
| 2026-05-16 | FJL866 | PEW → KHI | May 16, 09:35 UTC | May 17, 05:25 UTC | 19h 50m |
| 2026-05-16 | FJL866 | PEW → KHI | May 16, 05:15 UTC | May 17, 03:20 UTC | 22h 5m |
| 2026-05-16 | FJL866 | PEW → KHI | May 16, 03:05 UTC | May 16, 17:01 UTC | 13h 56m |
| 2026-05-15 | FJL856 | LHE → UET | May 15, 12:45 UTC | May 16, 11:51 UTC | 23h 5m |
| 2026-05-15 | FJL855 | UET → LHE | May 15, 10:35 UTC | May 15, 10:55 UTC | 20m |
| 2026-05-14 | FJL855 | UET → LHE | May 14, 12:55 UTC | May 15, 10:55 UTC | 22h 0m |
| 2026-05-14 | FJL821 | SKT → KHI | May 14, 07:30 UTC | May 14, 13:10 UTC | 5h 40m |
| 2026-05-13 | FJL601 | JED → KHI | May 13, 12:55 UTC | May 14, 06:15 UTC | 17h 20m |
| 2026-05-13 | FJL870 | KHI → MUX | May 13, 11:50 UTC | May 13, 12:05 UTC | 15m |
| 2026-05-13 | FJL811 | LYP → KHI | May 13, 07:30 UTC | May 13, 07:40 UTC | 10m |
| 2026-05-12 | FJL670 | KHI → ISB | May 12, 03:05 UTC | May 12, 12:05 UTC | 9h 0m |
| 2026-05-11 | FJL670 | KHI → ISB | May 11, 17:20 UTC | May 12, 12:05 UTC | 18h 45m |
| 2026-05-11 | FJL674 | KHI → ISB | May 11, 14:45 UTC | May 12, 12:05 UTC | 21h 21m |
| 2026-05-11 | FJL674 | KHI → ISB | May 11, 11:25 UTC | May 12, 05:30 UTC | 18h 6m |
| 2026-05-11 | FJL865 | KHI → PEW | May 11, 09:35 UTC | May 12, 05:30 UTC | 19h 55m |
| 2026-05-11 | FJL671 | ISB → KHI | May 11, 05:20 UTC | May 12, 03:15 UTC | 21h 56m |
| 2026-05-11 | FJL670 | KHI → ISB | May 11, 03:10 UTC | May 11, 17:20 UTC | 14h 11m |
| 2026-05-10 | FJL670 | KHI → ISB | May 10, 20:25 UTC | May 11, 17:20 UTC | 20h 56m |
| 2026-05-10 | FJL857 | UET → ISB | May 10, 14:30 UTC | May 11, 11:30 UTC | 21h 0m |
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-BOP page for operator, model, and routing details .