sensors Mode-S transponder
7609FA
ICAO 24-bit transponder address · allocated to Pakistan
Currently assigned to AP-BOZ
- Hex
- 7609FA
- Octal
- 35404772
- Decimal
- 7,735,802
- Country
- PK
- Tail
- AP-BOZ
- Type
- A320
- Flights observed
- 283
- Distinct callsigns
- 20
- Country
- PK
- Last broadcast
- Jul 26, 20:55 UTC
Last known position
Country allocation
The ICAO 24-bit address 7609FA 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 |
|---|---|---|---|
| FJL781 | Fly Jinnah | 35 | 2026-07-25 |
| FJL500 | - | 14 | 2026-07-14 |
| FJL700 | Fly Jinnah | 13 | 2026-05-27 |
| FJL711 | Fly Jinnah | 11 | 2026-07-26 |
| FJL502 | - | 11 | 2026-07-14 |
| FJL866 | Fly Jinnah | 10 | 2026-04-30 |
| FJL783 | Fly Jinnah | 10 | 2026-06-15 |
| FJL514 | - | 10 | 2026-07-17 |
| FJL501 | - | 10 | 2026-07-14 |
| FJL515 | - | 9 | 2026-07-18 |
| FJL841 | - | 8 | 2026-07-12 |
| FJL741 | Fly Jinnah | 8 | 2026-07-23 |
| FJL701 | Fly Jinnah | 8 | 2026-07-20 |
| FJL503 | - | 8 | 2026-07-14 |
| FJL847 | - | 7 | 2026-07-12 |
| FJL843 | - | 7 | 2026-07-12 |
| FJL780 | - | 7 | 2026-07-18 |
| FJL740 | Fly Jinnah | 7 | 2026-07-25 |
| FJL857 | Fly Jinnah | 6 | 2026-06-17 |
| FJL710 | Fly Jinnah | 6 | 2026-07-26 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | FJL711 | DMM → ISB | Jul 26, 19:45 UTC | Jul 26, 20:55 UTC | 1h 10m |
| 2026-07-26 | FJL710 | ISB → DMM | Jul 26, 05:25 UTC | Jul 26, 18:40 UTC | 13h 16m |
| 2026-07-25 | FJL781 | RUH → ISB | Jul 25, 10:30 UTC | Jul 26, 04:10 UTC | 17h 40m |
| 2026-07-25 | FJL740 | ISB → SHJ | Jul 25, 05:05 UTC | Jul 25, 05:25 UTC | 20m |
| 2026-07-24 | FJL747 | SHJ → ISB | Jul 24, 22:30 UTC | Jul 25, 03:15 UTC | 4h 45m |
| 2026-07-24 | FJL746 | ISB → SHJ | Jul 24, 17:05 UTC | Jul 24, 19:25 UTC | 2h 20m |
| 2026-07-24 | FJL765D | - | Jul 24, 04:25 UTC | Jul 24, 09:35 UTC | 5h 10m |
| 2026-07-23 | FJL765 | BAH → ISB | Jul 23, 22:00 UTC | Jul 23, 23:05 UTC | 1h 5m |
| 2026-07-23 | FJL764 | ISB → BAH | Jul 23, 17:50 UTC | Jul 23, 20:45 UTC | 2h 55m |
| 2026-07-23 | FJL741 | SHJ → ISB | Jul 23, 05:25 UTC | Jul 23, 07:35 UTC | 2h 10m |
| 2026-07-21 | FJL781 | RUH → ISB | Jul 21, 21:05 UTC | Jul 22, 05:10 UTC | 8h 5m |
| 2026-07-21 | FJL741 | SHJ → ISB | Jul 21, 05:55 UTC | Jul 21, 18:55 UTC | 13h 0m |
| 2026-07-21 | FJL740 | ISB → SHJ | Jul 21, 03:55 UTC | Jul 21, 04:20 UTC | 25m |
| 2026-07-20 | FJL711 | DMM → ISB | Jul 20, 20:30 UTC | Jul 20, 23:25 UTC | 2h 55m |
| 2026-07-20 | FJL701 | JED → ISB | Jul 20, 02:25 UTC | Jul 20, 19:05 UTC | 16h 40m |
| 2026-07-19 | FJL701 | JED → ISB | Jul 19, 23:55 UTC | Jul 20, 19:05 UTC | 19h 10m |
| 2026-07-19 | FJL701 | JED → ISB | Jul 19, 20:55 UTC | Jul 20, 19:05 UTC | 22h 10m |
| 2026-07-18 | FJL701 | JED → ISB | Jul 18, 23:45 UTC | Jul 19, 18:10 UTC | 18h 25m |
| 2026-07-18 | FJL781 | RUH → ISB | Jul 18, 20:50 UTC | Jul 19, 18:10 UTC | 21h 20m |
| 2026-07-18 | FJL780 | - | Jul 18, 07:20 UTC | Jul 18, 18:20 UTC | 11h 0m |
| 2026-07-18 | FJL515 | DXB → DXB | Jul 18, 00:25 UTC | Jul 18, 00:50 UTC | 25m |
| 2026-07-17 | FJL514 | - | Jul 17, 19:35 UTC | Jul 17, 20:04 UTC | 30m |
| 2026-07-16 | FJL765 | - | Jul 16, 21:45 UTC | Jul 17, 08:25 UTC | 10h 40m |
| 2026-07-16 | FJL764 | ISB → BAH | Jul 16, 06:00 UTC | Jul 16, 20:35 UTC | 14h 35m |
| 2026-07-14 | FJL503 | - | Jul 14, 20:20 UTC | Jul 14, 22:35 UTC | 2h 15m |
| 2026-07-14 | FJL502 | - | Jul 14, 18:20 UTC | Jul 14, 18:45 UTC | 25m |
| 2026-07-14 | FJL501 | - | Jul 14, 12:00 UTC | Jul 14, 14:25 UTC | 2h 25m |
| 2026-07-14 | FJL500 | - | Jul 14, 10:40 UTC | Jul 14, 10:50 UTC | 10m |
| 2026-07-14 | FJL500 | - | Jul 14, 08:05 UTC | Jul 14, 08:40 UTC | 35m |
| 2026-07-14 | FJL503 | - | Jul 14, 00:40 UTC | Jul 14, 02:55 UTC | 2h 15m |
| 2026-07-13 | FJL502 | LHE → SHJ | Jul 13, 16:05 UTC | Jul 13, 18:50 UTC | 2h 45m |
| 2026-07-13 | FJL581 | - | Jul 13, 04:45 UTC | Jul 13, 13:50 UTC | 9h 5m |
| 2026-07-12 | FJL531 | - | Jul 12, 23:40 UTC | Jul 13, 02:35 UTC | 2h 55m |
| 2026-07-12 | FJL530 | - | Jul 12, 21:25 UTC | Jul 12, 22:30 UTC | 1h 5m |
| 2026-07-12 | FJL847 | - | Jul 12, 13:40 UTC | Jul 12, 17:10 UTC | 3h 30m |
| 2026-07-12 | FJL843 | - | Jul 12, 08:35 UTC | Jul 12, 12:10 UTC | 3h 35m |
| 2026-07-12 | FJL841 | - | Jul 12, 03:25 UTC | Jul 12, 07:01 UTC | 3h 35m |
| 2026-07-11 | FJL503 | - | Jul 11, 20:15 UTC | Jul 11, 22:30 UTC | 2h 15m |
| 2026-07-11 | FJL502 | - | Jul 11, 15:35 UTC | Jul 11, 18:15 UTC | 2h 40m |
| 2026-07-11 | FJL501 | - | Jul 11, 11:40 UTC | Jul 11, 14:00 UTC | 2h 20m |
| 2026-07-11 | FJL500 | LHE → SHJ | Jul 11, 07:30 UTC | Jul 11, 10:20 UTC | 2h 50m |
| 2026-07-10 | FJL531 | - | Jul 10, 23:50 UTC | Jul 11, 02:45 UTC | 2h 55m |
| 2026-07-10 | FJL530 | - | Jul 10, 19:35 UTC | Jul 10, 22:50 UTC | 3h 15m |
| 2026-07-10 | FJL501 | - | Jul 10, 12:45 UTC | Jul 10, 15:00 UTC | 2h 15m |
| 2026-07-10 | FJL500 | - | Jul 10, 08:50 UTC | Jul 10, 11:35 UTC | 2h 45m |
| 2026-07-10 | FJL501 | - | Jul 10, 00:50 UTC | Jul 10, 03:10 UTC | 2h 20m |
| 2026-07-09 | FJL500 | - | Jul 9, 10:20 UTC | Jul 9, 10:30 UTC | 10m |
| 2026-07-09 | FJL500 | - | Jul 9, 07:45 UTC | Jul 9, 08:15 UTC | 30m |
| 2026-07-08 | FJL503 | - | Jul 8, 20:25 UTC | Jul 8, 22:35 UTC | 2h 10m |
| 2026-07-08 | FJL502 | - | Jul 8, 15:40 UTC | Jul 8, 18:25 UTC | 2h 45m |
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-BOZ page for operator, model, and routing details .