sensors Mode-S transponder
896111
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-ECJ · BOEING 777-300ER
- Hex
- 896111
- Octal
- 42260421
- Decimal
- 9,003,281
- Country
- AE
- Tail
- A6-ECJ
- Type
- B77W
- Flights observed
- 85
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 2h ago
Current position
Country allocation
The ICAO 24-bit address 896111 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 |
|---|---|---|---|
| UAE7AM | Emirates | 4 | 2026-04-17 |
| UAE331 | - | 4 | 2026-05-28 |
| UAE330 | - | 4 | 2026-05-27 |
| UAE9U | Emirates | 3 | 2026-04-16 |
| UAE583 | Emirates | 3 | 2026-04-16 |
| UAE51P | Emirates | 3 | 2026-04-17 |
| UAE375 | Emirates | 3 | 2026-05-12 |
| UAE358 | Emirates | 3 | 2026-05-27 |
| UAE333 | Emirates | 3 | 2026-05-23 |
| UAE2578 | - | 3 | 2026-04-13 |
| UAE9988 | Emirates | 2 | 2026-04-30 |
| UAE9987 | Emirates | 2 | 2026-04-29 |
| UAE9315 | Emirates | 2 | 2026-04-21 |
| UAE359 | Emirates | 2 | 2026-05-27 |
| UAE357 | Emirates | 2 | 2026-05-16 |
| UAE2663 | - | 2 | 2026-04-24 |
| UAE2662 | - | 2 | 2026-04-24 |
| UAE2579 | - | 2 | 2026-04-13 |
| UAE1N | Emirates | 2 | 2026-05-25 |
| UAE9JQ | Emirates | 1 | 2026-05-08 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | UAE13U | FRA → DXB | May 29, 20:45 UTC | May 30, 08:35 UTC | 11h 50m |
| 2026-05-28 | UAE331 | - | May 28, 22:20 UTC | May 29, 17:30 UTC | 19h 10m |
| 2026-05-28 | UAE331 | - | May 28, 21:50 UTC | May 29, 17:30 UTC | 19h 40m |
| 2026-05-28 | UAE331 | - | May 28, 19:40 UTC | May 29, 17:30 UTC | 21h 50m |
| 2026-05-27 | UAE330 | - | May 27, 22:20 UTC | May 28, 17:15 UTC | 18h 55m |
| 2026-05-27 | UAE330 | - | May 27, 21:50 UTC | May 28, 17:15 UTC | 19h 25m |
| 2026-05-27 | UAE359 | CGK → DXB | May 27, 17:40 UTC | May 27, 18:05 UTC | 25m |
| 2026-05-27 | UAE358 | DXB → CGK | May 27, 09:05 UTC | May 27, 14:50 UTC | 5h 45m |
| 2026-05-26 | UAE49K | BLR → DXB | May 26, 05:10 UTC | May 26, 06:20 UTC | 1h 10m |
| 2026-05-25 | UAE1N | DXB → BLR | May 25, 15:40 UTC | May 26, 03:05 UTC | 11h 24m |
| 2026-05-24 | UAE566 | DXB → BLR | May 24, 18:30 UTC | May 25, 13:25 UTC | 18h 55m |
| 2026-05-24 | UAE359 | CGK → DXB | May 24, 17:45 UTC | May 24, 17:55 UTC | 10m |
| 2026-05-24 | UAE358 | DXB → CGK | May 24, 09:20 UTC | May 24, 14:30 UTC | 5h 10m |
| 2026-05-23 | UAE358 | DXB → CGK | May 23, 17:15 UTC | May 24, 14:30 UTC | 21h 15m |
| 2026-05-23 | UAE333 | MNL → DXB | May 23, 14:20 UTC | May 24, 14:15 UTC | 23h 55m |
| 2026-05-23 | UAE333 | MNL → DXB | May 23, 13:30 UTC | May 24, 10:45 UTC | 21h 15m |
| 2026-05-23 | UAE333 | MNL → DXB | May 23, 11:30 UTC | May 24, 09:40 UTC | 22h 10m |
| 2026-05-22 | UAE332 | DXB → MNL | May 22, 14:30 UTC | May 23, 09:00 UTC | 18h 29m |
| 2026-05-21 | UAE76J | DXB → BUD | May 21, 18:25 UTC | May 22, 11:40 UTC | 17h 15m |
| 2026-05-21 | UAE797 | DXB → DKR | May 21, 16:10 UTC | May 21, 16:30 UTC | 20m |
| 2026-05-20 | UAE4DT | STN → DXB | May 20, 14:20 UTC | May 21, 05:10 UTC | 14h 50m |
| 2026-05-19 | UAE9J | DXB → STN | May 19, 18:05 UTC | May 20, 12:10 UTC | 18h 6m |
| 2026-05-18 | UAE348 | DXB → SIN | May 18, 11:10 UTC | May 19, 05:55 UTC | 18h 44m |
| 2026-05-17 | UAE2728 | - | May 17, 13:31 UTC | May 18, 11:40 UTC | 22h 10m |
| 2026-05-16 | UAE357 | CGK → DXB | May 16, 14:25 UTC | May 17, 13:35 UTC | 23h 10m |
| 2026-05-16 | UAE357 | CGK → DXB | May 16, 10:40 UTC | May 16, 10:55 UTC | 15m |
| 2026-05-16 | UAE356 | DXB → CGK | May 16, 02:30 UTC | May 16, 08:11 UTC | 5h 41m |
| 2026-05-14 | UAE331 | - | May 14, 19:40 UTC | May 15, 02:30 UTC | 6h 50m |
| 2026-05-13 | UAE330 | - | May 13, 22:20 UTC | May 14, 16:50 UTC | 18h 30m |
| 2026-05-13 | UAE330 | MUC → MNL | May 13, 20:45 UTC | May 14, 16:50 UTC | 20h 5m |
| 2026-05-13 | UAE1DM | DXB → MUC | May 13, 05:10 UTC | May 13, 17:55 UTC | 12h 45m |
| 2026-05-13 | UAE1N | DXB → BLR | May 13, 02:35 UTC | May 13, 03:05 UTC | 30m |
| 2026-05-12 | UAE375 | BKK → DXB | May 12, 06:35 UTC | May 13, 03:05 UTC | 20h 30m |
| 2026-05-12 | UAE375 | BKK → DXB | May 12, 04:50 UTC | May 13, 03:05 UTC | 22h 15m |
| 2026-05-12 | UAE375 | BKK → DXB | May 12, 02:45 UTC | May 12, 07:10 UTC | 4h 25m |
| 2026-05-11 | UAE374 | DXB → BKK | May 11, 20:20 UTC | May 11, 22:35 UTC | 2h 14m |
| 2026-05-09 | UAE5W | AMM → DXB | May 9, 13:30 UTC | May 9, 13:40 UTC | 10m |
| 2026-05-08 | UAE78P | DUB → DXB | May 8, 21:25 UTC | May 9, 09:05 UTC | 11h 40m |
| 2026-05-08 | UAE9JQ | DXB → DUB | May 8, 05:05 UTC | May 8, 19:05 UTC | 14h 0m |
| 2026-05-08 | UAE544 | DXB → MAA | May 8, 01:40 UTC | May 8, 02:09 UTC | 30m |
| 2026-05-05 | UAE9443 | - | May 5, 00:55 UTC | May 5, 01:20 UTC | 25m |
| 2026-05-04 | UAE9442 | - | May 4, 20:20 UTC | May 4, 20:50 UTC | 30m |
| 2026-04-30 | UAE9988 | ORD → DWC | Apr 30, 10:25 UTC | Apr 30, 16:55 UTC | 6h 30m |
| 2026-04-29 | UAE9988 | ORD → DWC | Apr 29, 23:35 UTC | Apr 30, 08:40 UTC | 9h 5m |
| 2026-04-29 | UAE9987 | AMS → ORD | Apr 29, 10:30 UTC | Apr 29, 20:50 UTC | 10h 20m |
| 2026-04-29 | UAE9987 | AMS → ORD | Apr 29, 00:59 UTC | Apr 29, 08:40 UTC | 7h 40m |
| 2026-04-27 | UAE9434 | - | Apr 27, 13:50 UTC | Apr 27, 14:55 UTC | 1h 5m |
| 2026-04-27 | UAE9433 | - | Apr 27, 10:35 UTC | Apr 27, 11:30 UTC | 55m |
| 2026-04-27 | UAE305 | PVG → DXB | Apr 27, 08:15 UTC | Apr 27, 08:40 UTC | 25m |
| 2026-04-26 | UAE304 | DXB → PVG | Apr 26, 14:10 UTC | Apr 27, 04:55 UTC | 14h 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 A6-ECJ page for operator, model, and routing details .