sensors Mode-S transponder
06A053
ICAO 24-bit transponder address · allocated to Qatar
Currently assigned to A7-BAB · BOEING 777-300ER
- Hex
- 06A053
- Octal
- 01520123
- Decimal
- 434,259
- Country
- QA
- Tail
- A7-BAB
- Type
- B77W
- Flights observed
- 53
- Distinct callsigns
- 20
- Country
- QA
- Last broadcast
- 9h ago
Last known position
Country allocation
The ICAO 24-bit address 06A053 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 |
|---|---|---|---|
| QTR90W | Qatar Airways | 4 | 2026-04-27 |
| QTR82C | - | 4 | 2026-04-27 |
| QTR818 | Qatar Airways | 4 | 2026-04-24 |
| QTR815 | Qatar Airways | 4 | 2026-04-24 |
| QTR27L | Qatar Airways | 4 | 2026-05-10 |
| QTR18J | Qatar Airways | 3 | 2026-05-22 |
| QTR1153 | Qatar Airways | 3 | 2026-05-17 |
| QTR63N | - | 2 | 2026-04-14 |
| QTR56U | Qatar Airways | 2 | 2026-05-27 |
| QTR31L | Qatar Airways | 2 | 2026-05-02 |
| QTR22X | Qatar Airways | 2 | 2026-05-20 |
| QTR16W | Qatar Airways | 2 | 2026-05-29 |
| QTR1169 | Qatar Airways | 2 | 2026-04-15 |
| QTR1168 | - | 2 | 2026-04-13 |
| QTR83V | Qatar Airways | 1 | 2026-05-19 |
| QTR829 | Qatar Airways | 1 | 2026-04-26 |
| QTR828 | Qatar Airways | 1 | 2026-04-25 |
| QTR7A | Qatar Airways | 1 | 2026-05-13 |
| QTR6B | Qatar Airways | 1 | 2026-05-21 |
| QTR643 | Qatar Airways | 1 | 2026-05-07 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | QTR16W | DOH → MLE | May 29, 19:05 UTC | May 29, 19:45 UTC | 40m |
| 2026-05-28 | QTR16W | DOH → MLE | May 28, 23:50 UTC | May 29, 19:45 UTC | 19h 55m |
| 2026-05-27 | QTR56U | LGG → DOH | May 27, 16:25 UTC | May 27, 18:50 UTC | 2h 25m |
| 2026-05-24 | QTR56U | LGG → DOH | May 24, 18:20 UTC | May 24, 19:00 UTC | 40m |
| 2026-05-22 | QTR18J | DOH → MAD | May 22, 21:15 UTC | May 23, 07:35 UTC | 10h 19m |
| 2026-05-21 | QTR6B | DOH → JFK | May 21, 13:35 UTC | May 21, 19:45 UTC | 6h 10m |
| 2026-05-21 | QTR18J | DOH → MAD | May 21, 03:45 UTC | May 21, 04:10 UTC | 25m |
| 2026-05-20 | QTR22X | DOH → CMB | May 20, 21:05 UTC | May 20, 21:50 UTC | 45m |
| 2026-05-19 | QTR83V | BGW → DOH | May 19, 11:40 UTC | May 19, 12:15 UTC | 35m |
| 2026-05-17 | QTR1153 | DMM → DOH | May 17, 17:50 UTC | May 17, 18:20 UTC | 30m |
| 2026-05-14 | QTR1165 | RUH → DOH | May 14, 17:45 UTC | May 14, 18:25 UTC | 40m |
| 2026-05-13 | QTR7A | CAI → DOH | May 13, 11:20 UTC | May 13, 13:50 UTC | 2h 30m |
| 2026-05-10 | QTR27L | BEY → DOH | May 10, 06:04 UTC | May 10, 14:04 UTC | 8h 0m |
| 2026-05-07 | QTR643 | SIN → DOH | May 7, 22:20 UTC | May 7, 23:19 UTC | 1h 0m |
| 2026-05-07 | QTR642 | DOH → SIN | May 7, 19:25 UTC | May 7, 20:25 UTC | 1h 0m |
| 2026-05-05 | QTR1153 | DMM → DOH | May 5, 17:40 UTC | May 5, 18:15 UTC | 35m |
| 2026-05-04 | QTR1153 | DMM → DOH | May 4, 18:40 UTC | May 4, 19:15 UTC | 35m |
| 2026-05-04 | QTR1152 | DOH → DMM | May 4, 13:50 UTC | May 4, 14:10 UTC | 20m |
| 2026-05-02 | QTR31L | VCE → DOH | May 2, 17:10 UTC | May 2, 17:40 UTC | 30m |
| 2026-05-02 | QTR1171 | RUH → DOH | May 2, 05:00 UTC | May 2, 09:40 UTC | 4h 40m |
| 2026-05-01 | QTR1191 | JED → DOH | May 1, 05:10 UTC | May 1, 11:05 UTC | 5h 55m |
| 2026-04-29 | QTR31L | VCE → DOH | Apr 29, 17:35 UTC | Apr 29, 17:55 UTC | 20m |
| 2026-04-28 | QTR27L | BEY → DOH | Apr 28, 05:20 UTC | Apr 28, 14:10 UTC | 8h 50m |
| 2026-04-27 | QTR90W | AMS → DOH | Apr 27, 22:05 UTC | Apr 28, 02:10 UTC | 4h 5m |
| 2026-04-27 | QTR82C | - | Apr 27, 13:15 UTC | Apr 27, 17:05 UTC | 3h 50m |
| 2026-04-26 | QTR829 | BKK → DOH | Apr 26, 12:10 UTC | Apr 26, 18:45 UTC | 6h 35m |
| 2026-04-25 | QTR828 | DOH → BKK | Apr 25, 23:40 UTC | Apr 26, 05:40 UTC | 6h 0m |
| 2026-04-24 | QTR815 | HKG → DOH | Apr 24, 20:10 UTC | Apr 25, 02:15 UTC | 6h 5m |
| 2026-04-24 | QTR815 | HKG → DOH | Apr 24, 17:55 UTC | Apr 24, 18:10 UTC | 15m |
| 2026-04-24 | QTR818 | DOH → HKG | Apr 24, 07:45 UTC | Apr 24, 08:15 UTC | 30m |
| 2026-04-24 | QTR818 | DOH → HKG | Apr 24, 01:10 UTC | Apr 24, 05:50 UTC | 4h 40m |
| 2026-04-22 | QTR815 | HKG → DOH | Apr 22, 20:05 UTC | Apr 23, 02:15 UTC | 6h 10m |
| 2026-04-22 | QTR815 | HKG → DOH | Apr 22, 17:55 UTC | Apr 22, 18:05 UTC | 10m |
| 2026-04-22 | QTR818 | DOH → HKG | Apr 22, 07:40 UTC | Apr 22, 08:10 UTC | 30m |
| 2026-04-22 | QTR818 | DOH → HKG | Apr 22, 01:05 UTC | Apr 22, 05:50 UTC | 4h 45m |
| 2026-04-20 | QTR403 | AMM → DOH | Apr 20, 11:05 UTC | Apr 20, 13:10 UTC | 2h 5m |
| 2026-04-20 | QTR25C | SFO → DOH | Apr 20, 05:55 UTC | Apr 20, 06:35 UTC | 40m |
| 2026-04-18 | QTR90W | AMS → DOH | Apr 18, 22:10 UTC | Apr 19, 02:25 UTC | 4h 15m |
| 2026-04-18 | QTR82C | - | Apr 18, 13:10 UTC | Apr 18, 16:55 UTC | 3h 45m |
| 2026-04-18 | QTR90W | AMS → DOH | Apr 18, 01:30 UTC | Apr 18, 02:40 UTC | 1h 10m |
| 2026-04-17 | QTR90W | AMS → DOH | Apr 17, 22:20 UTC | Apr 17, 22:55 UTC | 35m |
| 2026-04-17 | QTR82C | - | Apr 17, 16:40 UTC | Apr 17, 17:10 UTC | 30m |
| 2026-04-17 | QTR82C | - | Apr 17, 13:20 UTC | Apr 17, 14:00 UTC | 40m |
| 2026-04-15 | QTR1169 | RUH → DOH | Apr 15, 20:15 UTC | Apr 15, 21:00 UTC | 45m |
| 2026-04-14 | QTR27L | BEY → DOH | Apr 14, 14:20 UTC | Apr 14, 14:45 UTC | 25m |
| 2026-04-14 | QTR27L | BEY → DOH | Apr 14, 11:30 UTC | Apr 14, 12:25 UTC | 55m |
| 2026-04-14 | QTR63N | - | Apr 14, 08:05 UTC | Apr 14, 09:05 UTC | 1h 0m |
| 2026-04-14 | QTR63N | - | Apr 14, 05:15 UTC | Apr 14, 05:50 UTC | 35m |
| 2026-04-13 | QTR1169 | RUH → DOH | Apr 13, 20:30 UTC | Apr 13, 21:05 UTC | 35m |
| 2026-04-13 | QTR1168 | - | Apr 13, 16:15 UTC | Apr 13, 16:40 UTC | 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-BAB page for operator, model, and routing details .