sensors Mode-S transponder
06A0DD
ICAO 24-bit transponder address · allocated to Qatar
Currently assigned to A7-BFD · BOEING 777-200LR
- Hex
- 06A0DD
- Octal
- 01520335
- Decimal
- 434,397
- Country
- QA
- Tail
- A7-BFD
- Type
- B77L
- Flights observed
- 275
- Distinct callsigns
- 20
- Country
- QA
- Last broadcast
- 16m ago
Current position
Country allocation
The ICAO 24-bit address 06A0DD 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 |
|---|---|---|---|
| QTR8945 | Qatar Airways | 9 | 2026-05-26 |
| QTR8236 | Qatar Airways | 9 | 2026-05-27 |
| QTR8944 | Qatar Airways | 8 | 2026-05-25 |
| QTR8356 | Qatar Airways | 7 | 2026-04-27 |
| QTR19M | Qatar Airways | 7 | 2026-05-17 |
| QTR8406 | Qatar Airways | 5 | 2026-05-16 |
| QTR8434 | Qatar Airways | 4 | 2026-06-05 |
| QTR8410 | - | 4 | 2026-06-21 |
| QTR8402 | - | 4 | 2026-07-08 |
| QTR8142 | Qatar Airways | 4 | 2026-06-10 |
| QTR8089 | Qatar Airways | 4 | 2026-05-24 |
| QTR8040 | Qatar Airways | 4 | 2026-06-12 |
| QTR90G | - | 3 | 2026-07-07 |
| QTR8963 | Qatar Airways | 3 | 2026-05-16 |
| QTR8962 | Qatar Airways | 3 | 2026-05-15 |
| QTR8954 | Qatar Airways | 3 | 2026-06-16 |
| QTR8912 | Qatar Airways | 3 | 2026-05-28 |
| QTR8597 | - | 3 | 2026-07-03 |
| QTR8455 | - | 3 | 2026-07-12 |
| QTR8454 | - | 3 | 2026-07-12 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | QTR8464 | - | Jul 14, 20:10 UTC | Jul 15, 01:15 UTC | 5h 4m |
| 2026-07-14 | QTR8007 | - | Jul 14, 03:50 UTC | Jul 14, 17:45 UTC | 13h 55m |
| 2026-07-13 | QTR8006 | - | Jul 13, 08:50 UTC | Jul 14, 01:35 UTC | 16h 45m |
| 2026-07-12 | QTR8455 | - | Jul 12, 23:50 UTC | Jul 13, 01:50 UTC | 2h 0m |
| 2026-07-12 | QTR8455 | - | Jul 12, 22:10 UTC | Jul 12, 22:20 UTC | 10m |
| 2026-07-12 | QTR8454 | - | Jul 12, 07:35 UTC | Jul 12, 19:35 UTC | 12h 0m |
| 2026-07-11 | QTR8081 | - | Jul 11, 15:50 UTC | Jul 12, 03:30 UTC | 11h 40m |
| 2026-07-11 | QTR8080 | JFK → ATL | Jul 11, 06:50 UTC | Jul 11, 08:30 UTC | 1h 40m |
| 2026-07-10 | QTR8080 | - | Jul 10, 20:55 UTC | Jul 11, 04:15 UTC | 7h 20m |
| 2026-07-10 | QTR8080 | - | Jul 10, 13:20 UTC | Jul 10, 17:30 UTC | 4h 10m |
| 2026-07-09 | QTR8968 | - | Jul 9, 14:25 UTC | Jul 10, 02:35 UTC | 12h 10m |
| 2026-07-09 | QTR78F | - | Jul 9, 06:55 UTC | Jul 9, 13:20 UTC | 6h 25m |
| 2026-07-09 | QTR8694 | - | Jul 9, 00:10 UTC | Jul 9, 00:50 UTC | 40m |
| 2026-07-08 | QTR8403 | - | Jul 8, 04:15 UTC | Jul 8, 11:05 UTC | 6h 50m |
| 2026-07-08 | QTR8403 | - | Jul 8, 03:30 UTC | Jul 8, 03:45 UTC | 15m |
| 2026-07-08 | QTR8402 | - | Jul 8, 00:35 UTC | Jul 8, 01:00 UTC | 25m |
| 2026-07-07 | QTR8402 | - | Jul 7, 17:05 UTC | Jul 7, 22:50 UTC | 5h 45m |
| 2026-07-07 | QTR46U | - | Jul 7, 09:30 UTC | Jul 7, 14:55 UTC | 5h 25m |
| 2026-07-07 | QTR90G | - | Jul 7, 00:55 UTC | Jul 7, 06:40 UTC | 5h 45m |
| 2026-07-06 | QTR57R | FRA → DOH | Jul 6, 14:20 UTC | Jul 6, 19:45 UTC | 5h 25m |
| 2026-07-06 | QTR75J | - | Jul 6, 05:45 UTC | Jul 6, 11:30 UTC | 5h 45m |
| 2026-07-05 | QTR8220 | - | Jul 5, 17:50 UTC | Jul 5, 23:50 UTC | 6h 0m |
| 2026-07-05 | QTR8220 | - | Jul 5, 09:15 UTC | Jul 5, 10:35 UTC | 1h 20m |
| 2026-07-05 | QTR23J | DOH → AMS | Jul 5, 01:05 UTC | Jul 5, 07:00 UTC | 5h 55m |
| 2026-07-04 | QTR8485 | STN → SYD | Jul 4, 14:20 UTC | Jul 4, 20:10 UTC | 5h 50m |
| 2026-07-04 | QTR8485 | STN → SYD | Jul 4, 10:35 UTC | Jul 4, 12:20 UTC | 1h 45m |
| 2026-07-04 | QTR8484 | ROK → BNE | Jul 4, 03:15 UTC | Jul 4, 08:00 UTC | 4h 45m |
| 2026-07-03 | QTR8597 | PRG → DOH | Jul 3, 19:40 UTC | Jul 4, 00:40 UTC | 5h 0m |
| 2026-07-03 | QTR8597 | BUD → PRG | Jul 3, 16:40 UTC | Jul 3, 17:35 UTC | 55m |
| 2026-07-03 | QTR8596 | DOH → BUD | Jul 3, 09:40 UTC | Jul 3, 14:25 UTC | 4h 45m |
| 2026-07-03 | QTR8409 | - | Jul 3, 00:10 UTC | Jul 3, 06:40 UTC | 6h 30m |
| 2026-07-02 | QTR8409 | - | Jul 2, 23:15 UTC | Jul 2, 23:30 UTC | 15m |
| 2026-07-02 | QTR8408 | - | Jul 2, 20:55 UTC | Jul 2, 21:20 UTC | 25m |
| 2026-07-02 | QTR8408 | - | Jul 2, 14:15 UTC | Jul 2, 20:10 UTC | 5h 55m |
| 2026-07-02 | QTR35T | - | Jul 2, 11:00 UTC | Jul 2, 11:40 UTC | 40m |
| 2026-07-02 | QTR8726 | - | Jul 2, 07:10 UTC | Jul 2, 07:55 UTC | 45m |
| 2026-07-01 | QTR8941 | - | Jul 1, 20:55 UTC | Jul 2, 03:30 UTC | 6h 35m |
| 2026-07-01 | QTR8940 | - | Jul 1, 09:35 UTC | Jul 1, 15:25 UTC | 5h 50m |
| 2026-07-01 | QTR8745 | - | Jul 1, 06:10 UTC | Jul 1, 06:55 UTC | 45m |
| 2026-07-01 | QTR8744 | - | Jul 1, 03:15 UTC | Jul 1, 03:45 UTC | 30m |
| 2026-06-30 | QTR8441 | - | Jun 30, 17:45 UTC | Jul 1, 00:30 UTC | 6h 45m |
| 2026-06-30 | QTR8441 | - | Jun 30, 17:05 UTC | Jun 30, 17:15 UTC | 10m |
| 2026-06-30 | QTR8440 | - | Jun 30, 14:50 UTC | Jun 30, 15:15 UTC | 25m |
| 2026-06-30 | QTR8440 | - | Jun 30, 07:20 UTC | Jun 30, 14:05 UTC | 6h 45m |
| 2026-06-29 | QTR8140 | ORD → HNL | Jun 29, 21:24 UTC | Jun 30, 06:05 UTC | 8h 41m |
| 2026-06-29 | QTR8140 | ORD → HNL | Jun 29, 10:04 UTC | Jun 29, 18:39 UTC | 8h 35m |
| 2026-06-29 | QTR8152 | - | Jun 29, 05:50 UTC | Jun 29, 07:55 UTC | 2h 5m |
| 2026-06-28 | QTR8U | - | Jun 28, 18:55 UTC | Jun 29, 03:05 UTC | 8h 10m |
| 2026-06-28 | QTR8U | - | Jun 28, 11:19 UTC | Jun 28, 17:25 UTC | 6h 5m |
| 2026-06-28 | QTR99R | DOH → DOH | Jun 28, 04:05 UTC | Jun 28, 07:40 UTC | 3h 35m |
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-BFD page for operator, model, and routing details .