sensors Mode-S transponder
7609E4
ICAO 24-bit transponder address · allocated to Pakistan
Currently assigned to AP-BOD · AIRBUS A-321neo
- Hex
- 7609E4
- Octal
- 35404744
- Decimal
- 7,735,780
- Country
- PK
- Tail
- AP-BOD
- Type
- A21N
- Flights observed
- 102
- Distinct callsigns
- 15
- Country
- PK
- Last broadcast
- 11h ago
Last known position
Country allocation
The ICAO 24-bit address 7609E4 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 15 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| ABQ216 | - | 33 | 2026-07-11 |
| ABQ217 | Airblue | 15 | 2026-06-26 |
| ABQ230 | - | 9 | 2026-07-13 |
| ABQ212 | - | 9 | 2026-07-11 |
| ABQ213 | - | 8 | 2026-06-30 |
| ABQ210 | - | 6 | 2026-07-10 |
| ABQ218 | Airblue | 5 | 2026-06-06 |
| ABQ231 | - | 4 | 2026-07-13 |
| ABQ211 | - | 4 | 2026-07-13 |
| ABQ200 | Airblue | 3 | 2026-05-29 |
| ABQ219 | Airblue | 2 | 2026-06-11 |
| ABQ286 | - | 1 | 2026-04-15 |
| ABQ279 | - | 1 | 2026-04-16 |
| ABQ214 | Airblue | 1 | 2026-05-04 |
| ABQ208 | Airblue | 1 | 2026-05-29 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | ABQ231 | - | Jul 13, 23:50 UTC | Jul 14, 00:00 UTC | 10m |
| 2026-07-13 | ABQ230 | - | Jul 13, 03:15 UTC | Jul 13, 21:40 UTC | 18h 25m |
| 2026-07-13 | ABQ211 | - | Jul 13, 01:10 UTC | Jul 13, 21:40 UTC | 20h 30m |
| 2026-07-11 | ABQ212 | - | Jul 11, 19:35 UTC | Jul 12, 09:35 UTC | 14h 0m |
| 2026-07-11 | ABQ216 | - | Jul 11, 10:25 UTC | Jul 11, 12:45 UTC | 2h 20m |
| 2026-07-10 | ABQ210 | - | Jul 10, 19:55 UTC | Jul 10, 22:10 UTC | 2h 15m |
| 2026-07-10 | ABQ216 | - | Jul 10, 00:45 UTC | Jul 10, 12:50 UTC | 12h 5m |
| 2026-06-30 | ABQ213 | - | Jun 30, 11:30 UTC | Jun 30, 13:45 UTC | 2h 15m |
| 2026-06-30 | ABQ211 | - | Jun 30, 01:09 UTC | Jun 30, 01:40 UTC | 31m |
| 2026-06-29 | ABQ216 | - | Jun 29, 10:24 UTC | Jun 29, 12:45 UTC | 2h 20m |
| 2026-06-28 | ABQ216 | - | Jun 28, 10:30 UTC | Jun 28, 12:50 UTC | 2h 20m |
| 2026-06-27 | ABQ230 | - | Jun 27, 19:19 UTC | Jun 27, 21:40 UTC | 2h 20m |
| 2026-06-26 | ABQ217 | DXB → ISB | Jun 26, 14:59 UTC | Jun 26, 17:15 UTC | 2h 15m |
| 2026-06-25 | ABQ217 | DXB → ISB | Jun 25, 14:44 UTC | Jun 25, 22:10 UTC | 7h 25m |
| 2026-06-24 | ABQ216 | - | Jun 24, 10:30 UTC | Jun 24, 12:50 UTC | 2h 20m |
| 2026-06-23 | ABQ216 | - | Jun 23, 13:29 UTC | Jun 24, 12:50 UTC | 23h 20m |
| 2026-06-23 | ABQ213 | - | Jun 23, 11:19 UTC | Jun 24, 10:35 UTC | 23h 15m |
| 2026-06-22 | ABQ230 | - | Jun 22, 10:05 UTC | Jun 22, 21:40 UTC | 11h 35m |
| 2026-06-21 | ABQ217 | DXB → ISB | Jun 21, 14:34 UTC | Jun 21, 15:05 UTC | 30m |
| 2026-06-18 | ABQ212 | ISB → SHJ | Jun 18, 16:50 UTC | Jun 19, 07:19 UTC | 14h 29m |
| 2026-06-18 | ABQ217 | DXB → ISB | Jun 18, 14:40 UTC | Jun 18, 15:10 UTC | 30m |
| 2026-06-17 | ABQ210 | - | Jun 17, 16:45 UTC | Jun 18, 01:20 UTC | 8h 35m |
| 2026-06-17 | ABQ217 | DXB → ISB | Jun 17, 14:35 UTC | Jun 17, 15:05 UTC | 30m |
| 2026-06-15 | ABQ216 | - | Jun 15, 10:24 UTC | Jun 15, 19:50 UTC | 9h 25m |
| 2026-06-13 | ABQ230 | - | Jun 13, 18:00 UTC | Jun 14, 07:25 UTC | 13h 26m |
| 2026-06-13 | ABQ216 | - | Jun 13, 12:05 UTC | Jun 14, 07:25 UTC | 19h 21m |
| 2026-06-12 | ABQ213 | SHJ → ISB | Jun 12, 23:20 UTC | Jun 13, 21:00 UTC | 21h 39m |
| 2026-06-12 | ABQ213 | SHJ → ISB | Jun 12, 21:20 UTC | Jun 12, 21:45 UTC | 25m |
| 2026-06-12 | ABQ213 | SHJ → ISB | Jun 12, 19:25 UTC | Jun 12, 19:40 UTC | 15m |
| 2026-06-11 | ABQ219 | DXB → ISB | Jun 11, 19:40 UTC | Jun 12, 12:10 UTC | 16h 30m |
| 2026-06-11 | ABQ219 | DXB → ISB | Jun 11, 16:30 UTC | Jun 12, 12:10 UTC | 19h 41m |
| 2026-06-09 | ABQ216 | ISB → DXB | Jun 9, 17:20 UTC | Jun 10, 10:50 UTC | 17h 30m |
| 2026-06-08 | ABQ217 | DXB → ISB | Jun 8, 19:50 UTC | Jun 9, 17:25 UTC | 21h 35m |
| 2026-06-07 | ABQ212 | ISB → SHJ | Jun 7, 07:15 UTC | Jun 7, 19:45 UTC | 12h 30m |
| 2026-06-06 | ABQ218 | ISB → DXB | Jun 6, 20:14 UTC | Jun 7, 07:20 UTC | 11h 5m |
| 2026-06-06 | ABQ211 | DXB → ISB | Jun 6, 02:10 UTC | Jun 6, 20:19 UTC | 18h 10m |
| 2026-06-05 | ABQ211 | DXB → ISB | Jun 5, 10:35 UTC | Jun 6, 02:15 UTC | 15h 40m |
| 2026-06-04 | ABQ218 | ISB → DXB | Jun 4, 16:55 UTC | Jun 5, 10:35 UTC | 17h 40m |
| 2026-06-02 | ABQ216 | ISB → DXB | Jun 2, 19:55 UTC | Jun 3, 10:40 UTC | 14h 45m |
| 2026-06-01 | ABQ217 | DXB → ISB | Jun 1, 16:45 UTC | Jun 2, 07:25 UTC | 14h 40m |
| 2026-05-29 | ABQ208 | KHI → ISB | May 29, 16:10 UTC | May 30, 10:45 UTC | 18h 35m |
| 2026-05-29 | ABQ200 | KHI → ISB | May 29, 08:50 UTC | May 29, 16:20 UTC | 7h 31m |
| 2026-05-28 | ABQ200 | KHI → ISB | May 28, 19:20 UTC | May 29, 16:20 UTC | 21h 1m |
| 2026-05-28 | ABQ200 | KHI → ISB | May 28, 12:35 UTC | May 29, 09:05 UTC | 20h 30m |
| 2026-05-27 | ABQ216 | ISB → DXB | May 27, 10:30 UTC | May 27, 10:40 UTC | 10m |
| 2026-05-26 | ABQ216 | ISB → DXB | May 26, 13:19 UTC | May 27, 10:40 UTC | 21h 20m |
| 2026-05-26 | ABQ212 | ISB → SHJ | May 26, 07:05 UTC | May 26, 13:24 UTC | 6h 20m |
| 2026-05-25 | ABQ212 | ISB → SHJ | May 25, 17:10 UTC | May 26, 13:24 UTC | 20h 15m |
| 2026-05-23 | ABQ230 | ISB → AUH | May 23, 19:15 UTC | May 24, 07:25 UTC | 12h 10m |
| 2026-05-23 | ABQ216 | ISB → DXB | May 23, 10:15 UTC | May 24, 07:25 UTC | 21h 10m |
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-BOD page for operator, model, and routing details .