sensors Mode-S transponder
06A1EC
ICAO 24-bit transponder address · allocated to Qatar
Currently assigned to A7-BFO · BOEING 777-200LR
- Hex
- 06A1EC
- Octal
- 01520754
- Decimal
- 434,668
- Country
- QA
- Tail
- A7-BFO
- Type
- B77L
- Flights observed
- 136
- Distinct callsigns
- 20
- Country
- QA
- Last broadcast
- 9m ago
Last known position
Country allocation
The ICAO 24-bit address 06A1EC 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 |
|---|---|---|---|
| QTR8356 | Qatar Airways | 6 | 2026-05-08 |
| QTR8951 | Qatar Airways | 5 | 2026-05-30 |
| QTR8427 | - | 5 | 2026-05-27 |
| QTR99E | Qatar Airways | 4 | 2026-04-17 |
| QTR8961 | Qatar Airways | 4 | 2026-05-02 |
| QTR8426 | Qatar Airways | 4 | 2026-05-27 |
| QTR70R | - | 4 | 2026-04-15 |
| QTR66R | Qatar Airways | 4 | 2026-04-15 |
| QTR12B | - | 4 | 2026-04-17 |
| QTR8984 | Qatar Airways | 3 | 2026-05-05 |
| QTR8976 | - | 3 | 2026-05-16 |
| QTR8971 | Qatar Airways | 3 | 2026-04-29 |
| QTR8417 | Qatar Airways | 3 | 2026-05-14 |
| QTR8284 | Qatar Airways | 3 | 2026-04-23 |
| QTR8280 | Qatar Airways | 3 | 2026-05-24 |
| QTR8232 | Qatar Airways | 3 | 2026-04-27 |
| QTR8157 | Qatar Airways | 3 | 2026-05-19 |
| QTR8073 | Qatar Airways | 3 | 2026-04-25 |
| QTR8056 | - | 3 | 2026-05-12 |
| QTR3F | - | 3 | 2026-04-13 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | QTR8951 | HAN → DOH | May 30, 03:40 UTC | May 30, 05:00 UTC | 1h 20m |
| 2026-05-30 | QTR8951 | HAN → DOH | May 30, 02:55 UTC | May 30, 03:05 UTC | 10m |
| 2026-05-30 | QTR8950 | EDI → DUB | May 30, 00:20 UTC | May 30, 00:30 UTC | 10m |
| 2026-05-29 | QTR8950 | EDI → DUB | May 29, 19:55 UTC | May 29, 23:40 UTC | 3h 45m |
| 2026-05-29 | QTR8025 | HKG → DOH | May 29, 01:00 UTC | May 29, 14:25 UTC | 13h 25m |
| 2026-05-28 | QTR8024 | - | May 28, 20:30 UTC | May 28, 22:10 UTC | 1h 40m |
| 2026-05-27 | QTR8427 | - | May 27, 21:35 UTC | May 28, 21:00 UTC | 23h 25m |
| 2026-05-27 | QTR8427 | - | May 27, 18:35 UTC | May 27, 22:25 UTC | 3h 50m |
| 2026-05-27 | QTR8427 | - | May 27, 16:45 UTC | May 27, 16:55 UTC | 10m |
| 2026-05-27 | QTR8426 | DOH → HKG | May 27, 13:50 UTC | May 27, 14:30 UTC | 40m |
| 2026-05-27 | QTR8426 | DOH → HKG | May 27, 08:30 UTC | May 27, 11:45 UTC | 3h 15m |
| 2026-05-24 | QTR8280 | IST → DOH | May 24, 20:40 UTC | May 24, 21:15 UTC | 35m |
| 2026-05-24 | QTR8280 | IST → DOH | May 24, 16:10 UTC | May 24, 19:20 UTC | 3h 10m |
| 2026-05-24 | QTR8280 | IST → DOH | May 24, 13:00 UTC | May 24, 13:55 UTC | 55m |
| 2026-05-23 | QTR20X | - | May 23, 19:35 UTC | May 24, 01:10 UTC | 5h 35m |
| 2026-05-22 | QTR8943 | CAN → DOH | May 22, 21:40 UTC | May 23, 09:35 UTC | 11h 54m |
| 2026-05-22 | QTR8942 | DOH → CAN | May 22, 04:40 UTC | May 22, 14:45 UTC | 10h 5m |
| 2026-05-21 | QTR8427 | - | May 21, 08:40 UTC | May 22, 01:35 UTC | 16h 55m |
| 2026-05-21 | QTR8427 | - | May 21, 06:35 UTC | May 21, 06:50 UTC | 15m |
| 2026-05-21 | QTR8426 | DOH → HKG | May 21, 00:55 UTC | May 21, 01:35 UTC | 40m |
| 2026-05-20 | QTR8426 | DOH → HKG | May 20, 19:30 UTC | May 20, 22:35 UTC | 3h 5m |
| 2026-05-20 | QTR8158 | MST → PTY | May 20, 09:25 UTC | May 20, 15:15 UTC | 5h 50m |
| 2026-05-19 | QTR8158 | MST → PTY | May 19, 11:20 UTC | May 20, 06:50 UTC | 19h 31m |
| 2026-05-19 | QTR8157 | EZE → UIO | May 19, 09:40 UTC | May 20, 06:50 UTC | 21h 11m |
| 2026-05-18 | QTR8157 | EZE → UIO | May 18, 19:50 UTC | May 19, 07:15 UTC | 11h 25m |
| 2026-05-18 | QTR8157 | EZE → UIO | May 18, 09:35 UTC | May 18, 15:30 UTC | 5h 55m |
| 2026-05-17 | QTR8099 | MIA → LGG | May 17, 21:25 UTC | May 18, 03:15 UTC | 5h 50m |
| 2026-05-16 | QTR8098 | LOS → GRU | May 16, 23:10 UTC | May 17, 19:01 UTC | 19h 50m |
| 2026-05-16 | QTR8098 | LOS → GRU | May 16, 19:50 UTC | May 17, 17:01 UTC | 21h 10m |
| 2026-05-16 | QTR8976 | - | May 16, 07:05 UTC | May 17, 07:00 UTC | 23h 55m |
| 2026-05-16 | QTR8976 | - | May 16, 05:05 UTC | May 17, 04:35 UTC | 23h 31m |
| 2026-05-16 | QTR8976 | - | May 16, 03:55 UTC | May 17, 00:15 UTC | 20h 20m |
| 2026-05-15 | QTR8951 | HAN → DOH | May 15, 21:40 UTC | May 16, 20:35 UTC | 22h 55m |
| 2026-05-15 | QTR8951 | HAN → DOH | May 15, 13:05 UTC | May 16, 07:51 UTC | 18h 45m |
| 2026-05-15 | QTR8951 | HAN → DOH | May 15, 11:05 UTC | May 16, 07:51 UTC | 20h 45m |
| 2026-05-15 | QTR8405 | HKG → DOH | May 15, 09:15 UTC | May 16, 07:51 UTC | 22h 35m |
| 2026-05-15 | QTR8405 | HKG → DOH | May 15, 07:30 UTC | May 15, 07:45 UTC | 15m |
| 2026-05-14 | QTR8417 | HKG → DOH | May 14, 07:05 UTC | May 15, 02:45 UTC | 19h 40m |
| 2026-05-14 | QTR8417 | HKG → DOH | May 14, 06:20 UTC | May 15, 02:45 UTC | 20h 25m |
| 2026-05-14 | QTR8417 | HKG → DOH | May 14, 04:15 UTC | May 14, 04:30 UTC | 15m |
| 2026-05-13 | QTR8082 | MAD → OVD | May 13, 19:50 UTC | May 14, 01:25 UTC | 5h 35m |
| 2026-05-13 | QTR8057 | - | May 13, 08:55 UTC | May 13, 14:35 UTC | 5h 40m |
| 2026-05-13 | QTR8057 | - | May 13, 04:35 UTC | May 13, 06:10 UTC | 1h 35m |
| 2026-05-12 | QTR8056 | - | May 12, 07:05 UTC | May 13, 01:35 UTC | 18h 30m |
| 2026-05-12 | QTR8056 | - | May 12, 06:35 UTC | May 13, 01:35 UTC | 19h 0m |
| 2026-05-12 | QTR8083 | IKA → HKG | May 12, 04:00 UTC | May 12, 04:15 UTC | 15m |
| 2026-05-11 | QTR8082 | MAD → OVD | May 11, 20:00 UTC | May 11, 22:35 UTC | 2h 34m |
| 2026-05-10 | QTR8573 | ORD → LGG | May 10, 06:35 UTC | May 10, 07:10 UTC | 35m |
| 2026-05-09 | QTR8246 | MST → DOH | May 9, 18:20 UTC | May 10, 00:00 UTC | 5h 40m |
| 2026-05-09 | QTR8246 | MST → DOH | May 9, 14:50 UTC | May 9, 15:30 UTC | 40m |
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-BFO page for operator, model, and routing details .