sensors Mode-S transponder
06A30D
ICAO 24-bit transponder address · allocated to Qatar
Currently assigned to A7-BFZ · BOEING 777-200LR
- Hex
- 06A30D
- Octal
- 01521415
- Decimal
- 434,957
- Country
- QA
- Tail
- A7-BFZ
- Type
- B77L
- Flights observed
- 143
- Distinct callsigns
- 20
- Country
- QA
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address 06A30D 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 |
|---|---|---|---|
| QTR8099 | Qatar Airways | 12 | 2026-04-16 |
| QTR8162 | Qatar Airways | 8 | 2026-04-17 |
| QTR8163 | Qatar Airways | 7 | 2026-04-18 |
| QTR8098 | Qatar Airways | 7 | 2026-04-15 |
| QTR8963 | Qatar Airways | 6 | 2026-05-20 |
| QTR8464 | Qatar Airways | 6 | 2026-05-19 |
| QTR8962 | Qatar Airways | 5 | 2026-05-18 |
| QTR8465 | Qatar Airways | 5 | 2026-05-19 |
| QTR8090 | Qatar Airways | 5 | 2026-05-25 |
| QTR31T | Qatar Airways | 4 | 2026-05-27 |
| QTR8996 | - | 3 | 2026-05-21 |
| QTR8596 | Qatar Airways | 3 | 2026-05-16 |
| QTR8475 | Qatar Airways | 3 | 2026-04-24 |
| QTR8432 | Qatar Airways | 3 | 2026-04-26 |
| QTR8408 | Qatar Airways | 3 | 2026-05-31 |
| QTR8040 | Qatar Airways | 3 | 2026-05-07 |
| QTR90G | Qatar Airways | 2 | 2026-05-25 |
| QTR8945 | Qatar Airways | 2 | 2026-04-21 |
| QTR8944 | Qatar Airways | 2 | 2026-04-21 |
| QTR8943 | Qatar Airways | 2 | 2026-05-29 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | QTR8439 | THE → GRU | Jun 2, 18:45 UTC | Jun 2, 23:10 UTC | 4h 25m |
| 2026-06-02 | QTR8439 | THE → GRU | Jun 2, 18:00 UTC | Jun 2, 18:10 UTC | 10m |
| 2026-06-02 | QTR8438 | GRU → VIX | Jun 2, 10:10 UTC | Jun 2, 15:45 UTC | 5h 35m |
| 2026-06-01 | QTR8264 | MAD → IST | Jun 1, 22:35 UTC | Jun 2, 04:55 UTC | 6h 20m |
| 2026-06-01 | QTR5L | DOH → SYD | Jun 1, 02:20 UTC | Jun 1, 19:45 UTC | 17h 25m |
| 2026-05-31 | QTR8408 | SIN → HKG | May 31, 23:25 UTC | May 31, 23:50 UTC | 25m |
| 2026-05-31 | QTR8408 | SIN → HKG | May 31, 20:25 UTC | May 31, 20:40 UTC | 15m |
| 2026-05-30 | QTR8408 | SIN → HKG | May 30, 21:20 UTC | May 31, 17:15 UTC | 19h 55m |
| 2026-05-30 | QTR8266 | MXP → DOH | May 30, 19:20 UTC | May 31, 17:15 UTC | 21h 55m |
| 2026-05-30 | QTR29G | - | May 30, 06:30 UTC | May 30, 13:10 UTC | 6h 40m |
| 2026-05-29 | QTR8943 | CAN → DOH | May 29, 12:10 UTC | May 30, 02:00 UTC | 13h 50m |
| 2026-05-29 | QTR8943 | CAN → DOH | May 29, 04:40 UTC | May 30, 02:00 UTC | 21h 20m |
| 2026-05-28 | QTR76G | DOH → MAN | May 28, 13:00 UTC | May 28, 18:35 UTC | 5h 35m |
| 2026-05-28 | QTR76G | DOH → MAN | May 28, 02:30 UTC | May 28, 11:00 UTC | 8h 30m |
| 2026-05-27 | QTR31T | DOH → MXP | May 27, 14:15 UTC | May 27, 22:50 UTC | 8h 35m |
| 2026-05-27 | QTR31T | DOH → MXP | May 27, 07:35 UTC | May 27, 11:05 UTC | 3h 30m |
| 2026-05-26 | QTR46U | - | May 26, 15:29 UTC | May 26, 21:04 UTC | 5h 35m |
| 2026-05-25 | QTR90G | DOH → MIA | May 25, 22:00 UTC | May 26, 12:54 UTC | 14h 55m |
| 2026-05-25 | QTR8090 | MAD → XRY | May 25, 03:40 UTC | May 25, 19:25 UTC | 15h 44m |
| 2026-05-24 | QTR8090 | MAD → XRY | May 24, 23:30 UTC | May 25, 19:25 UTC | 19h 55m |
| 2026-05-24 | QTR8090 | MAD → XRY | May 24, 20:15 UTC | May 25, 19:15 UTC | 23h 0m |
| 2026-05-24 | QTR8975 | - | May 24, 11:45 UTC | May 25, 07:55 UTC | 20h 10m |
| 2026-05-24 | QTR8694 | DOH → BLR | May 24, 07:50 UTC | May 24, 09:15 UTC | 1h 25m |
| 2026-05-23 | QTR8419 | HKG → DOH | May 23, 21:05 UTC | May 24, 03:00 UTC | 5h 55m |
| 2026-05-23 | QTR8419 | HKG → DOH | May 23, 19:10 UTC | May 23, 19:20 UTC | 10m |
| 2026-05-23 | QTR8418 | POA → GRU | May 23, 12:45 UTC | May 23, 16:05 UTC | 3h 20m |
| 2026-05-23 | QTR8418 | POA → GRU | May 23, 09:30 UTC | May 23, 10:50 UTC | 1h 20m |
| 2026-05-21 | QTR8996 | - | May 21, 10:15 UTC | May 21, 23:00 UTC | 12h 45m |
| 2026-05-21 | QTR8996 | - | May 21, 02:00 UTC | May 21, 23:00 UTC | 21h 0m |
| 2026-05-21 | QTR8996 | - | May 21, 00:00 UTC | May 21, 23:00 UTC | 23h 0m |
| 2026-05-20 | QTR8963 | PVG → DOH | May 20, 13:20 UTC | May 21, 12:50 UTC | 23h 30m |
| 2026-05-20 | QTR8963 | PVG → DOH | May 20, 11:20 UTC | May 21, 10:50 UTC | 23h 30m |
| 2026-05-20 | QTR8963 | PVG → DOH | May 20, 11:10 UTC | May 21, 03:00 UTC | 15h 50m |
| 2026-05-19 | QTR8465 | HKG → DOH | May 19, 21:00 UTC | May 20, 13:45 UTC | 16h 46m |
| 2026-05-19 | QTR8465 | HKG → DOH | May 19, 18:55 UTC | May 19, 19:05 UTC | 10m |
| 2026-05-19 | QTR8464 | DOH → SYD | May 19, 00:00 UTC | May 19, 15:55 UTC | 15h 55m |
| 2026-05-18 | QTR8464 | DOH → SYD | May 18, 13:25 UTC | May 19, 13:10 UTC | 23h 44m |
| 2026-05-18 | QTR8963 | PVG → DOH | May 18, 11:20 UTC | May 19, 11:10 UTC | 23h 49m |
| 2026-05-18 | QTR8962 | DOH → PVG | May 18, 11:10 UTC | May 19, 03:10 UTC | 15h 59m |
| 2026-05-18 | QTR8962 | DOH → PVG | May 18, 01:25 UTC | May 19, 00:50 UTC | 23h 24m |
| 2026-05-17 | QTR8962 | DOH → PVG | May 17, 22:20 UTC | May 18, 14:20 UTC | 16h 0m |
| 2026-05-17 | QTR8949 | SZX → DOH | May 17, 20:30 UTC | May 17, 20:40 UTC | 10m |
| 2026-05-17 | QTR8839 | YMX → MXP | May 17, 01:15 UTC | May 17, 14:30 UTC | 13h 15m |
| 2026-05-16 | QTR8839 | YMX → MXP | May 16, 08:46 UTC | May 16, 16:05 UTC | 7h 20m |
| 2026-05-16 | QTR8596 | OMA → ORD | May 16, 04:00 UTC | May 16, 06:01 UTC | 2h 1m |
| 2026-05-15 | QTR8596 | OMA → ORD | May 15, 16:00 UTC | May 16, 00:20 UTC | 8h 20m |
| 2026-05-15 | QTR8596 | OMA → ORD | May 15, 06:55 UTC | May 15, 13:25 UTC | 6h 30m |
| 2026-05-13 | QTR8941 | CAN → DOH | May 13, 22:10 UTC | May 14, 02:05 UTC | 3h 55m |
| 2026-05-12 | QTR8465 | HKG → DOH | May 12, 22:35 UTC | May 13, 14:40 UTC | 16h 5m |
| 2026-05-12 | QTR8465 | HKG → DOH | May 12, 20:30 UTC | May 12, 20:40 UTC | 10m |
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-BFZ page for operator, model, and routing details .