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