sensors Mode-S transponder
06A2E3
ICAO 24-bit transponder address · allocated to Qatar
Currently assigned to A7-BFV · BOEING 777-200LR
- Hex
- 06A2E3
- Octal
- 01521343
- Decimal
- 434,915
- Country
- QA
- Tail
- A7-BFV
- Type
- B77L
- Flights observed
- 263
- Distinct callsigns
- 20
- Country
- QA
- Last broadcast
- 7h ago
Last known position
Country allocation
The ICAO 24-bit address 06A2E3 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 |
|---|---|---|---|
| QTR8942 | Qatar Airways | 7 | 2026-06-07 |
| QTR8432 | Qatar Airways | 6 | 2026-05-30 |
| QTR40T | - | 6 | 2026-06-01 |
| QTR8941 | - | 5 | 2026-07-08 |
| QTR8430 | - | 5 | 2026-06-20 |
| QTR8401 | - | 5 | 2026-07-10 |
| QTR8151 | - | 5 | 2026-07-12 |
| QTR30G | Qatar Airways | 5 | 2026-06-01 |
| QTR8951 | - | 4 | 2026-06-27 |
| QTR8470 | Qatar Airways | 4 | 2026-06-17 |
| QTR8407 | - | 4 | 2026-06-30 |
| QTR8262 | - | 4 | 2026-04-13 |
| QTR8175 | Qatar Airways | 4 | 2026-04-27 |
| QTR8147 | Qatar Airways | 4 | 2026-06-11 |
| QTR8062 | Qatar Airways | 4 | 2026-07-01 |
| QTR46P | Qatar Airways | 4 | 2026-05-06 |
| QTR8943 | Qatar Airways | 3 | 2026-04-17 |
| QTR8833 | - | 3 | 2026-04-25 |
| QTR8596 | - | 3 | 2026-06-22 |
| QTR8471 | Qatar Airways | 3 | 2026-06-17 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | QTR2A | - | Jul 14, 17:50 UTC | Jul 14, 19:00 UTC | 1h 10m |
| 2026-07-14 | QTR2A | - | Jul 14, 08:10 UTC | Jul 14, 15:20 UTC | 7h 10m |
| 2026-07-13 | QTR55P | - | Jul 13, 12:25 UTC | Jul 13, 22:15 UTC | 9h 50m |
| 2026-07-13 | QTR55P | - | Jul 13, 02:25 UTC | Jul 13, 22:15 UTC | 19h 50m |
| 2026-07-12 | QTR8151 | - | Jul 12, 17:05 UTC | Jul 12, 23:10 UTC | 6h 5m |
| 2026-07-12 | QTR8151 | ORD → AMS | Jul 12, 05:25 UTC | Jul 12, 13:01 UTC | 7h 35m |
| 2026-07-11 | QTR8150 | AMS → ORD | Jul 11, 18:50 UTC | Jul 12, 02:55 UTC | 8h 5m |
| 2026-07-11 | QTR24A | DOH → AMS | Jul 11, 08:55 UTC | Jul 11, 15:50 UTC | 6h 55m |
| 2026-07-11 | QTR47V | - | Jul 11, 02:55 UTC | Jul 11, 05:20 UTC | 2h 25m |
| 2026-07-10 | QTR8612 | - | Jul 10, 21:35 UTC | Jul 11, 00:10 UTC | 2h 35m |
| 2026-07-10 | QTR72U | - | Jul 10, 13:10 UTC | Jul 10, 19:05 UTC | 5h 55m |
| 2026-07-10 | QTR72U | PRG → OSL | Jul 10, 09:35 UTC | Jul 10, 11:10 UTC | 1h 35m |
| 2026-07-10 | QTR8209 | - | Jul 10, 02:15 UTC | Jul 10, 07:15 UTC | 5h 0m |
| 2026-07-10 | QTR8401 | - | Jul 10, 00:10 UTC | Jul 10, 00:25 UTC | 15m |
| 2026-07-09 | QTR8401 | - | Jul 9, 18:35 UTC | Jul 9, 22:30 UTC | 3h 55m |
| 2026-07-09 | QTR8401 | - | Jul 9, 16:50 UTC | Jul 9, 17:05 UTC | 15m |
| 2026-07-09 | QTR8400 | - | Jul 9, 06:55 UTC | Jul 9, 15:05 UTC | 8h 10m |
| 2026-07-08 | QTR8941 | - | Jul 8, 20:10 UTC | Jul 9, 03:25 UTC | 7h 15m |
| 2026-07-08 | QTR8940 | - | Jul 8, 09:45 UTC | Jul 8, 15:35 UTC | 5h 50m |
| 2026-07-07 | QTR8173 | DFW → DOH | Jul 7, 17:50 UTC | Jul 8, 08:05 UTC | 14h 15m |
| 2026-07-07 | QTR8172 | LGG → DFW | Jul 7, 04:35 UTC | Jul 7, 14:10 UTC | 9h 35m |
| 2026-07-06 | QTR8172 | - | Jul 6, 20:10 UTC | Jul 7, 02:10 UTC | 6h 0m |
| 2026-07-06 | QTR8401 | - | Jul 6, 10:40 UTC | Jul 6, 17:30 UTC | 6h 50m |
| 2026-07-06 | QTR8401 | - | Jul 6, 09:50 UTC | Jul 6, 10:05 UTC | 15m |
| 2026-07-05 | QTR8400 | - | Jul 5, 22:50 UTC | Jul 6, 07:00 UTC | 8h 10m |
| 2026-07-05 | QTR8151 | - | Jul 5, 20:10 UTC | Jul 5, 20:45 UTC | 35m |
| 2026-07-05 | QTR8151 | - | Jul 5, 15:00 UTC | Jul 5, 19:05 UTC | 4h 5m |
| 2026-07-05 | QTR8151 | ORD → AMS | Jul 5, 05:40 UTC | Jul 5, 12:55 UTC | 7h 15m |
| 2026-07-04 | QTR8150 | AMS → ORD | Jul 4, 18:25 UTC | Jul 5, 02:45 UTC | 8h 20m |
| 2026-07-04 | QTR24A | - | Jul 4, 08:45 UTC | Jul 4, 15:15 UTC | 6h 30m |
| 2026-07-03 | QTR8941 | - | Jul 3, 11:30 UTC | Jul 4, 04:50 UTC | 17h 20m |
| 2026-07-02 | QTR8923 | - | Jul 2, 23:40 UTC | Jul 3, 09:35 UTC | 9h 55m |
| 2026-07-02 | QTR8922 | - | Jul 2, 12:40 UTC | Jul 2, 20:05 UTC | 7h 25m |
| 2026-07-01 | QTR8063 | CDG → DOH | Jul 1, 21:40 UTC | Jul 2, 10:05 UTC | 12h 25m |
| 2026-07-01 | QTR8062 | DOH → JFK | Jul 1, 09:25 UTC | Jul 1, 18:15 UTC | 8h 50m |
| 2026-07-01 | QTR8062 | DOH → JFK | Jul 1, 02:05 UTC | Jul 1, 07:45 UTC | 5h 40m |
| 2026-06-30 | QTR8031 | - | Jun 30, 18:05 UTC | Jun 30, 23:35 UTC | 5h 30m |
| 2026-06-30 | QTR8030 | DOH → LEJ | Jun 30, 09:15 UTC | Jun 30, 14:55 UTC | 5h 40m |
| 2026-06-30 | QTR8407 | - | Jun 30, 00:35 UTC | Jun 30, 07:15 UTC | 6h 41m |
| 2026-06-29 | QTR8407 | - | Jun 29, 23:44 UTC | Jun 29, 23:54 UTC | 10m |
| 2026-06-29 | QTR8406 | - | Jun 29, 12:00 UTC | Jun 29, 19:49 UTC | 7h 50m |
| 2026-06-28 | QTR8961 | - | Jun 28, 09:30 UTC | Jun 29, 03:25 UTC | 17h 55m |
| 2026-06-28 | QTR8961 | - | Jun 28, 07:40 UTC | Jun 29, 03:25 UTC | 19h 45m |
| 2026-06-27 | QTR8968 | DOH → DOH | Jun 27, 12:19 UTC | Jun 28, 04:15 UTC | 15h 55m |
| 2026-06-27 | QTR8951 | - | Jun 27, 03:55 UTC | Jun 27, 09:24 UTC | 5h 30m |
| 2026-06-27 | QTR8951 | - | Jun 27, 03:15 UTC | Jun 27, 03:25 UTC | 10m |
| 2026-06-26 | QTR8950 | EDI → DUB | Jun 26, 17:59 UTC | Jun 27, 00:20 UTC | 6h 20m |
| 2026-06-26 | QTR8737 | - | Jun 26, 15:10 UTC | Jun 26, 15:49 UTC | 40m |
| 2026-06-26 | QTR8736 | DOH → AUH | Jun 26, 12:14 UTC | Jun 26, 12:50 UTC | 35m |
| 2026-06-26 | QTR8045 | MAD → MLN | Jun 26, 04:34 UTC | Jun 26, 10:35 UTC | 6h 0m |
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-BFV page for operator, model, and routing details .