sensors Mode-S transponder
896119
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-ECR · BOEING 777-300ER
- Hex
- 896119
- Octal
- 42260431
- Decimal
- 9,003,289
- Country
- AE
- Tail
- A6-ECR
- Type
- B77W
- Flights observed
- 81
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 3h ago
Last known position
Country allocation
The ICAO 24-bit address 896119 falls within the block assigned to United Arab Emirates (AE) by ICAO Annex 10, Volume III. Every aircraft registered in United Arab Emirates 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 |
|---|---|---|---|
| UAE69R | - | 6 | 2026-04-13 |
| UAE3MX | Emirates | 6 | 2026-05-26 |
| UAE797 | Emirates | 5 | 2026-05-05 |
| UAE8UW | Emirates | 4 | 2026-04-15 |
| UAE2W | Emirates | 4 | 2026-04-16 |
| UAE145 | Emirates | 4 | 2026-04-16 |
| UAE349 | Emirates | 3 | 2026-05-04 |
| UAE348 | Emirates | 3 | 2026-05-04 |
| UAE232 | Emirates | 3 | 2026-05-27 |
| UAE9U | Emirates | 2 | 2026-04-24 |
| UAE9974 | Emirates | 2 | 2026-05-29 |
| UAE9968 | Emirates | 2 | 2026-05-22 |
| UAE9967 | - | 2 | 2026-05-21 |
| UAE7Y | Emirates | 2 | 2026-04-24 |
| UAE359 | Emirates | 2 | 2026-04-20 |
| UAE333 | Emirates | 2 | 2026-04-23 |
| UAE332 | Emirates | 2 | 2026-04-23 |
| UAE31T | Emirates | 2 | 2026-04-22 |
| UAE248 | Emirates | 2 | 2026-04-26 |
| UAE247 | Emirates | 2 | 2026-04-25 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | UAE9974 | FRA → DXB | May 29, 15:15 UTC | May 29, 21:15 UTC | 6h 0m |
| 2026-05-29 | UAE9974 | FRA → DXB | May 29, 11:00 UTC | May 29, 12:40 UTC | 1h 40m |
| 2026-05-28 | UAE9973 | DXB → FRA | May 28, 15:45 UTC | May 29, 08:40 UTC | 16h 55m |
| 2026-05-27 | UAE232 | IAD → DXB | May 27, 16:20 UTC | May 28, 13:15 UTC | 20h 55m |
| 2026-05-27 | UAE232 | IAD → DXB | May 27, 15:45 UTC | May 28, 13:15 UTC | 21h 30m |
| 2026-05-26 | UAE3MX | DXB → IAD | May 26, 22:54 UTC | May 27, 12:50 UTC | 13h 56m |
| 2026-05-22 | UAE9968 | DFW → DWC | May 22, 05:50 UTC | May 22, 18:50 UTC | 13h 0m |
| 2026-05-21 | UAE9968 | DFW → DWC | May 21, 23:20 UTC | May 22, 01:00 UTC | 1h 40m |
| 2026-05-21 | UAE9967 | - | May 21, 10:20 UTC | May 21, 20:25 UTC | 10h 5m |
| 2026-05-21 | UAE9967 | - | May 21, 03:50 UTC | May 21, 08:15 UTC | 4h 25m |
| 2026-05-17 | UAE304 | DXB → PVG | May 17, 16:01 UTC | May 18, 06:40 UTC | 14h 40m |
| 2026-05-07 | UAE958 | BEY → DXB | May 7, 13:40 UTC | May 7, 16:10 UTC | 2h 30m |
| 2026-05-06 | UAE20 | MAN → DXB | May 6, 21:10 UTC | May 7, 00:45 UTC | 3h 35m |
| 2026-05-06 | UAE19 | DXB → MAN | May 6, 13:20 UTC | May 6, 18:25 UTC | 5h 4m |
| 2026-05-05 | UAE797 | DXB → DKR | May 5, 21:01 UTC | May 6, 05:55 UTC | 8h 54m |
| 2026-05-05 | UAE797 | DXB → DKR | May 5, 12:20 UTC | May 5, 18:50 UTC | 6h 30m |
| 2026-05-04 | UAE349 | SIN → DXB | May 4, 18:35 UTC | May 5, 01:10 UTC | 6h 35m |
| 2026-05-04 | UAE348 | DXB → SIN | May 4, 08:00 UTC | May 4, 15:10 UTC | 7h 10m |
| 2026-05-03 | UAE348 | DXB → SIN | May 3, 22:54 UTC | May 4, 05:20 UTC | 6h 25m |
| 2026-05-03 | UAE4P | NBO → DXB | May 3, 18:05 UTC | May 3, 18:34 UTC | 30m |
| 2026-05-03 | UAE719 | DXB → NBO | May 3, 07:30 UTC | May 3, 07:45 UTC | 15m |
| 2026-05-02 | UAE797 | DXB → DKR | May 2, 19:55 UTC | May 3, 03:55 UTC | 7h 59m |
| 2026-05-02 | UAE797 | DXB → DKR | May 2, 17:30 UTC | May 2, 18:00 UTC | 30m |
| 2026-05-02 | UAE797 | DXB → DKR | May 2, 04:25 UTC | May 2, 05:30 UTC | 1h 5m |
| 2026-05-01 | UAE349 | SIN → DXB | May 1, 18:15 UTC | May 2, 01:00 UTC | 6h 45m |
| 2026-05-01 | UAE349 | SIN → DXB | May 1, 08:05 UTC | May 1, 15:35 UTC | 7h 30m |
| 2026-04-30 | UAE348 | DXB → SIN | Apr 30, 22:50 UTC | May 1, 05:40 UTC | 6h 50m |
| 2026-04-29 | UAE60L | CPT → DXB | Apr 29, 16:45 UTC | Apr 30, 01:35 UTC | 8h 49m |
| 2026-04-29 | UAE23C | DXB → CPT | Apr 29, 05:30 UTC | Apr 29, 14:30 UTC | 9h 1m |
| 2026-04-28 | UAE9Q | COK → DXB | Apr 28, 23:20 UTC | Apr 29, 02:50 UTC | 3h 30m |
| 2026-04-28 | UAE8M | DXB → COK | Apr 28, 17:45 UTC | Apr 28, 21:10 UTC | 3h 25m |
| 2026-04-26 | UAE248 | GIG → DXB | Apr 26, 06:30 UTC | Apr 26, 20:00 UTC | 13h 30m |
| 2026-04-26 | UAE248 | GIG → DXB | Apr 26, 01:50 UTC | Apr 26, 04:05 UTC | 2h 15m |
| 2026-04-25 | UAE247 | GIG → EZE | Apr 25, 20:50 UTC | Apr 25, 23:55 UTC | 3h 5m |
| 2026-04-25 | UAE247 | GIG → EZE | Apr 25, 04:35 UTC | Apr 25, 19:05 UTC | 14h 30m |
| 2026-04-24 | UAE7Y | BOM → DXB | Apr 24, 19:40 UTC | Apr 24, 20:00 UTC | 20m |
| 2026-04-24 | UAE7Y | BOM → DXB | Apr 24, 17:40 UTC | Apr 24, 18:05 UTC | 25m |
| 2026-04-24 | UAE508 | DXB → BOM | Apr 24, 12:15 UTC | Apr 24, 15:05 UTC | 2h 50m |
| 2026-04-24 | UAE583 | DAC → DXB | Apr 24, 04:50 UTC | Apr 24, 09:15 UTC | 4h 25m |
| 2026-04-24 | UAE9U | DXB → DAC | Apr 24, 01:50 UTC | Apr 24, 02:45 UTC | 55m |
| 2026-04-23 | UAE9U | DXB → DAC | Apr 23, 22:40 UTC | Apr 23, 23:05 UTC | 25m |
| 2026-04-23 | UAE333 | MNL → DXB | Apr 23, 18:25 UTC | Apr 23, 18:55 UTC | 30m |
| 2026-04-23 | UAE333 | MNL → DXB | Apr 23, 10:20 UTC | Apr 23, 15:15 UTC | 4h 55m |
| 2026-04-23 | UAE332 | DXB → MNL | Apr 23, 03:05 UTC | Apr 23, 07:40 UTC | 4h 36m |
| 2026-04-22 | UAE332 | DXB → MNL | Apr 22, 23:55 UTC | Apr 23, 00:20 UTC | 25m |
| 2026-04-22 | UAE31T | BLR → DXB | Apr 22, 15:50 UTC | Apr 22, 19:10 UTC | 3h 20m |
| 2026-04-22 | UAE566 | DXB → BLR | Apr 22, 10:05 UTC | Apr 22, 13:15 UTC | 3h 10m |
| 2026-04-22 | UAE9Y | PEW → DXB | Apr 22, 06:55 UTC | Apr 22, 07:15 UTC | 20m |
| 2026-04-22 | UAE20T | DXB → PEW | Apr 22, 00:05 UTC | Apr 22, 00:30 UTC | 25m |
| 2026-04-21 | UAE158 | ARN → DXB | Apr 21, 13:50 UTC | Apr 21, 20:20 UTC | 6h 30m |
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 A6-ECR page for operator, model, and routing details .