sensors Mode-S transponder
06A12B
ICAO 24-bit transponder address · allocated to Qatar
Currently assigned to A7-ANO · AIRBUS A-350-1000
- Hex
- 06A12B
- Octal
- 01520453
- Decimal
- 434,475
- Country
- QA
- Tail
- A7-ANO
- Type
- A35K
- Flights observed
- 163
- Distinct callsigns
- 20
- Country
- QA
- Last broadcast
- 2h ago
Last known position
Country allocation
The ICAO 24-bit address 06A12B 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 |
|---|---|---|---|
| QTR815 | Qatar Airways | 9 | 2026-05-29 |
| QTR17E | - | 8 | 2026-05-14 |
| QTR4E | Qatar Airways | 7 | 2026-04-29 |
| QTR20V | - | 7 | 2026-06-13 |
| QTR818 | Qatar Airways | 6 | 2026-05-29 |
| QTR93V | - | 5 | 2026-07-14 |
| QTR87Q | Qatar Airways | 5 | 2026-06-14 |
| QTR29F | - | 5 | 2026-06-15 |
| QTR90B | - | 4 | 2026-07-10 |
| QTR8M | Qatar Airways | 4 | 2026-05-11 |
| QTR7E | - | 4 | 2026-07-11 |
| QTR778 | - | 4 | 2026-06-24 |
| QTR5M | Qatar Airways | 4 | 2026-05-10 |
| QTR35P | - | 4 | 2026-07-11 |
| QTR16M | Qatar Airways | 4 | 2026-05-24 |
| QTR003 | - | 4 | 2026-04-20 |
| QTR99M | Qatar Airways | 3 | 2026-04-22 |
| QTR5Q | Qatar Airways | 3 | 2026-07-06 |
| QTR572 | - | 3 | 2026-06-17 |
| QTR51U | - | 3 | 2026-07-13 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | QTR93V | - | Jul 14, 08:30 UTC | Jul 14, 13:50 UTC | 5h 20m |
| 2026-07-14 | QTR93V | - | Jul 14, 06:20 UTC | Jul 14, 06:55 UTC | 35m |
| 2026-07-14 | QTR1157 | - | Jul 14, 02:50 UTC | Jul 14, 03:30 UTC | 40m |
| 2026-07-14 | QTR1156 | - | Jul 14, 00:10 UTC | Jul 14, 00:40 UTC | 30m |
| 2026-07-13 | QTR51U | - | Jul 13, 05:15 UTC | Jul 13, 18:05 UTC | 12h 50m |
| 2026-07-11 | QTR7E | DOH → DFW | Jul 11, 23:40 UTC | Jul 12, 14:55 UTC | 15h 15m |
| 2026-07-11 | QTR35P | - | Jul 11, 00:20 UTC | Jul 11, 16:00 UTC | 15h 40m |
| 2026-07-10 | QTR90B | - | Jul 10, 05:25 UTC | Jul 10, 21:40 UTC | 16h 15m |
| 2026-07-09 | QTR51U | DFW → DOH | Jul 9, 05:00 UTC | Jul 9, 20:00 UTC | 15h 0m |
| 2026-07-08 | QTR7E | MAD → BSL | Jul 8, 01:35 UTC | Jul 8, 14:55 UTC | 13h 20m |
| 2026-07-07 | QTR7E | MAD → BSL | Jul 7, 23:30 UTC | Jul 7, 23:55 UTC | 25m |
| 2026-07-07 | QTR73V | SFO → DOH | Jul 7, 01:00 UTC | Jul 7, 15:55 UTC | 14h 55m |
| 2026-07-06 | QTR5Q | SAW → DOH | Jul 6, 06:00 UTC | Jul 6, 22:20 UTC | 16h 20m |
| 2026-07-05 | QTR1237 | - | Jul 5, 22:45 UTC | Jul 5, 23:15 UTC | 30m |
| 2026-07-05 | QTR1236 | - | Jul 5, 19:25 UTC | Jul 5, 19:45 UTC | 20m |
| 2026-07-04 | QTR35P | BUD → DOH | Jul 4, 23:55 UTC | Jul 5, 15:15 UTC | 15h 20m |
| 2026-07-04 | QTR90B | CPT → DOH | Jul 4, 05:10 UTC | Jul 4, 21:15 UTC | 16h 5m |
| 2026-07-03 | QTR35P | BUD → DOH | Jul 3, 14:15 UTC | Jul 3, 14:50 UTC | 35m |
| 2026-07-02 | QTR35P | BUD → DOH | Jul 2, 23:55 UTC | Jul 3, 13:15 UTC | 13h 20m |
| 2026-07-02 | QTR90B | CPT → DOH | Jul 2, 06:41 UTC | Jul 2, 21:00 UTC | 14h 19m |
| 2026-07-02 | QTR90B | CPT → DOH | Jul 2, 05:00 UTC | Jul 2, 05:30 UTC | 30m |
| 2026-07-01 | QTR65B | - | Jul 1, 23:20 UTC | Jul 2, 02:15 UTC | 2h 55m |
| 2026-07-01 | QTR93W | DOH → BOM | Jul 1, 18:10 UTC | Jul 1, 21:10 UTC | 3h 0m |
| 2026-07-01 | QTR73V | SFO → DOH | Jul 1, 00:00 UTC | Jul 1, 15:10 UTC | 15h 10m |
| 2026-06-30 | QTR5Q | SAW → DOH | Jun 30, 06:45 UTC | Jun 30, 20:40 UTC | 13h 55m |
| 2026-06-30 | QTR5Q | SAW → DOH | Jun 30, 05:00 UTC | Jun 30, 05:30 UTC | 30m |
| 2026-06-29 | QTR859 | - | Jun 29, 16:59 UTC | Jun 30, 02:20 UTC | 9h 21m |
| 2026-06-29 | QTR858 | - | Jun 29, 07:25 UTC | Jun 29, 07:55 UTC | 30m |
| 2026-06-28 | QTR858 | - | Jun 28, 23:14 UTC | Jun 29, 06:40 UTC | 7h 25m |
| 2026-06-28 | QTR51U | DFW → DOH | Jun 28, 04:35 UTC | Jun 28, 18:55 UTC | 14h 20m |
| 2026-06-26 | QTR7E | MAD → BSL | Jun 26, 23:19 UTC | Jun 27, 14:35 UTC | 15h 15m |
| 2026-06-26 | QTR98E | - | Jun 26, 15:34 UTC | Jun 26, 20:55 UTC | 5h 20m |
| 2026-06-26 | QTR5X | DOH → ALG | Jun 26, 06:04 UTC | Jun 26, 11:24 UTC | 5h 20m |
| 2026-06-26 | QTR1157 | - | Jun 26, 02:14 UTC | Jun 26, 02:44 UTC | 30m |
| 2026-06-25 | QTR1156 | - | Jun 25, 23:39 UTC | Jun 26, 00:10 UTC | 30m |
| 2026-06-24 | QTR778 | - | Jun 24, 23:54 UTC | Jun 25, 13:55 UTC | 14h 0m |
| 2026-06-24 | QTR93V | DOH → MIA | Jun 24, 05:54 UTC | Jun 24, 20:44 UTC | 14h 50m |
| 2026-06-23 | QTR29R | CDG → DOH | Jun 23, 08:15 UTC | Jun 23, 14:10 UTC | 5h 55m |
| 2026-06-22 | QTR38P | DOH → MAN | Jun 22, 23:14 UTC | Jun 23, 05:29 UTC | 6h 15m |
| 2026-06-22 | QTR66X | - | Jun 22, 03:50 UTC | Jun 22, 17:40 UTC | 13h 50m |
| 2026-06-20 | QTR3V | - | Jun 20, 23:10 UTC | Jun 21, 13:54 UTC | 14h 45m |
| 2026-06-20 | QTR22B | - | Jun 20, 00:09 UTC | Jun 20, 14:39 UTC | 14h 30m |
| 2026-06-19 | QTR70E | - | Jun 19, 05:45 UTC | Jun 19, 20:29 UTC | 14h 45m |
| 2026-06-18 | QTR67H | SKT → DOH | Jun 18, 19:05 UTC | Jun 19, 01:19 UTC | 6h 14m |
| 2026-06-17 | QTR1F | - | Jun 17, 22:40 UTC | Jun 18, 16:35 UTC | 17h 55m |
| 2026-06-17 | QTR572 | - | Jun 17, 19:10 UTC | Jun 17, 20:50 UTC | 1h 40m |
| 2026-06-17 | QTR778 | - | Jun 17, 00:15 UTC | Jun 17, 13:50 UTC | 13h 35m |
| 2026-06-16 | QTR93V | - | Jun 16, 08:00 UTC | Jun 16, 20:30 UTC | 12h 31m |
| 2026-06-15 | QTR29F | - | Jun 15, 08:10 UTC | Jun 15, 14:30 UTC | 6h 20m |
| 2026-06-15 | QTR57W | - | Jun 15, 01:00 UTC | Jun 15, 06:15 UTC | 5h 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-ANO page for operator, model, and routing details .