sensors Mode-S transponder
896114
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-ECM · BOEING 777-300ER
- Hex
- 896114
- Octal
- 42260424
- Decimal
- 9,003,284
- Country
- AE
- Tail
- A6-ECM
- Type
- B77W
- Flights observed
- 85
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 13h ago
Last known position
Country allocation
The ICAO 24-bit address 896114 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 |
|---|---|---|---|
| UAE8M | Emirates | 6 | 2026-05-10 |
| UAE9Q | Emirates | 4 | 2026-05-10 |
| UAE507 | Emirates | 4 | 2026-05-01 |
| UAE333 | Emirates | 4 | 2026-05-05 |
| UAE18V | Emirates | 4 | 2026-05-01 |
| UAE9828 | Emirates | 3 | 2026-05-24 |
| UAE332 | Emirates | 3 | 2026-05-05 |
| UAE2568 | Emirates | 3 | 2026-05-29 |
| UAE9U | Emirates | 2 | 2026-04-29 |
| UAE9989 | Emirates | 2 | 2026-05-21 |
| UAE96 | Emirates | 2 | 2026-05-07 |
| UAE795 | Emirates | 2 | 2026-04-19 |
| UAE784 | Emirates | 2 | 2026-04-21 |
| UAE583 | Emirates | 2 | 2026-04-29 |
| UAE51P | Emirates | 2 | 2026-04-23 |
| UAE4P | Emirates | 2 | 2026-04-26 |
| UAE49K | - | 2 | 2026-04-13 |
| UAE330 | - | 2 | 2026-04-25 |
| UAE2567 | - | 2 | 2026-05-29 |
| UAE9Y | Emirates | 1 | 2026-04-24 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | UAE2568 | GRU → DXB | May 29, 22:55 UTC | May 30, 00:00 UTC | 1h 5m |
| 2026-05-29 | UAE2567 | - | May 29, 17:50 UTC | May 29, 19:25 UTC | 1h 35m |
| 2026-05-25 | UAE9829 | BOM → DWC | May 25, 17:30 UTC | May 25, 21:49 UTC | 4h 19m |
| 2026-05-24 | UAE9828 | DWC → BOM | May 24, 21:05 UTC | May 25, 15:25 UTC | 18h 20m |
| 2026-05-24 | UAE9828 | DWC → BOM | May 24, 19:05 UTC | May 25, 15:25 UTC | 20h 20m |
| 2026-05-24 | UAE9828 | DWC → BOM | May 24, 18:35 UTC | May 25, 15:25 UTC | 20h 50m |
| 2026-05-22 | UAE7GV | AMS → DWC | May 22, 10:05 UTC | May 23, 01:25 UTC | 15h 20m |
| 2026-05-21 | UAE9989 | LCK → ORD | May 21, 13:05 UTC | May 22, 07:25 UTC | 18h 20m |
| 2026-05-21 | UAE9989 | LCK → ORD | May 21, 12:40 UTC | May 22, 07:25 UTC | 18h 45m |
| 2026-05-18 | UAE2585 | - | May 18, 16:25 UTC | May 18, 21:05 UTC | 4h 39m |
| 2026-05-18 | UAE2584 | - | May 18, 10:35 UTC | May 18, 14:10 UTC | 3h 35m |
| 2026-05-16 | UAE2595 | - | May 16, 18:45 UTC | May 17, 07:45 UTC | 13h 0m |
| 2026-05-16 | UAE2594 | DWC → DWC | May 16, 17:25 UTC | May 16, 17:45 UTC | 20m |
| 2026-05-14 | UAE9224 | - | May 14, 12:00 UTC | May 14, 12:30 UTC | 30m |
| 2026-05-13 | UAE2568 | GRU → DXB | May 13, 12:05 UTC | May 14, 09:40 UTC | 21h 35m |
| 2026-05-12 | UAE2568 | GRU → DXB | May 12, 23:05 UTC | May 13, 12:30 UTC | 13h 25m |
| 2026-05-12 | UAE2567 | - | May 12, 18:00 UTC | May 12, 19:40 UTC | 1h 40m |
| 2026-05-10 | UAE9Q | COK → DXB | May 10, 23:19 UTC | May 10, 23:44 UTC | 25m |
| 2026-05-10 | UAE8M | DXB → COK | May 10, 20:45 UTC | May 10, 21:25 UTC | 40m |
| 2026-05-09 | UAE112 | BUD → DXB | May 9, 14:20 UTC | May 9, 19:14 UTC | 4h 55m |
| 2026-05-08 | UAE76J | DXB → BUD | May 8, 23:20 UTC | May 9, 11:00 UTC | 11h 40m |
| 2026-05-08 | UAE8M | DXB → COK | May 8, 20:45 UTC | May 8, 21:15 UTC | 30m |
| 2026-05-07 | UAE8M | DXB → COK | May 7, 23:09 UTC | May 8, 21:15 UTC | 22h 5m |
| 2026-05-07 | UAE96 | FCO → DXB | May 7, 21:05 UTC | May 8, 20:55 UTC | 23h 50m |
| 2026-05-07 | UAE96 | FCO → DXB | May 7, 20:50 UTC | May 7, 23:14 UTC | 2h 25m |
| 2026-05-07 | UAE95 | DXB → FCO | May 7, 05:35 UTC | May 7, 18:35 UTC | 13h 0m |
| 2026-05-06 | UAE6AQ | MAN → DXB | May 6, 09:25 UTC | May 7, 03:10 UTC | 17h 44m |
| 2026-05-06 | UAE1KM | DXB → MAN | May 6, 01:10 UTC | May 6, 06:20 UTC | 5h 10m |
| 2026-05-05 | UAE333 | MNL → DXB | May 5, 19:15 UTC | May 5, 19:35 UTC | 20m |
| 2026-05-05 | UAE333 | MNL → DXB | May 5, 11:05 UTC | May 5, 16:06 UTC | 5h 0m |
| 2026-05-05 | UAE332 | DXB → MNL | May 5, 02:30 UTC | May 5, 08:45 UTC | 6h 15m |
| 2026-05-04 | UAE1CL | LGW → DXB | May 4, 14:10 UTC | May 4, 21:35 UTC | 7h 26m |
| 2026-05-04 | UAE72V | DXB → LGW | May 4, 03:24 UTC | May 4, 11:25 UTC | 8h 0m |
| 2026-05-03 | UAE1GQ | SKT → DXB | May 3, 19:25 UTC | May 4, 00:50 UTC | 5h 25m |
| 2026-05-03 | UAE75V | DXB → SKT | May 3, 17:29 UTC | May 3, 17:54 UTC | 25m |
| 2026-05-01 | UAE507 | BOM → DXB | May 1, 11:00 UTC | May 1, 11:15 UTC | 15m |
| 2026-05-01 | UAE18V | DXB → BOM | May 1, 05:50 UTC | May 1, 08:40 UTC | 2h 50m |
| 2026-04-30 | UAE2Y | KHI → DXB | Apr 30, 23:15 UTC | Apr 30, 23:40 UTC | 25m |
| 2026-04-30 | UAE606 | DXB → KHI | Apr 30, 17:55 UTC | Apr 30, 18:20 UTC | 25m |
| 2026-04-30 | UAE507 | BOM → DXB | Apr 30, 11:15 UTC | Apr 30, 13:40 UTC | 2h 25m |
| 2026-04-30 | UAE18V | DXB → BOM | Apr 30, 05:55 UTC | Apr 30, 08:25 UTC | 2h 30m |
| 2026-04-29 | UAE56F | CMB → DXB | Apr 29, 22:00 UTC | Apr 30, 01:45 UTC | 3h 44m |
| 2026-04-29 | UAE648 | DXB → CMB | Apr 29, 12:30 UTC | Apr 29, 15:55 UTC | 3h 25m |
| 2026-04-29 | UAE583 | DAC → DXB | Apr 29, 08:50 UTC | Apr 29, 09:10 UTC | 21m |
| 2026-04-29 | UAE583 | DAC → DXB | Apr 29, 04:39 UTC | Apr 29, 05:30 UTC | 50m |
| 2026-04-29 | UAE9U | DXB → DAC | Apr 29, 01:25 UTC | Apr 29, 02:55 UTC | 1h 30m |
| 2026-04-28 | UAE9U | DXB → DAC | Apr 28, 22:20 UTC | Apr 28, 22:40 UTC | 20m |
| 2026-04-28 | UAE31T | BLR → DXB | Apr 28, 15:40 UTC | Apr 28, 19:10 UTC | 3h 30m |
| 2026-04-28 | UAE566 | DXB → BLR | Apr 28, 10:05 UTC | Apr 28, 13:15 UTC | 3h 10m |
| 2026-04-27 | UAE333 | MNL → DXB | Apr 27, 18:45 UTC | Apr 27, 19:05 UTC | 20m |
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-ECM page for operator, model, and routing details .