sensors Mode-S transponder
06A2FB
ICAO 24-bit transponder address · allocated to Qatar
Currently assigned to A7-BHX · BOEING 787-9 Dreamliner
- Hex
- 06A2FB
- Octal
- 01521373
- Decimal
- 434,939
- Country
- QA
- Tail
- A7-BHX
- Type
- B789
- Flights observed
- 108
- Distinct callsigns
- 20
- Country
- QA
- Last broadcast
- 7h ago
Last known position
Country allocation
The ICAO 24-bit address 06A2FB 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 |
|---|---|---|---|
| QTR977 | Qatar Airways | 14 | 2026-05-29 |
| QTR80C | - | 11 | 2026-05-15 |
| QTR60F | Qatar Airways | 8 | 2026-05-15 |
| QTR69X | - | 7 | 2026-05-16 |
| QTR340 | Qatar Airways | 5 | 2026-05-16 |
| QTR22P | - | 5 | 2026-04-14 |
| QTR6R | Qatar Airways | 4 | 2026-04-15 |
| QTR39C | Qatar Airways | 4 | 2026-04-15 |
| QTR338 | Qatar Airways | 4 | 2026-05-25 |
| QTR337 | Qatar Airways | 4 | 2026-05-25 |
| QTR1N | Qatar Airways | 4 | 2026-04-13 |
| QTR976 | Qatar Airways | 3 | 2026-05-29 |
| QTR52N | Qatar Airways | 3 | 2026-05-17 |
| QTR1396 | - | 3 | 2026-05-09 |
| QTR48L | - | 2 | 2026-04-26 |
| QTR46M | Qatar Airways | 2 | 2026-05-08 |
| QTR46K | - | 2 | 2026-05-26 |
| QTR3B | Qatar Airways | 2 | 2026-05-28 |
| QTR1364 | Qatar Airways | 2 | 2026-05-26 |
| QTR970 | Qatar Airways | 1 | 2026-05-14 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | QTR977 | HAN → DOH | May 29, 20:00 UTC | May 29, 23:55 UTC | 3h 55m |
| 2026-05-29 | QTR977 | HAN → DOH | May 29, 19:15 UTC | May 29, 19:30 UTC | 15m |
| 2026-05-29 | QTR976 | DOH → HAN | May 29, 02:15 UTC | May 29, 06:05 UTC | 3h 50m |
| 2026-05-28 | QTR3B | JFK → ORD | May 28, 21:30 UTC | May 28, 22:10 UTC | 40m |
| 2026-05-26 | QTR1364 | JNB → DOH | May 26, 18:05 UTC | May 26, 18:30 UTC | 25m |
| 2026-05-26 | QTR46K | - | May 26, 07:49 UTC | May 26, 08:15 UTC | 25m |
| 2026-05-25 | QTR338 | SVO → DOH | May 25, 08:00 UTC | May 25, 14:20 UTC | 6h 20m |
| 2026-05-25 | QTR337 | DOH → SVO | May 25, 05:05 UTC | May 25, 05:35 UTC | 30m |
| 2026-05-25 | QTR337 | DOH → SVO | May 25, 02:20 UTC | May 25, 02:45 UTC | 25m |
| 2026-05-24 | QTR338 | SVO → DOH | May 24, 09:00 UTC | May 24, 14:15 UTC | 5h 15m |
| 2026-05-24 | QTR338 | SVO → DOH | May 24, 08:00 UTC | May 24, 08:20 UTC | 20m |
| 2026-05-24 | QTR337 | DOH → SVO | May 24, 02:05 UTC | May 24, 04:10 UTC | 2h 5m |
| 2026-05-23 | QTR48K | IAH → DOH | May 23, 15:30 UTC | May 23, 21:20 UTC | 5h 51m |
| 2026-05-23 | QTR6M | DOH → CCU | May 23, 08:15 UTC | May 23, 12:35 UTC | 4h 20m |
| 2026-05-22 | QTR1364 | JNB → DOH | May 22, 18:15 UTC | May 23, 02:05 UTC | 7h 50m |
| 2026-05-22 | QTR46K | - | May 22, 07:25 UTC | May 22, 08:00 UTC | 35m |
| 2026-05-20 | QTR977 | HAN → DOH | May 20, 05:05 UTC | May 21, 00:05 UTC | 19h 0m |
| 2026-05-20 | QTR977 | HAN → DOH | May 20, 02:50 UTC | May 21, 00:05 UTC | 21h 16m |
| 2026-05-19 | QTR44R | DOH → FCO | May 19, 14:55 UTC | May 19, 20:05 UTC | 5h 10m |
| 2026-05-19 | QTR37K | - | May 19, 11:10 UTC | May 19, 12:40 UTC | 1h 30m |
| 2026-05-18 | QTR8V | DOH → DXB | May 18, 20:55 UTC | May 19, 03:05 UTC | 6h 10m |
| 2026-05-17 | QTR52N | ATL → DOH | May 17, 23:00 UTC | May 18, 18:20 UTC | 19h 20m |
| 2026-05-17 | QTR52N | ATL → DOH | May 17, 20:50 UTC | May 18, 18:20 UTC | 21h 30m |
| 2026-05-17 | QTR52N | ATL → DOH | May 17, 19:55 UTC | May 18, 18:20 UTC | 22h 25m |
| 2026-05-17 | QTR977 | HAN → DOH | May 17, 04:50 UTC | May 17, 23:50 UTC | 19h 0m |
| 2026-05-17 | QTR977 | HAN → DOH | May 17, 02:50 UTC | May 17, 23:50 UTC | 21h 0m |
| 2026-05-16 | QTR340 | SVO → DOH | May 16, 15:50 UTC | May 16, 20:55 UTC | 5h 5m |
| 2026-05-16 | QTR69X | - | May 16, 12:31 UTC | May 16, 12:40 UTC | 10m |
| 2026-05-16 | QTR69X | - | May 16, 09:01 UTC | May 16, 11:25 UTC | 2h 25m |
| 2026-05-15 | QTR60F | BRU → DOH | May 15, 15:40 UTC | May 15, 21:15 UTC | 5h 35m |
| 2026-05-15 | QTR80C | - | May 15, 08:15 UTC | May 15, 13:35 UTC | 5h 20m |
| 2026-05-14 | QTR80C | - | May 14, 18:00 UTC | May 15, 13:35 UTC | 19h 35m |
| 2026-05-14 | QTR80C | - | May 14, 14:10 UTC | May 15, 12:45 UTC | 22h 35m |
| 2026-05-14 | QTR970 | SGN → PNH | May 14, 02:50 UTC | May 14, 18:40 UTC | 15h 50m |
| 2026-05-13 | QTR60F | BRU → DOH | May 13, 15:40 UTC | May 13, 21:25 UTC | 5h 45m |
| 2026-05-13 | QTR80C | - | May 13, 06:25 UTC | May 13, 13:20 UTC | 6h 55m |
| 2026-05-12 | QTR340 | SVO → DOH | May 12, 15:40 UTC | May 12, 21:25 UTC | 5h 45m |
| 2026-05-12 | QTR69X | - | May 12, 08:30 UTC | May 12, 12:00 UTC | 3h 30m |
| 2026-05-11 | QTR60F | BRU → DOH | May 11, 15:40 UTC | May 11, 21:25 UTC | 5h 46m |
| 2026-05-11 | QTR80C | - | May 11, 08:35 UTC | May 11, 13:40 UTC | 5h 5m |
| 2026-05-10 | QTR90W | AMS → DOH | May 10, 23:00 UTC | May 10, 23:39 UTC | 40m |
| 2026-05-10 | QTR82C | - | May 10, 16:25 UTC | May 10, 20:14 UTC | 3h 50m |
| 2026-05-09 | QTR1396 | - | May 9, 19:35 UTC | May 9, 20:05 UTC | 30m |
| 2026-05-09 | QTR1396 | - | May 9, 13:55 UTC | May 9, 17:00 UTC | 3h 5m |
| 2026-05-08 | QTR46M | WAW → DOH | May 8, 09:14 UTC | May 8, 14:30 UTC | 5h 15m |
| 2026-05-07 | QTR60F | BRU → DOH | May 7, 16:15 UTC | May 7, 22:15 UTC | 6h 0m |
| 2026-05-07 | QTR80C | - | May 7, 09:00 UTC | May 7, 14:05 UTC | 5h 5m |
| 2026-05-06 | QTR80C | - | May 6, 11:00 UTC | May 7, 10:30 UTC | 23h 30m |
| 2026-05-05 | QTR1365 | DOH → JNB | May 5, 18:40 UTC | May 6, 01:50 UTC | 7h 10m |
| 2026-05-04 | QTR69X | - | May 4, 06:25 UTC | May 4, 21:30 UTC | 15h 6m |
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-BHX page for operator, model, and routing details .