sensors Mode-S transponder
7609F6
ICAO 24-bit transponder address · allocated to Pakistan
Currently assigned to AP-BOV · AIRBUS A-320
- Hex
- 7609F6
- Octal
- 35404766
- Decimal
- 7,735,798
- Country
- PK
- Tail
- AP-BOV
- Type
- A320
- Flights observed
- 281
- Distinct callsigns
- 20
- Country
- PK
- Last broadcast
- Jul 26, 21:30 UTC
Last known position
Country allocation
The ICAO 24-bit address 7609F6 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 |
|---|---|---|---|
| FJL600 | - | 32 | 2026-07-17 |
| FJL601 | - | 30 | 2026-07-14 |
| FJL581 | Fly Jinnah | 14 | 2026-06-15 |
| FJL514 | Fly Jinnah | 14 | 2026-06-15 |
| FJL856 | - | 13 | 2026-07-15 |
| FJL843 | - | 13 | 2026-06-17 |
| FJL580 | Fly Jinnah | 12 | 2026-06-07 |
| FJL570 | Fly Jinnah | 12 | 2026-05-23 |
| FJL841 | - | 11 | 2026-06-17 |
| FJL711 | Fly Jinnah | 11 | 2026-07-25 |
| FJL502 | Fly Jinnah | 9 | 2026-06-16 |
| FJL781 | Fly Jinnah | 8 | 2026-07-26 |
| FJL586 | Fly Jinnah | 8 | 2026-06-04 |
| FJL500 | Fly Jinnah | 8 | 2026-06-16 |
| FJL571 | Fly Jinnah | 7 | 2026-06-02 |
| FJL870 | - | 6 | 2026-07-11 |
| FJL871 | - | 5 | 2026-07-01 |
| FJL701 | Fly Jinnah | 5 | 2026-07-24 |
| FJL700 | Fly Jinnah | 5 | 2026-05-08 |
| FJL631 | - | 5 | 2026-07-16 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | FJL781 | RUH → ISB | Jul 26, 04:20 UTC | Jul 26, 21:30 UTC | 17h 11m |
| 2026-07-25 | FJL711 | DMM → ISB | Jul 25, 20:10 UTC | Jul 26, 18:00 UTC | 21h 51m |
| 2026-07-25 | FJL710 | ISB → DMM | Jul 25, 16:00 UTC | Jul 25, 19:00 UTC | 3h 0m |
| 2026-07-24 | FJL781 | RUH → ISB | Jul 24, 17:35 UTC | Jul 25, 11:35 UTC | 18h 0m |
| 2026-07-24 | FJL781 | RUH → ISB | Jul 24, 17:05 UTC | Jul 25, 11:35 UTC | 18h 30m |
| 2026-07-24 | FJL781 | RUH → ISB | Jul 24, 15:15 UTC | Jul 25, 11:35 UTC | 20h 20m |
| 2026-07-24 | FJL781 | RUH → ISB | Jul 24, 12:50 UTC | Jul 25, 11:30 UTC | 22h 40m |
| 2026-07-24 | FJL781 | RUH → ISB | Jul 24, 09:55 UTC | Jul 25, 05:20 UTC | 19h 25m |
| 2026-07-24 | FJL781 | RUH → ISB | Jul 24, 04:30 UTC | Jul 25, 02:35 UTC | 22h 5m |
| 2026-07-24 | FJL781 | RUH → ISB | Jul 24, 02:35 UTC | Jul 24, 23:40 UTC | 21h 5m |
| 2026-07-24 | FJL701 | JED → ISB | Jul 24, 00:25 UTC | Jul 24, 21:55 UTC | 21h 30m |
| 2026-07-23 | FJL701 | JED → ISB | Jul 23, 22:20 UTC | Jul 24, 21:30 UTC | 23h 10m |
| 2026-07-22 | FJL711 | DMM → ISB | Jul 22, 21:35 UTC | Jul 23, 17:30 UTC | 19h 55m |
| 2026-07-22 | FJL711 | DMM → ISB | Jul 22, 21:05 UTC | Jul 23, 17:30 UTC | 20h 25m |
| 2026-07-22 | FJL745 | SHJ → ISB | Jul 22, 04:15 UTC | Jul 22, 16:55 UTC | 12h 40m |
| 2026-07-20 | FJL783 | - | Jul 20, 19:10 UTC | Jul 21, 03:40 UTC | 8h 29m |
| 2026-07-20 | FJL782 | - | Jul 20, 17:30 UTC | Jul 20, 17:40 UTC | 10m |
| 2026-07-19 | FJL782 | - | Jul 19, 21:35 UTC | Jul 20, 16:50 UTC | 19h 15m |
| 2026-07-19 | FJL711 | DMM → ISB | Jul 19, 21:05 UTC | Jul 20, 16:50 UTC | 19h 45m |
| 2026-07-19 | FJL710 | - | Jul 19, 16:40 UTC | Jul 19, 19:40 UTC | 3h 0m |
| 2026-07-19 | FJL858 | ISB → UET | Jul 19, 06:10 UTC | Jul 19, 08:20 UTC | 2h 10m |
| 2026-07-18 | FJL747 | SHJ → ISB | Jul 18, 22:00 UTC | Jul 18, 22:30 UTC | 30m |
| 2026-07-18 | FJL746 | - | Jul 18, 18:30 UTC | Jul 18, 20:40 UTC | 2h 10m |
| 2026-07-18 | FJL821 | - | Jul 18, 07:25 UTC | Jul 18, 11:10 UTC | 3h 45m |
| 2026-07-17 | FJL600 | - | Jul 17, 12:10 UTC | Jul 18, 06:15 UTC | 18h 6m |
| 2026-07-17 | FJL600 | - | Jul 17, 07:35 UTC | Jul 18, 06:15 UTC | 22h 41m |
| 2026-07-17 | FJL600 | - | Jul 17, 05:10 UTC | Jul 17, 19:05 UTC | 13h 55m |
| 2026-07-16 | FJL631 | - | Jul 16, 21:35 UTC | Jul 17, 19:05 UTC | 21h 30m |
| 2026-07-16 | FJL631 | - | Jul 16, 20:39 UTC | Jul 17, 19:05 UTC | 22h 25m |
| 2026-07-16 | FJL630 | - | Jul 16, 03:10 UTC | Jul 16, 18:59 UTC | 15h 50m |
| 2026-07-15 | FJL856 | - | Jul 15, 12:05 UTC | Jul 16, 11:30 UTC | 23h 25m |
| 2026-07-14 | FJL601 | - | Jul 14, 22:50 UTC | Jul 15, 10:40 UTC | 11h 50m |
| 2026-07-14 | FJL600 | - | Jul 14, 11:05 UTC | Jul 14, 22:45 UTC | 11h 39m |
| 2026-07-13 | FJL600 | - | Jul 13, 16:55 UTC | Jul 14, 09:40 UTC | 16h 45m |
| 2026-07-13 | FJL600 | - | Jul 13, 13:05 UTC | Jul 14, 09:40 UTC | 20h 35m |
| 2026-07-13 | FJL600 | - | Jul 13, 10:50 UTC | Jul 14, 06:10 UTC | 19h 20m |
| 2026-07-13 | FJL600 | - | Jul 13, 05:20 UTC | Jul 14, 03:30 UTC | 22h 10m |
| 2026-07-13 | FJL600 | - | Jul 13, 03:10 UTC | Jul 13, 23:30 UTC | 20h 20m |
| 2026-07-12 | FJL600 | - | Jul 12, 20:40 UTC | Jul 13, 17:55 UTC | 21h 15m |
| 2026-07-12 | FJL600 | - | Jul 12, 18:35 UTC | Jul 13, 17:30 UTC | 22h 55m |
| 2026-07-12 | FJL856 | - | Jul 12, 11:40 UTC | Jul 13, 05:31 UTC | 17h 50m |
| 2026-07-11 | FJL631 | - | Jul 11, 19:20 UTC | Jul 12, 10:15 UTC | 14h 55m |
| 2026-07-11 | FJL630 | - | Jul 11, 16:55 UTC | Jul 11, 18:00 UTC | 1h 5m |
| 2026-07-11 | FJL870 | - | Jul 11, 11:55 UTC | Jul 11, 12:10 UTC | 15m |
| 2026-07-11 | FJL856 | - | Jul 11, 06:50 UTC | Jul 11, 07:25 UTC | 35m |
| 2026-07-10 | FJL856 | - | Jul 10, 11:55 UTC | Jul 11, 05:31 UTC | 17h 36m |
| 2026-07-09 | FJL631 | - | Jul 9, 20:30 UTC | Jul 10, 10:35 UTC | 14h 5m |
| 2026-07-09 | FJL630 | - | Jul 9, 12:50 UTC | Jul 9, 18:00 UTC | 5h 10m |
| 2026-07-08 | FJL600 | - | Jul 8, 18:55 UTC | Jul 9, 11:15 UTC | 16h 20m |
| 2026-07-08 | FJL600 | - | Jul 8, 12:30 UTC | Jul 9, 11:15 UTC | 22h 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-BOV page for operator, model, and routing details .