sensors Mode-S transponder
06A0F4
ICAO 24-bit transponder address · allocated to Qatar
Currently assigned to A7-ANT · AIRBUS A-350-1000
- Hex
- 06A0F4
- Octal
- 01520364
- Decimal
- 434,420
- Country
- QA
- Tail
- A7-ANT
- Type
- A35K
- Flights observed
- 147
- Distinct callsigns
- 20
- Country
- QA
- Last broadcast
- 12h ago
Last known position
Country allocation
The ICAO 24-bit address 06A0F4 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 |
|---|---|---|---|
| QTR40X | - | 9 | 2026-06-08 |
| QTR18F | Qatar Airways | 7 | 2026-06-01 |
| QTR73V | - | 6 | 2026-07-10 |
| QTR65R | Qatar Airways | 6 | 2026-06-02 |
| QTR35P | Qatar Airways | 6 | 2026-07-03 |
| QTR90B | Qatar Airways | 5 | 2026-07-03 |
| QTR87Q | - | 5 | 2026-07-14 |
| QTR5Q | - | 5 | 2026-07-09 |
| QTR58G | - | 5 | 2026-07-11 |
| QTR20V | - | 5 | 2026-07-13 |
| QTR818 | Qatar Airways | 4 | 2026-05-04 |
| QTR815 | Qatar Airways | 4 | 2026-05-04 |
| QTR780 | Qatar Airways | 4 | 2026-06-05 |
| QTR779 | Qatar Airways | 4 | 2026-06-05 |
| QTR4U | Qatar Airways | 4 | 2026-04-20 |
| QTR27R | - | 4 | 2026-06-09 |
| QTR22B | - | 4 | 2026-06-27 |
| QTR93W | - | 3 | 2026-07-10 |
| QTR7E | - | 3 | 2026-07-14 |
| QTR70E | - | 3 | 2026-06-26 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-16 | QTR3V | DOH → MIA | Jul 16, 23:10 UTC | Jul 17, 13:55 UTC | 14h 45m |
| 2026-07-16 | QTR51U | - | Jul 16, 05:05 UTC | Jul 16, 19:40 UTC | 14h 35m |
| 2026-07-14 | QTR7E | - | Jul 14, 23:15 UTC | Jul 15, 14:35 UTC | 15h 20m |
| 2026-07-14 | QTR87Q | ORD → DOH | Jul 14, 01:20 UTC | Jul 14, 14:55 UTC | 13h 35m |
| 2026-07-13 | QTR20V | - | Jul 13, 06:15 UTC | Jul 13, 20:25 UTC | 14h 10m |
| 2026-07-12 | QTR1G | DST → DOH | Jul 12, 19:30 UTC | Jul 12, 20:20 UTC | 50m |
| 2026-07-12 | QTR9R | - | Jul 12, 16:35 UTC | Jul 12, 17:25 UTC | 50m |
| 2026-07-11 | QTR1X | - | Jul 11, 23:40 UTC | Jul 12, 12:25 UTC | 12h 45m |
| 2026-07-11 | QTR58G | - | Jul 11, 05:20 UTC | Jul 11, 20:45 UTC | 15h 25m |
| 2026-07-10 | QTR65B | - | Jul 10, 23:25 UTC | Jul 11, 02:10 UTC | 2h 45m |
| 2026-07-10 | QTR93W | - | Jul 10, 18:05 UTC | Jul 10, 21:10 UTC | 3h 6m |
| 2026-07-10 | QTR73V | - | Jul 10, 15:35 UTC | Jul 10, 15:50 UTC | 15m |
| 2026-07-10 | QTR73V | - | Jul 10, 00:30 UTC | Jul 10, 13:50 UTC | 13h 20m |
| 2026-07-09 | QTR5Q | - | Jul 9, 07:15 UTC | Jul 9, 21:30 UTC | 14h 15m |
| 2026-07-09 | QTR5Q | - | Jul 9, 05:20 UTC | Jul 9, 06:00 UTC | 40m |
| 2026-07-08 | QTR51U | DFW → DOH | Jul 8, 05:05 UTC | Jul 8, 19:40 UTC | 14h 35m |
| 2026-07-06 | QTR7E | MAD → BSL | Jul 6, 23:10 UTC | Jul 7, 14:45 UTC | 15h 35m |
| 2026-07-06 | QTR87Q | ORD → DOH | Jul 6, 00:55 UTC | Jul 6, 13:40 UTC | 12h 45m |
| 2026-07-05 | QTR20V | - | Jul 5, 05:40 UTC | Jul 5, 20:00 UTC | 14h 20m |
| 2026-07-05 | QTR1157 | - | Jul 5, 02:25 UTC | Jul 5, 03:00 UTC | 35m |
| 2026-07-04 | QTR1156 | - | Jul 4, 23:45 UTC | Jul 5, 00:15 UTC | 30m |
| 2026-07-03 | QTR35P | BUD → DOH | Jul 3, 23:55 UTC | Jul 4, 15:10 UTC | 15h 15m |
| 2026-07-03 | QTR90B | CPT → DOH | Jul 3, 05:25 UTC | Jul 3, 21:15 UTC | 15h 50m |
| 2026-07-02 | QTR92E | - | Jul 2, 23:55 UTC | Jul 3, 02:20 UTC | 2h 25m |
| 2026-07-02 | QTR90T | - | Jul 2, 18:30 UTC | Jul 2, 21:00 UTC | 2h 30m |
| 2026-07-01 | QTR51U | DFW → DOH | Jul 1, 04:40 UTC | Jul 1, 19:00 UTC | 14h 20m |
| 2026-06-29 | QTR7E | MAD → BSL | Jun 29, 23:09 UTC | Jun 30, 14:15 UTC | 15h 5m |
| 2026-06-28 | QTR35P | BUD → DOH | Jun 28, 23:44 UTC | Jun 29, 15:24 UTC | 15h 40m |
| 2026-06-28 | QTR90B | CPT → DOH | Jun 28, 08:44 UTC | Jun 28, 20:34 UTC | 11h 50m |
| 2026-06-27 | QTR1169 | - | Jun 27, 20:49 UTC | Jun 27, 21:29 UTC | 40m |
| 2026-06-27 | QTR1168 | - | Jun 27, 17:29 UTC | Jun 27, 17:55 UTC | 25m |
| 2026-06-27 | QTR22B | - | Jun 27, 13:44 UTC | Jun 27, 14:14 UTC | 30m |
| 2026-06-27 | QTR22B | - | Jun 27, 00:00 UTC | Jun 27, 11:44 UTC | 11h 45m |
| 2026-06-26 | QTR70E | - | Jun 26, 05:19 UTC | Jun 26, 20:34 UTC | 15h 15m |
| 2026-06-25 | QTR1183 | DOH → DOH | Jun 25, 20:45 UTC | Jun 26, 02:20 UTC | 5h 35m |
| 2026-06-25 | QTR73V | SFO → DOH | Jun 25, 00:35 UTC | Jun 25, 12:25 UTC | 11h 50m |
| 2026-06-24 | QTR5Q | SAW → DOH | Jun 24, 05:05 UTC | Jun 24, 21:04 UTC | 16h 0m |
| 2026-06-23 | QTR35P | BUD → DOH | Jun 23, 00:09 UTC | Jun 23, 15:55 UTC | 15h 45m |
| 2026-06-22 | QTR90B | CPT → DOH | Jun 22, 05:40 UTC | Jun 22, 21:40 UTC | 16h 0m |
| 2026-06-21 | QTR65B | - | Jun 21, 22:54 UTC | Jun 22, 01:44 UTC | 2h 50m |
| 2026-06-21 | QTR93W | DOH → BOM | Jun 21, 17:54 UTC | Jun 21, 20:54 UTC | 3h 0m |
| 2026-06-20 | QTR73V | SFO → DOH | Jun 20, 23:45 UTC | Jun 21, 15:15 UTC | 15h 30m |
| 2026-06-20 | QTR5Q | SAW → DOH | Jun 20, 05:04 UTC | Jun 20, 20:45 UTC | 15h 40m |
| 2026-06-18 | QTR1X | DOH → LHR | Jun 18, 23:55 UTC | Jun 19, 14:34 UTC | 14h 39m |
| 2026-06-18 | QTR58G | DOH → IAH | Jun 18, 05:10 UTC | Jun 18, 20:55 UTC | 15h 45m |
| 2026-06-17 | QTR1155 | DMM → DOH | Jun 17, 19:55 UTC | Jun 17, 20:30 UTC | 35m |
| 2026-06-17 | QTR1154 | DOH → DMM | Jun 17, 17:10 UTC | Jun 17, 17:40 UTC | 30m |
| 2026-06-17 | QTR714 | - | Jun 17, 00:05 UTC | Jun 17, 14:20 UTC | 14h 15m |
| 2026-06-16 | QTR58G | DOH → IAH | Jun 16, 07:55 UTC | Jun 16, 21:15 UTC | 13h 21m |
| 2026-06-15 | QTR58G | DOH → IAH | Jun 15, 15:04 UTC | Jun 16, 14:15 UTC | 23h 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 A7-ANT page for operator, model, and routing details .