sensors Mode-S transponder
896211
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-EGP · BOEING 777-300ER
- Hex
- 896211
- Octal
- 42261021
- Decimal
- 9,003,537
- Country
- AE
- Tail
- A6-EGP
- Type
- B77W
- Flights observed
- 95
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 9h ago
Last known position
Country allocation
The ICAO 24-bit address 896211 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 |
|---|---|---|---|
| UAE13U | Emirates | 6 | 2026-05-27 |
| UAE95 | Emirates | 5 | 2026-05-25 |
| UAE96 | Emirates | 4 | 2026-05-25 |
| UAE89V | Emirates | 4 | 2026-05-24 |
| UAE545 | Emirates | 4 | 2026-05-02 |
| UAE544 | Emirates | 4 | 2026-05-01 |
| UAE516 | Emirates | 4 | 2026-05-19 |
| UAE514 | Emirates | 4 | 2026-04-17 |
| UAE29V | Emirates | 4 | 2026-05-27 |
| UAE6U | Emirates | 3 | 2026-04-17 |
| UAE517 | Emirates | 3 | 2026-05-20 |
| UAE510 | Emirates | 3 | 2026-04-18 |
| UAE9398 | - | 2 | 2026-04-28 |
| UAE9397 | - | 2 | 2026-04-28 |
| UAE584 | Emirates | 2 | 2026-05-02 |
| UAE57X | Emirates | 2 | 2026-05-26 |
| UAE546 | Emirates | 2 | 2026-05-08 |
| UAE512 | Emirates | 2 | 2026-04-15 |
| UAE4Q | Emirates | 2 | 2026-04-18 |
| UAE21W | Emirates | 2 | 2026-04-16 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-28 | UAE20 | MAN → DXB | May 28, 21:10 UTC | May 29, 15:25 UTC | 18h 15m |
| 2026-05-27 | UAE19 | DXB → MAN | May 27, 22:20 UTC | May 28, 17:40 UTC | 19h 20m |
| 2026-05-27 | UAE13U | FRA → DXB | May 27, 20:30 UTC | May 28, 17:40 UTC | 21h 10m |
| 2026-05-27 | UAE29V | DXB → FRA | May 27, 04:39 UTC | May 27, 17:40 UTC | 13h 1m |
| 2026-05-26 | UAE57X | HAM → DXB | May 26, 13:50 UTC | May 27, 02:14 UTC | 12h 25m |
| 2026-05-25 | UAE96 | FCO → DXB | May 25, 20:19 UTC | May 26, 11:34 UTC | 15h 15m |
| 2026-05-25 | UAE95 | DXB → FCO | May 25, 06:15 UTC | May 25, 17:40 UTC | 11h 25m |
| 2026-05-24 | UAE89V | CCU → DXB | May 24, 16:45 UTC | May 25, 16:15 UTC | 23h 30m |
| 2026-05-24 | UAE922 | CAI → DXB | May 24, 14:50 UTC | May 25, 07:10 UTC | 16h 20m |
| 2026-05-23 | UAE921 | DXB → CAI | May 23, 23:30 UTC | May 24, 11:45 UTC | 12h 15m |
| 2026-05-21 | UAE1J | LHR → DXB | May 21, 19:20 UTC | May 22, 01:45 UTC | 6h 25m |
| 2026-05-21 | UAE4PY | DXB → LHR | May 21, 13:15 UTC | May 21, 15:00 UTC | 1h 45m |
| 2026-05-20 | UAE1P | TRV → DXB | May 20, 23:20 UTC | May 20, 23:30 UTC | 10m |
| 2026-05-20 | UAE517 | DEL → DXB | May 20, 11:30 UTC | May 20, 21:10 UTC | 9h 40m |
| 2026-05-19 | UAE516 | DXB → DEL | May 19, 23:20 UTC | May 20, 08:50 UTC | 9h 31m |
| 2026-05-19 | UAE6Q | DXB → TRV | May 19, 11:20 UTC | May 19, 21:15 UTC | 9h 55m |
| 2026-05-19 | UAE516 | DXB → DEL | May 19, 08:15 UTC | May 19, 08:55 UTC | 40m |
| 2026-05-16 | UAE96 | FCO → DXB | May 16, 20:25 UTC | May 17, 00:45 UTC | 4h 20m |
| 2026-05-16 | UAE95 | DXB → FCO | May 16, 14:51 UTC | May 16, 18:10 UTC | 3h 20m |
| 2026-05-15 | UAE706 | SEZ → DXB | May 15, 08:10 UTC | May 15, 08:40 UTC | 30m |
| 2026-05-14 | UAE5W | AMM → DXB | May 14, 13:30 UTC | May 14, 15:40 UTC | 2h 10m |
| 2026-05-09 | UAE96 | FCO → DXB | May 9, 20:20 UTC | May 9, 22:05 UTC | 1h 45m |
| 2026-05-09 | UAE95 | DXB → FCO | May 9, 11:40 UTC | May 9, 17:15 UTC | 5h 35m |
| 2026-05-08 | UAE95 | DXB → FCO | May 8, 17:00 UTC | May 9, 16:15 UTC | 23h 15m |
| 2026-05-08 | UAE546 | DXB → MAA | May 8, 13:55 UTC | May 8, 14:20 UTC | 25m |
| 2026-05-06 | UAE5T | MUC → DXB | May 6, 14:00 UTC | May 6, 19:35 UTC | 5h 34m |
| 2026-05-05 | UAE9CL | DXB → MUC | May 5, 16:55 UTC | May 6, 11:45 UTC | 18h 50m |
| 2026-05-05 | UAE546 | DXB → MAA | May 5, 14:20 UTC | May 5, 14:40 UTC | 20m |
| 2026-05-05 | UAE527 | HYD → DXB | May 5, 08:40 UTC | May 5, 09:05 UTC | 25m |
| 2026-05-05 | UAE526 | DXB → HYD | May 5, 02:25 UTC | May 5, 02:55 UTC | 30m |
| 2026-05-04 | UAE71K | PRG → DXB | May 4, 14:15 UTC | May 4, 20:45 UTC | 6h 31m |
| 2026-05-04 | UAE42X | DXB → PRG | May 4, 03:35 UTC | May 4, 10:20 UTC | 6h 45m |
| 2026-05-03 | UAE57X | HAM → DXB | May 3, 16:45 UTC | May 3, 23:15 UTC | 6h 30m |
| 2026-05-02 | UAE59 | DXB → HAM | May 2, 19:50 UTC | May 3, 11:15 UTC | 15h 24m |
| 2026-05-02 | UAE584 | DXB → DAC | May 2, 15:10 UTC | May 2, 16:55 UTC | 1h 45m |
| 2026-05-02 | UAE584 | DXB → DAC | May 2, 13:00 UTC | May 2, 13:25 UTC | 25m |
| 2026-05-02 | UAE545 | MAA → DXB | May 2, 01:05 UTC | May 2, 08:00 UTC | 6h 55m |
| 2026-05-01 | UAE544 | DXB → MAA | May 1, 23:10 UTC | May 1, 23:30 UTC | 20m |
| 2026-05-01 | UAE2502 | ORD → DXB | May 1, 17:20 UTC | May 1, 17:35 UTC | 15m |
| 2026-05-01 | UAE305 | PVG → DXB | May 1, 08:40 UTC | May 1, 09:00 UTC | 20m |
| 2026-04-30 | UAE304 | DXB → PVG | Apr 30, 14:05 UTC | May 1, 05:25 UTC | 15h 20m |
| 2026-04-28 | UAE9398 | - | Apr 28, 14:10 UTC | Apr 28, 20:15 UTC | 6h 5m |
| 2026-04-28 | UAE9397 | - | Apr 28, 02:10 UTC | Apr 28, 09:45 UTC | 7h 35m |
| 2026-04-25 | UAE9652 | - | Apr 25, 02:20 UTC | Apr 25, 22:15 UTC | 19h 55m |
| 2026-04-25 | UAE9927 | MAD → DWC | Apr 25, 02:00 UTC | Apr 25, 22:15 UTC | 20h 15m |
| 2026-04-23 | UAE9974 | FRA → DXB | Apr 23, 15:15 UTC | Apr 23, 21:35 UTC | 6h 20m |
| 2026-04-23 | UAE9973 | DXB → FRA | Apr 23, 01:25 UTC | Apr 23, 09:05 UTC | 7h 40m |
| 2026-04-21 | UAE9398 | FRA → DWC | Apr 21, 14:35 UTC | Apr 21, 20:30 UTC | 5h 55m |
| 2026-04-21 | UAE9397 | - | Apr 21, 02:10 UTC | Apr 21, 09:55 UTC | 7h 45m |
| 2026-04-20 | UAE2501 | DXB → MAN | Apr 20, 14:00 UTC | Apr 20, 14:20 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-EGP page for operator, model, and routing details .