sensors Mode-S transponder
06A115
ICAO 24-bit transponder address · allocated to Qatar
Currently assigned to A7-AOG · AIRBUS A-350-1000
- Hex
- 06A115
- Octal
- 01520425
- Decimal
- 434,453
- Country
- QA
- Tail
- A7-AOG
- Type
- A35K
- Flights observed
- 83
- Distinct callsigns
- 20
- Country
- QA
- Last broadcast
- 2h ago
Last known position
Country allocation
The ICAO 24-bit address 06A115 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 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| QTR65U | Qatar Airways | 12 | 2026-05-26 |
| QTR50J | Qatar Airways | 9 | 2026-05-27 |
| QTR98E | - | 6 | 2026-05-28 |
| QTR962 | Qatar Airways | 6 | 2026-05-29 |
| QTR76W | Qatar Airways | 5 | 2026-05-18 |
| QTR5X | Qatar Airways | 5 | 2026-05-28 |
| QTR53W | Qatar Airways | 5 | 2026-05-19 |
| QTR960 | Qatar Airways | 4 | 2026-05-24 |
| QTR74X | - | 4 | 2026-05-23 |
| QTR963 | - | 3 | 2026-04-15 |
| QTR91F | Qatar Airways | 3 | 2026-04-28 |
| QTR7R | Qatar Airways | 3 | 2026-04-20 |
| QTR66Y | - | 3 | 2026-05-16 |
| QTR961 | Qatar Airways | 2 | 2026-04-18 |
| QTR6W | Qatar Airways | 2 | 2026-05-05 |
| QTR620 | Qatar Airways | 2 | 2026-05-17 |
| QTR2J | Qatar Airways | 2 | 2026-05-08 |
| QTR1P | Qatar Airways | 2 | 2026-04-16 |
| QTR74N | Qatar Airways | 1 | 2026-04-28 |
| QTR49F | Qatar Airways | 1 | 2026-04-27 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | QTR962 | DOH → DPS | May 29, 06:10 UTC | May 30, 03:05 UTC | 20h 55m |
| 2026-05-29 | QTR962 | DOH → DPS | May 29, 02:10 UTC | May 29, 16:35 UTC | 14h 25m |
| 2026-05-28 | QTR98E | - | May 28, 20:10 UTC | May 28, 20:45 UTC | 35m |
| 2026-05-28 | QTR98E | - | May 28, 15:15 UTC | May 28, 18:20 UTC | 3h 5m |
| 2026-05-28 | QTR5X | DOH → ALG | May 28, 05:15 UTC | May 28, 11:15 UTC | 6h 0m |
| 2026-05-27 | QTR50J | YYZ → DOH | May 27, 13:15 UTC | May 27, 13:45 UTC | 30m |
| 2026-05-27 | QTR50J | YYZ → DOH | May 27, 01:14 UTC | May 27, 11:15 UTC | 10h 1m |
| 2026-05-26 | QTR65U | LHR → DOH | May 26, 09:49 UTC | May 26, 21:00 UTC | 11h 10m |
| 2026-05-25 | QTR65U | LHR → DOH | May 25, 21:49 UTC | May 26, 21:00 UTC | 23h 10m |
| 2026-05-25 | QTR65U | LHR → DOH | May 25, 17:50 UTC | May 26, 14:55 UTC | 21h 5m |
| 2026-05-24 | QTR960 | DOH → DPS | May 24, 20:00 UTC | May 25, 18:05 UTC | 22h 5m |
| 2026-05-23 | QTR74X | - | May 23, 15:00 UTC | May 23, 19:20 UTC | 4h 20m |
| 2026-05-22 | QTR98E | - | May 22, 19:50 UTC | May 22, 20:30 UTC | 40m |
| 2026-05-22 | QTR98E | - | May 22, 14:50 UTC | May 22, 17:55 UTC | 3h 5m |
| 2026-05-21 | QTR5X | DOH → ALG | May 21, 23:20 UTC | May 22, 11:05 UTC | 11h 45m |
| 2026-05-20 | QTR98E | - | May 20, 19:55 UTC | May 20, 20:35 UTC | 40m |
| 2026-05-20 | QTR98E | - | May 20, 15:15 UTC | May 20, 18:00 UTC | 2h 45m |
| 2026-05-19 | QTR5X | DOH → ALG | May 19, 20:00 UTC | May 20, 11:55 UTC | 15h 56m |
| 2026-05-19 | QTR53W | DOH → CPH | May 19, 02:00 UTC | May 19, 13:45 UTC | 11h 45m |
| 2026-05-18 | QTR76W | DOH → YUL | May 18, 07:20 UTC | May 18, 19:30 UTC | 12h 9m |
| 2026-05-17 | QTR76W | DOH → YUL | May 17, 23:10 UTC | May 18, 19:30 UTC | 20h 19m |
| 2026-05-17 | QTR620 | DOH → LHE | May 17, 06:20 UTC | May 17, 20:25 UTC | 14h 5m |
| 2026-05-16 | QTR74X | - | May 16, 15:01 UTC | May 16, 21:00 UTC | 5h 59m |
| 2026-05-16 | QTR66Y | - | May 16, 05:25 UTC | May 16, 12:45 UTC | 7h 21m |
| 2026-05-15 | QTR5X | DOH → ALG | May 15, 07:45 UTC | May 15, 20:10 UTC | 12h 24m |
| 2026-05-14 | QTR5X | DOH → ALG | May 14, 05:50 UTC | May 14, 21:00 UTC | 15h 10m |
| 2026-05-13 | QTR50J | YYZ → DOH | May 13, 01:15 UTC | May 13, 12:55 UTC | 11h 40m |
| 2026-05-12 | QTR65U | LHR → DOH | May 12, 14:40 UTC | May 12, 20:01 UTC | 5h 20m |
| 2026-05-11 | QTR74X | - | May 11, 15:00 UTC | May 11, 21:10 UTC | 6h 10m |
| 2026-05-11 | QTR66Y | - | May 11, 07:45 UTC | May 11, 12:20 UTC | 4h 35m |
| 2026-05-10 | QTR50J | YYZ → DOH | May 10, 01:09 UTC | May 10, 13:10 UTC | 12h 0m |
| 2026-05-09 | QTR65U | LHR → DOH | May 9, 06:50 UTC | May 9, 20:44 UTC | 13h 55m |
| 2026-05-08 | QTR2J | DOH → DFW | May 8, 18:10 UTC | May 8, 23:40 UTC | 5h 30m |
| 2026-05-07 | QTR53W | DOH → CPH | May 7, 01:55 UTC | May 7, 13:55 UTC | 12h 0m |
| 2026-05-05 | QTR2J | DOH → DFW | May 5, 17:50 UTC | May 5, 18:05 UTC | 15m |
| 2026-05-05 | QTR6W | ORD → DOH | May 5, 06:40 UTC | May 5, 09:50 UTC | 3h 10m |
| 2026-05-04 | QTR74X | - | May 4, 15:15 UTC | May 4, 21:35 UTC | 6h 21m |
| 2026-05-04 | QTR66Y | - | May 4, 05:20 UTC | May 4, 12:50 UTC | 7h 30m |
| 2026-05-03 | QTR1T | BHX → DOH | May 3, 18:00 UTC | May 4, 01:55 UTC | 7h 55m |
| 2026-05-03 | QTR6W | ORD → DOH | May 3, 00:40 UTC | May 3, 09:00 UTC | 8h 19m |
| 2026-05-02 | QTR50J | YYZ → DOH | May 2, 01:35 UTC | May 2, 13:50 UTC | 12h 15m |
| 2026-05-01 | QTR65U | LHR → DOH | May 1, 07:00 UTC | May 1, 20:35 UTC | 13h 35m |
| 2026-04-30 | QTR962 | DOH → DPS | Apr 30, 01:35 UTC | Apr 30, 19:55 UTC | 18h 20m |
| 2026-04-29 | QTR962 | DOH → DPS | Apr 29, 23:40 UTC | Apr 30, 19:55 UTC | 20h 15m |
| 2026-04-28 | QTR91F | DOH → MAN | Apr 28, 17:55 UTC | Apr 29, 02:15 UTC | 8h 20m |
| 2026-04-28 | QTR74N | DOH → MEL | Apr 28, 06:40 UTC | Apr 28, 09:35 UTC | 2h 55m |
| 2026-04-27 | QTR49F | CDG → DOH | Apr 27, 23:10 UTC | Apr 28, 02:35 UTC | 3h 25m |
| 2026-04-27 | QTR53W | DOH → CPH | Apr 27, 02:30 UTC | Apr 27, 14:20 UTC | 11h 50m |
| 2026-04-26 | QTR76W | DOH → YUL | Apr 26, 06:20 UTC | Apr 26, 19:25 UTC | 13h 5m |
| 2026-04-24 | QTR004 | - | Apr 24, 14:25 UTC | Apr 24, 20:45 UTC | 6h 20m |
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-AOG page for operator, model, and routing details .