sensors Mode-S transponder
06A12F
ICAO 24-bit transponder address · allocated to Qatar
Currently assigned to A7-ANS · AIRBUS A-350-1000
- Hex
- 06A12F
- Octal
- 01520457
- Decimal
- 434,479
- Country
- QA
- Tail
- A7-ANS
- Type
- A35K
- Flights observed
- 90
- Distinct callsigns
- 20
- Country
- QA
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address 06A12F 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 |
|---|---|---|---|
| QTR003 | - | 10 | 2026-05-28 |
| QTR004 | - | 9 | 2026-05-28 |
| QTR65R | Qatar Airways | 6 | 2026-05-13 |
| QTR40X | - | 5 | 2026-05-24 |
| QTR17E | - | 5 | 2026-05-08 |
| QTR778 | Qatar Airways | 4 | 2026-05-20 |
| QTR87Q | Qatar Airways | 3 | 2026-05-17 |
| QTR65B | Qatar Airways | 3 | 2026-05-20 |
| QTR572 | Qatar Airways | 3 | 2026-05-13 |
| QTR32N | Qatar Airways | 3 | 2026-05-13 |
| QTR98P | Qatar Airways | 2 | 2026-05-02 |
| QTR93W | Qatar Airways | 2 | 2026-04-27 |
| QTR93V | Qatar Airways | 2 | 2026-05-04 |
| QTR706 | Qatar Airways | 2 | 2026-05-23 |
| QTR6W | Qatar Airways | 2 | 2026-04-18 |
| QTR52N | Qatar Airways | 2 | 2026-04-23 |
| QTR4E | Qatar Airways | 2 | 2026-05-07 |
| QTR47Y | Qatar Airways | 2 | 2026-05-11 |
| QTR27R | - | 2 | 2026-05-25 |
| QTR20V | Qatar Airways | 2 | 2026-05-01 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | QTR22B | DOH → JFK | May 30, 01:05 UTC | May 30, 03:45 UTC | 2h 40m |
| 2026-05-29 | QTR70E | TUN → DOH | May 29, 05:45 UTC | May 29, 20:50 UTC | 15h 5m |
| 2026-05-28 | QTR004 | - | May 28, 14:35 UTC | May 28, 20:50 UTC | 6h 15m |
| 2026-05-28 | QTR003 | - | May 28, 08:00 UTC | May 28, 11:55 UTC | 3h 55m |
| 2026-05-25 | QTR27R | - | May 25, 11:10 UTC | May 25, 21:49 UTC | 10h 39m |
| 2026-05-24 | QTR40X | - | May 24, 21:00 UTC | May 25, 07:50 UTC | 10h 50m |
| 2026-05-24 | QTR29F | LHR → DOH | May 24, 07:40 UTC | May 24, 13:55 UTC | 6h 15m |
| 2026-05-24 | QTR57W | BRU → DOH | May 24, 02:05 UTC | May 24, 05:05 UTC | 3h 0m |
| 2026-05-23 | QTR706 | JFK → DOH | May 23, 05:40 UTC | May 23, 17:35 UTC | 11h 55m |
| 2026-05-22 | QTR57H | - | May 22, 12:35 UTC | May 22, 13:05 UTC | 30m |
| 2026-05-20 | QTR65B | DFW → DOH | May 20, 23:05 UTC | May 20, 23:45 UTC | 40m |
| 2026-05-20 | QTR778 | MIA → DOH | May 20, 02:45 UTC | May 20, 20:25 UTC | 17h 41m |
| 2026-05-20 | QTR778 | MIA → DOH | May 20, 01:15 UTC | May 20, 20:25 UTC | 19h 11m |
| 2026-05-18 | QTR27R | - | May 18, 11:00 UTC | May 18, 21:55 UTC | 10h 54m |
| 2026-05-17 | QTR40X | - | May 17, 20:40 UTC | May 18, 06:40 UTC | 10h 0m |
| 2026-05-17 | QTR40X | - | May 17, 09:50 UTC | May 18, 06:40 UTC | 20h 50m |
| 2026-05-17 | QTR87Q | ORD → DOH | May 17, 07:50 UTC | May 18, 06:40 UTC | 22h 50m |
| 2026-05-17 | QTR87Q | ORD → DOH | May 17, 01:50 UTC | May 17, 21:35 UTC | 19h 45m |
| 2026-05-17 | QTR87Q | ORD → DOH | May 17, 00:55 UTC | May 17, 21:35 UTC | 20h 40m |
| 2026-05-15 | QTR21L | LAX → LGG | May 15, 15:20 UTC | May 15, 18:50 UTC | 3h 30m |
| 2026-05-13 | QTR32N | DOH → SJJ | May 13, 23:15 UTC | May 13, 23:45 UTC | 30m |
| 2026-05-13 | QTR572 | DOH → BLR | May 13, 20:35 UTC | May 13, 21:05 UTC | 30m |
| 2026-05-13 | QTR65R | SEA → DOH | May 13, 01:25 UTC | May 13, 13:40 UTC | 12h 15m |
| 2026-05-11 | QTR47Y | PHL → DOH | May 11, 15:15 UTC | May 11, 21:15 UTC | 6h 0m |
| 2026-05-10 | QTR28U | DOH → LHR | May 10, 20:25 UTC | May 11, 12:05 UTC | 15h 40m |
| 2026-05-10 | QTR815 | HKG → DOH | May 10, 18:25 UTC | May 10, 18:39 UTC | 15m |
| 2026-05-10 | QTR818 | DOH → HKG | May 10, 07:40 UTC | May 10, 08:05 UTC | 25m |
| 2026-05-09 | QTR47Y | PHL → DOH | May 9, 14:55 UTC | May 10, 05:50 UTC | 14h 55m |
| 2026-05-08 | QTR17E | - | May 8, 11:49 UTC | May 9, 06:05 UTC | 18h 15m |
| 2026-05-08 | QTR17E | - | May 8, 09:49 UTC | May 9, 06:05 UTC | 20h 15m |
| 2026-05-08 | QTR17E | - | May 8, 08:09 UTC | May 9, 06:05 UTC | 21h 55m |
| 2026-05-08 | QTR17E | - | May 8, 02:44 UTC | May 8, 12:14 UTC | 9h 30m |
| 2026-05-07 | QTR4E | DOH → BNE | May 7, 11:00 UTC | May 7, 22:15 UTC | 11h 15m |
| 2026-05-06 | QTR4U | DOH → CDG | May 6, 11:20 UTC | May 7, 01:50 UTC | 14h 29m |
| 2026-05-05 | QTR40X | - | May 5, 21:05 UTC | May 6, 07:20 UTC | 10h 15m |
| 2026-05-05 | QTR40X | - | May 5, 17:50 UTC | May 5, 18:00 UTC | 10m |
| 2026-05-05 | QTR778 | MIA → DOH | May 5, 01:10 UTC | May 5, 14:30 UTC | 13h 20m |
| 2026-05-04 | QTR93V | DOH → MIA | May 4, 06:40 UTC | May 4, 22:15 UTC | 15h 36m |
| 2026-05-03 | QTR004 | LHR → DOH | May 3, 14:20 UTC | May 3, 20:45 UTC | 6h 25m |
| 2026-05-03 | QTR003 | DOH → LHR | May 3, 04:50 UTC | May 3, 11:30 UTC | 6h 40m |
| 2026-05-03 | QTR1169 | RUH → DOH | May 3, 00:25 UTC | May 3, 00:50 UTC | 25m |
| 2026-05-02 | QTR1168 | DOH → RUH | May 2, 19:15 UTC | May 2, 19:40 UTC | 25m |
| 2026-05-02 | QTR98P | DOH → IAD | May 2, 01:00 UTC | May 2, 13:45 UTC | 12h 45m |
| 2026-05-01 | QTR20V | DOH → ORD | May 1, 07:05 UTC | May 1, 21:20 UTC | 14h 15m |
| 2026-04-29 | QTR706 | JFK → DOH | Apr 29, 05:40 UTC | Apr 29, 17:45 UTC | 12h 6m |
| 2026-04-28 | QTR15Q | DOH → JFK | Apr 28, 12:25 UTC | Apr 29, 01:50 UTC | 13h 25m |
| 2026-04-27 | QTR65B | DFW → DOH | Apr 27, 22:55 UTC | Apr 28, 01:50 UTC | 2h 55m |
| 2026-04-27 | QTR93W | TRV → DOH | Apr 27, 17:55 UTC | Apr 27, 20:40 UTC | 2h 45m |
| 2026-04-27 | QTR778 | MIA → DOH | Apr 27, 01:25 UTC | Apr 27, 14:40 UTC | 13h 15m |
| 2026-04-26 | QTR93V | DOH → MIA | Apr 26, 06:30 UTC | Apr 26, 22:55 UTC | 16h 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-ANS page for operator, model, and routing details .