sensors Mode-S transponder
06A1BC
ICAO 24-bit transponder address · allocated to Qatar
Currently assigned to A7-BEF · BOEING 777-300ER
- Hex
- 06A1BC
- Octal
- 01520674
- Decimal
- 434,620
- Country
- QA
- Tail
- A7-BEF
- Type
- B77W
- Flights observed
- 181
- Distinct callsigns
- 20
- Country
- QA
- Last broadcast
- Jul 26, 22:10 UTC
Last known position
Country allocation
The ICAO 24-bit address 06A1BC 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 |
|---|---|---|---|
| QTR838 | Qatar Airways | 8 | 2026-05-13 |
| QTR18F | Qatar Airways | 7 | 2026-07-24 |
| QTR839 | Qatar Airways | 6 | 2026-05-14 |
| QTR933 | Qatar Airways | 5 | 2026-06-01 |
| QTR932 | Qatar Airways | 5 | 2026-06-01 |
| QTR809 | - | 5 | 2026-07-17 |
| QTR28U | Qatar Airways | 5 | 2026-06-14 |
| QTR27F | Qatar Airways | 5 | 2026-05-07 |
| QTR1F | Qatar Airways | 5 | 2026-05-07 |
| QTR1V | Qatar Airways | 4 | 2026-06-13 |
| VOZ008 | - | 3 | 2026-07-11 |
| VOZ007 | - | 3 | 2026-07-13 |
| QTR858 | Qatar Airways | 3 | 2026-05-30 |
| QTR837 | Qatar Airways | 3 | 2026-06-10 |
| QTR836 | Qatar Airways | 3 | 2026-06-10 |
| QTR817 | Qatar Airways | 3 | 2026-05-29 |
| QTR814 | Qatar Airways | 3 | 2026-05-28 |
| QTR808 | - | 3 | 2026-07-16 |
| QTR6W | Qatar Airways | 3 | 2026-07-20 |
| QTR47Y | Qatar Airways | 3 | 2026-06-14 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | QTR27R | - | Jul 26, 11:45 UTC | Jul 26, 22:10 UTC | 10h 25m |
| 2026-07-25 | QTR40X | - | Jul 25, 17:40 UTC | Jul 26, 06:55 UTC | 13h 16m |
| 2026-07-25 | QTR65R | SEA → DOH | Jul 25, 00:35 UTC | Jul 25, 12:45 UTC | 12h 10m |
| 2026-07-24 | QTR18F | BUD → DOH | Jul 24, 07:55 UTC | Jul 24, 19:35 UTC | 11h 40m |
| 2026-07-23 | QTR32N | DOH → SJJ | Jul 23, 22:35 UTC | Jul 24, 02:15 UTC | 3h 40m |
| 2026-07-23 | QTR572 | DOH → BLR | Jul 23, 17:00 UTC | Jul 23, 20:40 UTC | 3h 40m |
| 2026-07-23 | QTR68T | SEA → DOH | Jul 23, 00:10 UTC | Jul 23, 14:35 UTC | 14h 25m |
| 2026-07-22 | QTR21X | DOH → SEA | Jul 22, 11:45 UTC | Jul 22, 20:30 UTC | 8h 45m |
| 2026-07-21 | QTR411 | - | Jul 21, 13:25 UTC | Jul 21, 14:20 UTC | 55m |
| 2026-07-21 | QTR411 | - | Jul 21, 11:35 UTC | Jul 21, 12:05 UTC | 30m |
| 2026-07-21 | QTR410 | - | Jul 21, 06:25 UTC | Jul 21, 08:40 UTC | 2h 15m |
| 2026-07-20 | QTR6W | ORD → DOH | Jul 20, 02:00 UTC | Jul 20, 14:50 UTC | 12h 50m |
| 2026-07-19 | QTR18F | BUD → DOH | Jul 19, 10:55 UTC | Jul 19, 20:35 UTC | 9h 40m |
| 2026-07-18 | QTR18F | BUD → DOH | Jul 18, 21:35 UTC | Jul 19, 19:00 UTC | 21h 25m |
| 2026-07-18 | QTR18F | BUD → DOH | Jul 18, 15:05 UTC | Jul 19, 13:50 UTC | 22h 45m |
| 2026-07-18 | QTR9W | DOH → NCE | Jul 18, 14:40 UTC | Jul 19, 13:00 UTC | 22h 20m |
| 2026-07-17 | QTR809 | - | Jul 17, 15:05 UTC | Jul 18, 10:25 UTC | 19h 21m |
| 2026-07-17 | QTR809 | - | Jul 17, 13:55 UTC | Jul 18, 10:25 UTC | 20h 31m |
| 2026-07-17 | QTR809 | - | Jul 17, 09:04 UTC | Jul 17, 17:20 UTC | 8h 15m |
| 2026-07-16 | QTR808 | - | Jul 16, 18:10 UTC | Jul 17, 03:55 UTC | 9h 45m |
| 2026-07-16 | QTR36A | - | Jul 16, 02:35 UTC | Jul 16, 09:05 UTC | 6h 30m |
| 2026-07-15 | QTR90C | - | Jul 15, 17:05 UTC | Jul 16, 00:15 UTC | 7h 10m |
| 2026-07-15 | QTR6W | - | Jul 15, 01:25 UTC | Jul 15, 14:25 UTC | 13h 0m |
| 2026-07-14 | QTR18F | - | Jul 14, 06:45 UTC | Jul 14, 07:15 UTC | 30m |
| 2026-07-13 | VOZ007 | - | Jul 13, 06:45 UTC | Jul 13, 20:35 UTC | 13h 50m |
| 2026-07-11 | VOZ008 | - | Jul 11, 23:20 UTC | Jul 12, 12:15 UTC | 12h 55m |
| 2026-07-11 | QTR6W | IAD → DOH | Jul 11, 01:20 UTC | Jul 11, 14:05 UTC | 12h 45m |
| 2026-07-10 | QTR18F | - | Jul 10, 06:00 UTC | Jul 10, 19:35 UTC | 13h 35m |
| 2026-07-09 | QTR15K | - | Jul 9, 18:50 UTC | Jul 10, 00:45 UTC | 5h 55m |
| 2026-07-09 | QTR74G | - | Jul 9, 00:30 UTC | Jul 9, 05:30 UTC | 5h 0m |
| 2026-07-08 | QTR74G | - | Jul 8, 22:50 UTC | Jul 8, 23:10 UTC | 20m |
| 2026-07-08 | VOZ007 | - | Jul 8, 06:30 UTC | Jul 8, 19:45 UTC | 13h 15m |
| 2026-07-06 | VOZ008 | - | Jul 6, 23:10 UTC | Jul 7, 12:00 UTC | 12h 50m |
| 2026-07-06 | QTR809 | - | Jul 6, 09:00 UTC | Jul 6, 19:50 UTC | 10h 50m |
| 2026-07-05 | QTR808 | - | Jul 5, 18:05 UTC | Jul 6, 04:00 UTC | 9h 55m |
| 2026-07-05 | QTR65R | - | Jul 5, 02:00 UTC | Jul 5, 14:20 UTC | 12h 20m |
| 2026-07-04 | QTR18F | - | Jul 4, 05:45 UTC | Jul 4, 19:25 UTC | 13h 40m |
| 2026-07-03 | QTR807 | NRT → DOH | Jul 3, 13:35 UTC | Jul 4, 00:20 UTC | 10h 45m |
| 2026-07-03 | QTR806 | - | Jul 3, 00:10 UTC | Jul 3, 10:05 UTC | 9h 55m |
| 2026-07-02 | VOZ001 | - | Jul 2, 05:05 UTC | Jul 2, 19:20 UTC | 14h 15m |
| 2026-07-01 | VOZ002 | - | Jul 1, 07:00 UTC | Jul 1, 20:10 UTC | 13h 10m |
| 2026-06-30 | QTR9W | - | Jun 30, 14:45 UTC | Jul 1, 01:30 UTC | 10h 45m |
| 2026-06-29 | QTR64V | - | Jun 29, 23:49 UTC | Jun 30, 10:20 UTC | 10h 31m |
| 2026-06-29 | QTR9J | - | Jun 29, 06:19 UTC | Jun 29, 10:04 UTC | 3h 45m |
| 2026-06-28 | QTR2L | - | Jun 28, 23:34 UTC | Jun 29, 03:44 UTC | 4h 10m |
| 2026-06-28 | QTR846 | - | Jun 28, 05:45 UTC | Jun 28, 20:29 UTC | 14h 45m |
| 2026-06-27 | QTR807 | - | Jun 27, 13:44 UTC | Jun 28, 00:20 UTC | 10h 35m |
| 2026-06-27 | QTR806 | - | Jun 27, 00:25 UTC | Jun 27, 10:05 UTC | 9h 40m |
| 2026-06-26 | VOZ001 | SYD → DOH | Jun 26, 05:10 UTC | Jun 26, 19:24 UTC | 14h 15m |
| 2026-06-25 | VOZ002 | - | Jun 25, 06:20 UTC | Jun 25, 20:05 UTC | 13h 45m |
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-BEF page for operator, model, and routing details .