sensors Mode-S transponder
06A00F
ICAO 24-bit transponder address · allocated to Qatar
Currently assigned to A7-AAG · AIRBUS A-320 · operated by Qatar Amiri Flight
- Hex
- 06A00F
- Octal
- 01520017
- Decimal
- 434,191
- Country
- QA
- Tail
- A7-AAG
- Type
- A320
- Flights observed
- 57
- Distinct callsigns
- 1
- Country
- QA
- Last broadcast
- 13h ago
Last known position
Country allocation
The ICAO 24-bit address 06A00F falls within the block assigned to Qatar (QA) by ICAO Annex 10, Volume III. Every aircraft registered in Qatar 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 1 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| QAF7 | - | 57 | 2026-07-17 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | QAF7 | - | Jul 17, 07:14 UTC | Jul 17, 12:50 UTC | 5h 35m |
| 2026-07-16 | QAF7 | DIA → NCE | Jul 16, 05:15 UTC | Jul 16, 11:30 UTC | 6h 15m |
| 2026-07-12 | QAF7 | MXP → DIA | Jul 12, 09:00 UTC | Jul 12, 14:45 UTC | 5h 45m |
| 2026-07-12 | QAF7 | DIA → MXP | Jul 12, 01:15 UTC | Jul 12, 07:01 UTC | 5h 45m |
| 2026-07-11 | QAF7 | ORY → DIA | Jul 11, 11:50 UTC | Jul 11, 18:05 UTC | 6h 15m |
| 2026-07-11 | QAF7 | - | Jul 11, 08:30 UTC | Jul 11, 08:50 UTC | 20m |
| 2026-07-09 | QAF7 | ORY → LBG | Jul 9, 15:00 UTC | Jul 9, 15:15 UTC | 15m |
| 2026-07-09 | QAF7 | ZRH → ORY | Jul 9, 13:00 UTC | Jul 9, 13:55 UTC | 55m |
| 2026-07-09 | QAF7 | - | Jul 9, 06:10 UTC | Jul 9, 07:45 UTC | 1h 35m |
| 2026-07-04 | QAF7 | - | Jul 4, 11:05 UTC | Jul 4, 11:45 UTC | 40m |
| 2026-07-04 | QAF7 | - | Jul 4, 07:40 UTC | Jul 4, 08:25 UTC | 45m |
| 2026-07-02 | QAF7 | - | Jul 2, 16:25 UTC | Jul 2, 16:45 UTC | 20m |
| 2026-07-02 | QAF7 | - | Jul 2, 09:30 UTC | Jul 2, 15:05 UTC | 5h 35m |
| 2026-06-29 | QAF7 | ZRH → DIA | Jun 29, 09:44 UTC | Jun 29, 15:34 UTC | 5h 50m |
| 2026-06-28 | QAF7 | DIA → ZRH | Jun 28, 06:59 UTC | Jun 28, 13:19 UTC | 6h 20m |
| 2026-06-25 | QAF7 | LBG → DIA | Jun 25, 11:35 UTC | Jun 25, 18:10 UTC | 6h 35m |
| 2026-06-24 | QAF7 | DIA → LBG | Jun 24, 09:59 UTC | Jun 24, 16:50 UTC | 6h 50m |
| 2026-06-11 | QAF7 | - | Jun 11, 10:05 UTC | Jun 11, 17:10 UTC | 7h 5m |
| 2026-06-10 | QAF7 | - | Jun 10, 12:15 UTC | Jun 10, 14:45 UTC | 2h 30m |
| 2026-06-10 | QAF7 | - | Jun 10, 08:00 UTC | Jun 10, 10:55 UTC | 2h 55m |
| 2026-06-10 | QAF7 | DIA → DIA | Jun 10, 05:10 UTC | Jun 10, 05:30 UTC | 20m |
| 2026-06-05 | QAF7 | - | Jun 5, 16:25 UTC | Jun 5, 16:35 UTC | 10m |
| 2026-06-05 | QAF7 | - | Jun 5, 12:30 UTC | Jun 5, 12:50 UTC | 20m |
| 2026-06-05 | QAF7 | - | Jun 5, 09:30 UTC | Jun 5, 09:55 UTC | 25m |
| 2026-06-05 | QAF7 | - | Jun 5, 06:25 UTC | Jun 5, 07:15 UTC | 50m |
| 2026-05-28 | QAF7 | - | May 28, 21:00 UTC | May 29, 03:30 UTC | 6h 30m |
| 2026-05-28 | QAF7 | - | May 28, 14:05 UTC | May 28, 15:55 UTC | 1h 50m |
| 2026-05-28 | QAF7 | - | May 28, 05:55 UTC | May 28, 12:35 UTC | 6h 40m |
| 2026-05-25 | QAF7 | - | May 25, 11:45 UTC | May 25, 18:15 UTC | 6h 30m |
| 2026-05-24 | QAF7 | - | May 24, 09:50 UTC | May 24, 14:05 UTC | 4h 15m |
| 2026-05-16 | QAF7 | - | May 16, 10:55 UTC | May 16, 15:45 UTC | 4h 50m |
| 2026-05-13 | QAF7 | - | May 13, 10:05 UTC | May 13, 13:35 UTC | 3h 30m |
| 2026-05-12 | QAF7 | - | May 12, 18:40 UTC | May 13, 00:40 UTC | 6h 0m |
| 2026-05-12 | QAF7 | AMM → LBG | May 12, 12:25 UTC | May 12, 17:10 UTC | 4h 45m |
| 2026-05-02 | QAF7 | - | May 2, 08:15 UTC | May 2, 13:40 UTC | 5h 25m |
| 2026-05-01 | QAF7 | - | May 1, 06:00 UTC | May 1, 12:55 UTC | 6h 55m |
| 2026-04-29 | QAF7 | ATH → DIA | Apr 29, 10:15 UTC | Apr 29, 14:20 UTC | 4h 5m |
| 2026-04-28 | QAF7 | - | Apr 28, 13:55 UTC | Apr 28, 15:50 UTC | 1h 55m |
| 2026-04-27 | QAF7 | - | Apr 27, 09:55 UTC | Apr 27, 10:40 UTC | 45m |
| 2026-04-26 | QAF7 | - | Apr 26, 10:25 UTC | Apr 26, 16:00 UTC | 5h 35m |
| 2026-04-26 | QAF7 | - | Apr 26, 07:50 UTC | Apr 26, 08:40 UTC | 50m |
| 2026-04-26 | QAF7 | - | Apr 26, 03:10 UTC | Apr 26, 06:20 UTC | 3h 10m |
| 2026-04-24 | QAF7 | - | Apr 24, 15:20 UTC | Apr 24, 18:15 UTC | 2h 55m |
| 2026-04-24 | QAF7 | - | Apr 24, 03:05 UTC | Apr 24, 08:55 UTC | 5h 50m |
| 2026-04-17 | QAF7 | - | Apr 17, 16:20 UTC | Apr 17, 16:55 UTC | 35m |
| 2026-04-17 | QAF7 | - | Apr 17, 13:20 UTC | Apr 17, 13:30 UTC | 10m |
| 2026-04-17 | QAF7 | - | Apr 17, 11:20 UTC | Apr 17, 13:15 UTC | 1h 55m |
| 2026-04-17 | QAF7 | - | Apr 17, 10:55 UTC | Apr 17, 11:15 UTC | 20m |
| 2026-04-17 | QAF7 | - | Apr 17, 09:20 UTC | Apr 17, 09:30 UTC | 10m |
| 2026-04-17 | QAF7 | - | Apr 17, 08:00 UTC | Apr 17, 09:15 UTC | 1h 15m |
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 A7-AAG page for operator, model, and routing details .