sensors Mode-S transponder
06A0DF
ICAO 24-bit transponder address · allocated to Qatar
Currently assigned to A7-BFF · BOEING 777-200LR
- Hex
- 06A0DF
- Octal
- 01520337
- Decimal
- 434,399
- Country
- QA
- Tail
- A7-BFF
- Type
- B77L
- Flights observed
- 263
- Distinct callsigns
- 20
- Country
- QA
- Last broadcast
- Jul 26, 20:05 UTC
Current position
Country allocation
The ICAO 24-bit address 06A0DF 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 |
|---|---|---|---|
| QTR8951 | Qatar Airways | 8 | 2026-07-18 |
| QTR8142 | Qatar Airways | 7 | 2026-05-27 |
| QTR8814 | Qatar Airways | 6 | 2026-05-04 |
| QTR8160 | - | 6 | 2026-06-26 |
| QTR72U | - | 6 | 2026-04-18 |
| QTR8961 | - | 5 | 2026-07-09 |
| QTR8220 | Qatar Airways | 5 | 2026-05-24 |
| QTR8912 | Qatar Airways | 4 | 2026-04-16 |
| QTR8694 | Qatar Airways | 4 | 2026-07-18 |
| QTR8500 | - | 4 | 2026-06-14 |
| QTR8421 | Qatar Airways | 4 | 2026-06-05 |
| QTR8358 | Qatar Airways | 4 | 2026-05-09 |
| QTR8256 | Qatar Airways | 4 | 2026-05-20 |
| QTR8139 | Qatar Airways | 4 | 2026-06-08 |
| QTR8059 | Qatar Airways | 4 | 2026-04-22 |
| QTR8022 | Qatar Airways | 4 | 2026-07-17 |
| QTR35M | Qatar Airways | 4 | 2026-06-19 |
| QTR31T | - | 4 | 2026-07-12 |
| QTR12B | Qatar Airways | 4 | 2026-07-22 |
| QTR8968 | Qatar Airways | 3 | 2026-06-18 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | QTR8953 | HAN → DOH | Jul 26, 13:50 UTC | Jul 26, 20:05 UTC | 6h 15m |
| 2026-07-26 | QTR8952 | DOH → HAN | Jul 26, 04:00 UTC | Jul 26, 10:00 UTC | 6h 1m |
| 2026-07-25 | QTR20X | - | Jul 25, 18:50 UTC | Jul 26, 01:05 UTC | 6h 15m |
| 2026-07-25 | QTR29G | - | Jul 25, 08:20 UTC | Jul 25, 08:50 UTC | 30m |
| 2026-07-24 | QTR8942 | DOH → CAN | Jul 24, 09:50 UTC | Jul 25, 03:25 UTC | 17h 35m |
| 2026-07-23 | QTR8413 | GRU → FLN | Jul 23, 15:35 UTC | Jul 23, 21:15 UTC | 5h 40m |
| 2026-07-23 | QTR8413 | - | Jul 23, 13:50 UTC | Jul 23, 14:00 UTC | 10m |
| 2026-07-23 | QTR8412 | - | Jul 23, 10:35 UTC | Jul 23, 11:05 UTC | 30m |
| 2026-07-23 | QTR8412 | - | Jul 23, 04:55 UTC | Jul 23, 08:40 UTC | 3h 45m |
| 2026-07-22 | QTR12B | ORD → DOH | Jul 22, 16:35 UTC | Jul 22, 23:05 UTC | 6h 30m |
| 2026-07-22 | QTR99E | DOH → AMS | Jul 22, 10:20 UTC | Jul 22, 13:25 UTC | 3h 5m |
| 2026-07-19 | QTR78F | - | Jul 19, 09:15 UTC | Jul 19, 10:20 UTC | 1h 5m |
| 2026-07-18 | QTR8694 | DOH → BLR | Jul 18, 17:10 UTC | Jul 19, 06:45 UTC | 13h 35m |
| 2026-07-18 | QTR8951 | HAN → DOH | Jul 18, 09:50 UTC | Jul 19, 06:45 UTC | 20h 55m |
| 2026-07-18 | QTR8951 | HAN → DOH | Jul 18, 09:05 UTC | Jul 19, 06:45 UTC | 21h 40m |
| 2026-07-18 | QTR8951 | HAN → DOH | Jul 18, 04:50 UTC | Jul 18, 17:45 UTC | 12h 55m |
| 2026-07-17 | QTR8951 | HAN → DOH | Jul 17, 18:55 UTC | Jul 18, 17:45 UTC | 22h 51m |
| 2026-07-17 | QTR8405 | HKG → DOH | Jul 17, 15:55 UTC | Jul 18, 11:00 UTC | 19h 6m |
| 2026-07-17 | QTR8405 | HKG → DOH | Jul 17, 14:10 UTC | Jul 17, 14:24 UTC | 15m |
| 2026-07-17 | QTR8022 | MUC → DOH | Jul 17, 11:15 UTC | Jul 17, 11:45 UTC | 30m |
| 2026-07-17 | QTR8022 | MUC → DOH | Jul 17, 03:30 UTC | Jul 17, 09:25 UTC | 5h 55m |
| 2026-07-16 | QTR8997 | - | Jul 16, 09:25 UTC | Jul 17, 01:25 UTC | 16h 0m |
| 2026-07-15 | QTR8940 | - | Jul 15, 09:55 UTC | Jul 16, 03:45 UTC | 17h 50m |
| 2026-07-15 | QTR8817 | - | Jul 15, 05:45 UTC | Jul 15, 06:20 UTC | 35m |
| 2026-07-15 | QTR8816 | - | Jul 15, 03:45 UTC | Jul 15, 04:20 UTC | 35m |
| 2026-07-14 | QTR8035 | - | Jul 14, 08:10 UTC | Jul 15, 02:35 UTC | 18h 24m |
| 2026-07-13 | QTR8963 | - | Jul 13, 12:05 UTC | Jul 14, 05:50 UTC | 17h 45m |
| 2026-07-13 | QTR8962 | - | Jul 13, 10:15 UTC | Jul 14, 05:50 UTC | 19h 35m |
| 2026-07-13 | QTR76G | - | Jul 13, 02:15 UTC | Jul 13, 08:01 UTC | 5h 45m |
| 2026-07-12 | QTR76G | - | Jul 12, 15:35 UTC | Jul 12, 23:55 UTC | 8h 20m |
| 2026-07-12 | QTR31T | MXP → ORD | Jul 12, 03:50 UTC | Jul 12, 13:01 UTC | 9h 10m |
| 2026-07-11 | QTR31T | - | Jul 11, 20:15 UTC | Jul 12, 01:40 UTC | 5h 25m |
| 2026-07-11 | QTR8473 | - | Jul 11, 11:55 UTC | Jul 11, 17:30 UTC | 5h 35m |
| 2026-07-11 | QTR8473 | - | Jul 11, 10:05 UTC | Jul 11, 10:20 UTC | 15m |
| 2026-07-10 | QTR8472 | - | Jul 10, 23:00 UTC | Jul 11, 07:15 UTC | 8h 15m |
| 2026-07-10 | QTR8252 | - | Jul 10, 15:25 UTC | Jul 10, 21:20 UTC | 5h 55m |
| 2026-07-10 | QTR90J | - | Jul 10, 05:55 UTC | Jul 10, 12:30 UTC | 6h 35m |
| 2026-07-09 | QTR8961 | - | Jul 9, 07:25 UTC | Jul 10, 01:15 UTC | 17h 50m |
| 2026-07-08 | QTR8939 | - | Jul 8, 10:35 UTC | Jul 9, 03:50 UTC | 17h 15m |
| 2026-07-07 | QTR8950 | - | Jul 7, 17:20 UTC | Jul 8, 08:25 UTC | 15h 5m |
| 2026-07-07 | QTR8025 | - | Jul 7, 01:25 UTC | Jul 7, 15:30 UTC | 14h 5m |
| 2026-07-06 | QTR8025 | - | Jul 6, 09:10 UTC | Jul 6, 22:50 UTC | 13h 40m |
| 2026-07-05 | QTR8024 | DOH → HKG | Jul 5, 23:00 UTC | Jul 6, 06:00 UTC | 7h 0m |
| 2026-07-05 | QTR35T | - | Jul 5, 12:05 UTC | Jul 5, 12:45 UTC | 40m |
| 2026-07-05 | QTR8726 | - | Jul 5, 09:20 UTC | Jul 5, 09:55 UTC | 35m |
| 2026-07-05 | QTR8367 | DEL → DOH | Jul 5, 02:50 UTC | Jul 5, 06:00 UTC | 3h 10m |
| 2026-07-04 | QTR8592 | - | Jul 4, 20:55 UTC | Jul 5, 00:10 UTC | 3h 15m |
| 2026-07-04 | QTR25Q | - | Jul 4, 16:55 UTC | Jul 4, 17:30 UTC | 35m |
| 2026-07-04 | QTR25Q | - | Jul 4, 11:50 UTC | Jul 4, 15:45 UTC | 3h 55m |
| 2026-07-04 | QTR40L | - | Jul 4, 02:30 UTC | Jul 4, 09:05 UTC | 6h 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-BFF page for operator, model, and routing details .