sensors Mode-S transponder
896112
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-ECK · BOEING 777-300ER
- Hex
- 896112
- Octal
- 42260422
- Decimal
- 9,003,282
- Country
- AE
- Tail
- A6-ECK
- Type
- B77W
- Flights observed
- 85
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 5h ago
Last known position
Country allocation
The ICAO 24-bit address 896112 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 |
|---|---|---|---|
| UAE1DM | Emirates | 10 | 2026-06-06 |
| UAE35Q | Emirates | 5 | 2026-06-07 |
| UAE332 | Emirates | 5 | 2026-05-17 |
| UAE3MV | Emirates | 4 | 2026-05-11 |
| UAE333 | Emirates | 4 | 2026-05-18 |
| UAE566 | Emirates | 3 | 2026-06-09 |
| UAE349 | Emirates | 3 | 2026-06-13 |
| UAE18V | - | 3 | 2026-06-18 |
| UAE9Q | - | 2 | 2026-06-17 |
| UAE8M | - | 2 | 2026-06-17 |
| UAE79Y | Emirates | 2 | 2026-06-05 |
| UAE797 | Emirates | 2 | 2026-05-19 |
| UAE584 | - | 2 | 2026-06-19 |
| UAE507 | - | 2 | 2026-06-18 |
| UAE395 | Emirates | 2 | 2026-05-14 |
| UAE348 | Emirates | 2 | 2026-06-13 |
| UAE314 | Emirates | 2 | 2026-06-18 |
| UAE112 | Emirates | 2 | 2026-06-01 |
| UAE98X | - | 1 | 2026-06-22 |
| UAE8349 | Emirates | 1 | 2026-06-16 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-24 | UAE16M | - | Jun 24, 10:55 UTC | Jun 25, 03:50 UTC | 16h 55m |
| 2026-06-24 | UAE49K | - | Jun 24, 05:24 UTC | Jun 24, 08:30 UTC | 3h 5m |
| 2026-06-23 | UAE1N | - | Jun 23, 23:55 UTC | Jun 24, 03:10 UTC | 3h 15m |
| 2026-06-22 | UAE180 | - | Jun 22, 13:35 UTC | Jun 22, 19:05 UTC | 5h 30m |
| 2026-06-22 | UAE98X | - | Jun 22, 04:19 UTC | Jun 22, 10:00 UTC | 5h 40m |
| 2026-06-22 | UAE24E | - | Jun 22, 00:50 UTC | Jun 22, 01:25 UTC | 35m |
| 2026-06-21 | UAE793 | DXB → LAD | Jun 21, 06:04 UTC | Jun 21, 13:00 UTC | 6h 55m |
| 2026-06-19 | UAE3PX | - | Jun 19, 20:19 UTC | Jun 19, 23:04 UTC | 2h 45m |
| 2026-06-19 | UAE584 | - | Jun 19, 16:49 UTC | Jun 19, 17:39 UTC | 50m |
| 2026-06-19 | UAE584 | - | Jun 19, 13:29 UTC | Jun 19, 13:54 UTC | 25m |
| 2026-06-19 | UAE315 | SIN → DXB | Jun 19, 02:59 UTC | Jun 19, 07:45 UTC | 4h 45m |
| 2026-06-18 | UAE314 | DXB → SIN | Jun 18, 19:15 UTC | Jun 19, 00:34 UTC | 5h 19m |
| 2026-06-18 | UAE314 | DXB → SIN | Jun 18, 17:25 UTC | Jun 18, 17:45 UTC | 20m |
| 2026-06-18 | UAE507 | - | Jun 18, 11:55 UTC | Jun 18, 12:20 UTC | 25m |
| 2026-06-18 | UAE18V | - | Jun 18, 08:00 UTC | Jun 18, 09:00 UTC | 1h 0m |
| 2026-06-18 | UAE18V | - | Jun 18, 06:15 UTC | Jun 18, 06:40 UTC | 25m |
| 2026-06-17 | UAE9Q | - | Jun 17, 23:45 UTC | Jun 18, 00:05 UTC | 20m |
| 2026-06-17 | UAE8M | - | Jun 17, 21:15 UTC | Jun 17, 21:25 UTC | 10m |
| 2026-06-17 | UAE8M | - | Jun 17, 18:00 UTC | Jun 17, 18:20 UTC | 20m |
| 2026-06-16 | UAE8349 | SIN → DXB | Jun 16, 18:35 UTC | Jun 16, 23:10 UTC | 4h 36m |
| 2026-06-15 | UAE136 | - | Jun 15, 14:05 UTC | Jun 16, 06:20 UTC | 16h 15m |
| 2026-06-14 | UAE135 | - | Jun 14, 17:05 UTC | Jun 15, 11:24 UTC | 18h 19m |
| 2026-06-13 | UAE121 | - | Jun 13, 22:25 UTC | Jun 14, 14:55 UTC | 16h 30m |
| 2026-06-13 | UAE349 | SIN → DXB | Jun 13, 18:35 UTC | Jun 14, 14:55 UTC | 20h 21m |
| 2026-06-13 | UAE349 | SIN → DXB | Jun 13, 18:05 UTC | Jun 14, 14:55 UTC | 20h 51m |
| 2026-06-13 | UAE348 | DXB → SIN | Jun 13, 08:10 UTC | Jun 13, 15:15 UTC | 7h 5m |
| 2026-06-12 | UAE46 | FRA → DXB | Jun 12, 13:35 UTC | Jun 13, 05:50 UTC | 16h 14m |
| 2026-06-11 | UAE52M | DXB → FRA | Jun 11, 18:05 UTC | Jun 12, 10:50 UTC | 16h 46m |
| 2026-06-11 | UAE349 | SIN → DXB | Jun 11, 08:00 UTC | Jun 11, 15:35 UTC | 7h 35m |
| 2026-06-10 | UAE348 | DXB → SIN | Jun 10, 16:00 UTC | Jun 11, 05:35 UTC | 13h 35m |
| 2026-06-09 | UAE566 | DXB → BLR | Jun 9, 18:35 UTC | Jun 10, 13:40 UTC | 19h 5m |
| 2026-06-09 | UAE566 | DXB → BLR | Jun 9, 18:25 UTC | Jun 10, 13:40 UTC | 19h 15m |
| 2026-06-08 | UAE359 | CGK → DXB | Jun 8, 17:55 UTC | Jun 8, 23:15 UTC | 5h 20m |
| 2026-06-07 | UAE35Q | MUC → DXB | Jun 7, 21:25 UTC | Jun 8, 15:10 UTC | 17h 45m |
| 2026-06-06 | UAE1DM | DXB → MUC | Jun 6, 22:34 UTC | Jun 7, 18:15 UTC | 19h 40m |
| 2026-06-06 | UAE1DM | DXB → MUC | Jun 6, 20:55 UTC | Jun 7, 18:15 UTC | 21h 20m |
| 2026-06-06 | UAE1DM | DXB → MUC | Jun 6, 14:45 UTC | Jun 6, 18:19 UTC | 3h 35m |
| 2026-06-05 | UAE1DM | DXB → MUC | Jun 5, 21:50 UTC | Jun 6, 18:19 UTC | 20h 30m |
| 2026-06-05 | UAE1DM | DXB → MUC | Jun 5, 18:35 UTC | Jun 6, 18:19 UTC | 23h 45m |
| 2026-06-05 | UAE79Y | LHR → DXB | Jun 5, 16:35 UTC | Jun 6, 16:30 UTC | 23h 55m |
| 2026-06-05 | UAE79Y | LHR → DXB | Jun 5, 16:15 UTC | Jun 5, 22:30 UTC | 6h 15m |
| 2026-06-05 | UAE62T | DXB → LHR | Jun 5, 10:05 UTC | Jun 5, 13:30 UTC | 3h 25m |
| 2026-06-03 | UAE331 | - | Jun 3, 20:05 UTC | Jun 4, 07:40 UTC | 11h 35m |
| 2026-06-02 | UAE330 | - | Jun 2, 22:35 UTC | Jun 3, 17:10 UTC | 18h 35m |
| 2026-06-02 | UAE35Q | MUC → DXB | Jun 2, 20:50 UTC | Jun 3, 17:10 UTC | 20h 20m |
| 2026-06-02 | UAE1DM | DXB → MUC | Jun 2, 05:10 UTC | Jun 2, 18:30 UTC | 13h 20m |
| 2026-06-01 | UAE112 | BUD → DXB | Jun 1, 14:20 UTC | Jun 2, 03:10 UTC | 12h 50m |
| 2026-05-31 | UAE76J | DXB → BUD | May 31, 21:30 UTC | Jun 1, 11:30 UTC | 14h 0m |
| 2026-05-30 | UAE35Q | MUC → DXB | May 30, 22:35 UTC | May 31, 21:30 UTC | 22h 55m |
| 2026-05-30 | UAE35Q | MUC → DXB | May 30, 20:55 UTC | May 30, 23:50 UTC | 2h 55m |
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-ECK page for operator, model, and routing details .