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
- 249
- Distinct callsigns
- 20
- Country
- PK
- Last broadcast
- 5h ago
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 |
|---|---|---|---|
| FJL601 | Fly Jinnah | 29 | 2026-07-06 |
| FJL600 | - | 28 | 2026-07-13 |
| FJL581 | Fly Jinnah | 14 | 2026-06-15 |
| FJL514 | Fly Jinnah | 14 | 2026-06-15 |
| FJL843 | - | 13 | 2026-06-17 |
| FJL856 | - | 12 | 2026-07-12 |
| FJL580 | Fly Jinnah | 12 | 2026-06-07 |
| FJL570 | Fly Jinnah | 12 | 2026-05-23 |
| FJL841 | - | 11 | 2026-06-17 |
| FJL502 | Fly Jinnah | 9 | 2026-06-16 |
| FJL586 | Fly Jinnah | 8 | 2026-06-04 |
| FJL500 | Fly Jinnah | 8 | 2026-06-16 |
| FJL711 | Fly Jinnah | 7 | 2026-05-09 |
| FJL571 | Fly Jinnah | 7 | 2026-06-02 |
| FJL870 | - | 6 | 2026-07-11 |
| FJL871 | - | 5 | 2026-07-01 |
| FJL700 | Fly Jinnah | 5 | 2026-05-08 |
| FJL847 | Fly Jinnah | 4 | 2026-06-14 |
| FJL587 | Fly Jinnah | 4 | 2026-06-03 |
| FJL855 | - | 3 | 2026-07-01 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | FJL845 | - | Jul 14, 11:05 UTC | Jul 14, 11:35 UTC | 30m |
| 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 |
| 2026-07-07 | FJL631 | - | Jul 7, 19:15 UTC | Jul 8, 11:10 UTC | 15h 55m |
| 2026-07-06 | FJL630 | - | Jul 6, 23:35 UTC | Jul 7, 18:00 UTC | 18h 25m |
| 2026-07-06 | FJL601 | JED → KHI | Jul 6, 22:45 UTC | Jul 7, 18:00 UTC | 19h 15m |
| 2026-07-06 | FJL601 | JED → KHI | Jul 6, 17:35 UTC | Jul 7, 17:30 UTC | 23h 55m |
| 2026-07-06 | FJL601 | JED → KHI | Jul 6, 13:15 UTC | Jul 7, 10:35 UTC | 21h 20m |
| 2026-07-06 | FJL601 | JED → KHI | Jul 6, 10:50 UTC | Jul 7, 08:30 UTC | 21h 40m |
| 2026-07-06 | FJL601 | JED → KHI | Jul 6, 05:35 UTC | Jul 6, 23:50 UTC | 18h 15m |
| 2026-07-06 | FJL601 | JED → KHI | Jul 6, 03:15 UTC | Jul 6, 23:50 UTC | 20h 35m |
| 2026-07-05 | FJL600 | - | Jul 5, 20:55 UTC | Jul 6, 18:25 UTC | 21h 30m |
| 2026-07-05 | FJL670 | - | Jul 5, 18:40 UTC | Jul 6, 13:25 UTC | 18h 45m |
| 2026-07-05 | FJL856 | - | Jul 5, 11:50 UTC | Jul 6, 11:00 UTC | 23h 10m |
| 2026-07-04 | FJL600 | - | Jul 4, 17:15 UTC | Jul 5, 10:30 UTC | 17h 15m |
| 2026-07-04 | FJL600 | - | Jul 4, 13:00 UTC | Jul 5, 10:30 UTC | 21h 30m |
| 2026-07-04 | FJL600 | - | Jul 4, 10:55 UTC | Jul 5, 05:40 UTC | 18h 45m |
| 2026-07-04 | FJL600 | - | Jul 4, 05:40 UTC | Jul 5, 05:30 UTC | 23h 50m |
| 2026-07-04 | FJL600 | - | Jul 4, 03:35 UTC | Jul 5, 03:25 UTC | 23h 50m |
| 2026-07-03 | FJL601 | JED → KHI | Jul 3, 23:35 UTC | Jul 4, 23:30 UTC | 23h 55m |
| 2026-07-03 | FJL600 | - | Jul 3, 22:50 UTC | Jul 4, 18:10 UTC | 19h 20m |
| 2026-07-03 | FJL601 | JED → KHI | Jul 3, 17:35 UTC | Jul 4, 17:30 UTC | 23h 55m |
| 2026-07-03 | FJL601 | JED → KHI | Jul 3, 17:10 UTC | Jul 4, 13:10 UTC | 20h 0m |
| 2026-07-03 | FJL601 | JED → KHI | Jul 3, 13:00 UTC | Jul 4, 11:05 UTC | 22h 5m |
| 2026-07-03 | FJL601 | JED → KHI | Jul 3, 10:45 UTC | Jul 4, 05:50 UTC | 19h 5m |
| 2026-07-03 | FJL601 | JED → KHI | Jul 3, 07:35 UTC | Jul 4, 05:50 UTC | 22h 15m |
| 2026-07-03 | FJL601 | JED → KHI | Jul 3, 05:00 UTC | Jul 3, 23:55 UTC | 18h 55m |
| 2026-07-02 | FJL601 | JED → KHI | Jul 2, 23:40 UTC | Jul 3, 23:30 UTC | 23h 50m |
| 2026-07-02 | FJL601 | JED → KHI | Jul 2, 23:05 UTC | Jul 3, 18:05 UTC | 19h 0m |
| 2026-07-02 | FJL600 | - | Jul 2, 17:35 UTC | Jul 3, 17:30 UTC | 23h 55m |
| 2026-07-02 | FJL600 | - | Jul 2, 13:35 UTC | Jul 3, 13:15 UTC | 23h 40m |
| 2026-07-02 | FJL600 | - | Jul 2, 13:25 UTC | Jul 3, 11:00 UTC | 21h 35m |
| 2026-07-02 | FJL600 | - | Jul 2, 11:10 UTC | Jul 3, 07:35 UTC | 20h 25m |
| 2026-07-02 | FJL600 | - | Jul 2, 05:45 UTC | Jul 3, 05:05 UTC | 23h 20m |
| 2026-07-02 | FJL600 | - | Jul 2, 03:10 UTC | Jul 3, 00:05 UTC | 20h 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-BOV page for operator, model, and routing details .