sensors Mode-S transponder
896210
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-EGO · BOEING 777-300ER
- Hex
- 896210
- Octal
- 42261020
- Decimal
- 9,003,536
- Country
- AE
- Tail
- A6-EGO
- Type
- B77W
- Flights observed
- 87
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 12h ago
Last known position
Country allocation
The ICAO 24-bit address 896210 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 |
|---|---|---|---|
| UAE4PY | Emirates | 6 | 2026-05-27 |
| UAE9937 | Emirates | 5 | 2026-04-17 |
| UAE526 | Emirates | 5 | 2026-05-21 |
| UAE121 | Emirates | 4 | 2026-05-27 |
| UAE2V | Emirates | 3 | 2026-05-08 |
| UAE1J | Emirates | 3 | 2026-05-28 |
| UAE180 | Emirates | 3 | 2026-06-01 |
| UAE9818 | - | 2 | 2026-04-18 |
| UAE89V | Emirates | 2 | 2026-05-08 |
| UAE6U | Emirates | 2 | 2026-05-09 |
| UAE528 | Emirates | 2 | 2026-05-26 |
| UAE527 | Emirates | 2 | 2026-05-21 |
| UAE514 | Emirates | 2 | 2026-05-09 |
| UAE31T | Emirates | 2 | 2026-05-07 |
| UAE316 | Emirates | 2 | 2026-04-28 |
| UAE309 | Emirates | 2 | 2026-04-26 |
| UAE308 | Emirates | 2 | 2026-04-25 |
| UAE305 | Emirates | 2 | 2026-04-20 |
| UAE29V | Emirates | 2 | 2026-05-03 |
| UAE2593 | - | 2 | 2026-04-19 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | UAE6J | CPT → DXB | Jun 2, 11:15 UTC | Jun 2, 12:55 UTC | 1h 40m |
| 2026-06-01 | UAE180 | WAW → DXB | Jun 1, 14:05 UTC | Jun 2, 09:15 UTC | 19h 10m |
| 2026-06-01 | UAE180 | WAW → DXB | Jun 1, 13:45 UTC | Jun 2, 09:15 UTC | 19h 30m |
| 2026-05-31 | UAE112 | BUD → DXB | May 31, 15:20 UTC | Jun 1, 09:35 UTC | 18h 15m |
| 2026-05-31 | UAE76J | DXB → BUD | May 31, 10:20 UTC | May 31, 12:15 UTC | 1h 55m |
| 2026-05-28 | UAE1J | LHR → DXB | May 28, 19:05 UTC | May 29, 01:25 UTC | 6h 20m |
| 2026-05-27 | UAE4PY | DXB → LHR | May 27, 20:05 UTC | May 28, 14:50 UTC | 18h 45m |
| 2026-05-27 | UAE4PY | DXB → LHR | May 27, 18:05 UTC | May 28, 14:50 UTC | 20h 45m |
| 2026-05-27 | UAE4PY | DXB → LHR | May 27, 16:50 UTC | May 28, 14:50 UTC | 22h 0m |
| 2026-05-27 | UAE121 | DXB → IST | May 27, 13:25 UTC | May 27, 14:15 UTC | 50m |
| 2026-05-26 | UAE121 | DXB → IST | May 26, 18:05 UTC | May 27, 14:15 UTC | 20h 10m |
| 2026-05-26 | UAE529 | HYD → DXB | May 26, 17:30 UTC | May 27, 14:00 UTC | 20h 30m |
| 2026-05-26 | UAE528 | DXB → HYD | May 26, 06:29 UTC | May 26, 18:24 UTC | 11h 55m |
| 2026-05-25 | UAE528 | DXB → HYD | May 25, 12:55 UTC | May 26, 04:24 UTC | 15h 29m |
| 2026-05-21 | UAE21W | DEL → DXB | May 21, 23:10 UTC | May 21, 23:40 UTC | 30m |
| 2026-05-21 | UAE527 | HYD → DXB | May 21, 05:20 UTC | May 21, 20:40 UTC | 15h 20m |
| 2026-05-21 | UAE526 | DXB → HYD | May 21, 00:55 UTC | May 21, 20:40 UTC | 19h 45m |
| 2026-05-20 | UAE547 | MAA → DXB | May 20, 16:45 UTC | May 21, 06:00 UTC | 13h 15m |
| 2026-05-20 | UAE526 | DXB → HYD | May 20, 00:55 UTC | May 20, 14:10 UTC | 13h 16m |
| 2026-05-19 | UAE526 | DXB → HYD | May 19, 06:05 UTC | May 20, 05:50 UTC | 23h 46m |
| 2026-05-19 | UAE526 | DXB → HYD | May 19, 05:50 UTC | May 20, 01:40 UTC | 19h 50m |
| 2026-05-19 | UAE526 | DXB → HYD | May 19, 02:05 UTC | May 20, 01:40 UTC | 23h 35m |
| 2026-05-18 | UAE180 | WAW → DXB | May 18, 13:20 UTC | May 19, 06:20 UTC | 16h 59m |
| 2026-05-17 | UAE98X | DXB → WAW | May 17, 16:55 UTC | May 18, 10:00 UTC | 17h 5m |
| 2026-05-17 | UAE121 | DXB → IST | May 17, 14:40 UTC | May 17, 14:50 UTC | 10m |
| 2026-05-17 | UAE121 | DXB → IST | May 17, 13:15 UTC | May 17, 14:05 UTC | 50m |
| 2026-05-14 | UAE74W | LGW → DXB | May 14, 09:15 UTC | May 14, 13:30 UTC | 4h 15m |
| 2026-05-14 | UAE9W | DXB → LGW | May 14, 01:05 UTC | May 14, 05:50 UTC | 4h 45m |
| 2026-05-13 | UAE1J | LHR → DXB | May 13, 01:25 UTC | May 13, 01:45 UTC | 20m |
| 2026-05-12 | UAE1J | LHR → DXB | May 12, 19:00 UTC | May 12, 23:01 UTC | 4h 0m |
| 2026-05-12 | UAE4PY | DXB → LHR | May 12, 03:15 UTC | May 12, 14:55 UTC | 11h 40m |
| 2026-05-11 | UAE4PY | DXB → LHR | May 11, 16:05 UTC | May 12, 14:55 UTC | 22h 51m |
| 2026-05-11 | UAE4PY | DXB → LHR | May 11, 15:50 UTC | May 12, 14:00 UTC | 22h 11m |
| 2026-05-11 | UAE566 | DXB → BLR | May 11, 12:50 UTC | May 11, 13:20 UTC | 30m |
| 2026-05-09 | UAE6U | DEL → DXB | May 9, 19:35 UTC | May 9, 19:45 UTC | 10m |
| 2026-05-09 | UAE6U | DEL → DXB | May 9, 16:50 UTC | May 9, 17:25 UTC | 35m |
| 2026-05-09 | UAE514 | DXB → DEL | May 9, 13:45 UTC | May 9, 14:25 UTC | 40m |
| 2026-05-09 | UAE514 | DXB → DEL | May 9, 11:40 UTC | May 9, 12:00 UTC | 20m |
| 2026-05-08 | UAE89V | CCU → DXB | May 8, 04:54 UTC | May 8, 18:00 UTC | 13h 6m |
| 2026-05-08 | UAE2V | DXB → CCU | May 8, 01:29 UTC | May 8, 02:19 UTC | 50m |
| 2026-05-07 | UAE31T | BLR → DXB | May 7, 18:55 UTC | May 7, 19:20 UTC | 25m |
| 2026-05-07 | UAE31T | BLR → DXB | May 7, 15:50 UTC | May 7, 16:15 UTC | 25m |
| 2026-05-06 | UAE21W | DEL → DXB | May 6, 23:00 UTC | May 7, 13:35 UTC | 14h 35m |
| 2026-05-06 | UAE512 | DXB → DEL | May 6, 19:40 UTC | May 6, 20:25 UTC | 45m |
| 2026-05-05 | UAE158 | ARN → DXB | May 5, 14:10 UTC | May 5, 18:20 UTC | 4h 10m |
| 2026-05-05 | UAE4T | DXB → ARN | May 5, 11:30 UTC | May 5, 12:00 UTC | 30m |
| 2026-05-04 | UAE725 | DXB → DAR | May 4, 05:50 UTC | May 4, 06:15 UTC | 25m |
| 2026-05-03 | UAE13U | FRA → DXB | May 3, 20:25 UTC | May 4, 02:45 UTC | 6h 20m |
| 2026-05-03 | UAE29V | DXB → FRA | May 3, 10:30 UTC | May 3, 17:29 UTC | 7h 0m |
| 2026-05-03 | UAE527 | HYD → DXB | May 3, 00:10 UTC | May 3, 08:10 UTC | 7h 59m |
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-EGO page for operator, model, and routing details .