sensors Mode-S transponder
89620D
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-EGL · BOEING 777-300ER
- Hex
- 89620D
- Octal
- 42261015
- Decimal
- 9,003,533
- Country
- AE
- Tail
- A6-EGL
- Type
- B77W
- Flights observed
- 63
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 7h ago
Current position
Country allocation
The ICAO 24-bit address 89620D 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 |
|---|---|---|---|
| UAE71 | Emirates | 7 | 2026-04-22 |
| UAE9232 | Emirates | 3 | 2026-05-21 |
| UAE316 | Emirates | 3 | 2026-04-15 |
| UAE2585 | - | 3 | 2026-05-25 |
| UAE2567 | - | 3 | 2026-04-16 |
| UAE2549 | - | 3 | 2026-04-13 |
| UAE9904 | - | 2 | 2026-05-20 |
| UAE9648 | - | 2 | 2026-04-24 |
| UAE9328 | - | 2 | 2026-04-13 |
| UAE72 | Emirates | 2 | 2026-04-23 |
| UAE512 | Emirates | 2 | 2026-04-19 |
| UAE317 | Emirates | 2 | 2026-04-16 |
| UAE308 | Emirates | 2 | 2026-04-27 |
| UAE2584 | - | 2 | 2026-05-25 |
| UAE2568 | Emirates | 2 | 2026-04-17 |
| UAE21W | Emirates | 2 | 2026-04-20 |
| UAE9989 | Emirates | 1 | 2026-05-08 |
| UAE9937 | Emirates | 1 | 2026-04-21 |
| UAE9719 | - | 1 | 2026-05-23 |
| UAE9652 | - | 1 | 2026-04-21 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | UAE2593 | - | May 29, 09:30 UTC | May 29, 21:25 UTC | 11h 55m |
| 2026-05-25 | UAE2585 | - | May 25, 16:30 UTC | May 25, 20:55 UTC | 4h 24m |
| 2026-05-25 | UAE2584 | - | May 25, 09:15 UTC | May 25, 14:10 UTC | 4h 55m |
| 2026-05-23 | UAE9719 | - | May 23, 08:35 UTC | May 23, 08:55 UTC | 20m |
| 2026-05-21 | UAE9232 | ORD → DWC | May 21, 03:35 UTC | May 21, 21:15 UTC | 17h 40m |
| 2026-05-20 | UAE9232 | ORD → DWC | May 20, 23:25 UTC | May 21, 21:15 UTC | 21h 50m |
| 2026-05-20 | UAE9232 | ORD → DWC | May 20, 22:05 UTC | May 21, 21:15 UTC | 23h 10m |
| 2026-05-20 | UAE9904 | - | May 20, 10:25 UTC | May 20, 19:00 UTC | 8h 35m |
| 2026-05-20 | UAE9904 | - | May 20, 04:15 UTC | May 20, 08:25 UTC | 4h 11m |
| 2026-05-18 | UAE9396 | ORD → DWC | May 18, 17:25 UTC | May 18, 19:05 UTC | 1h 39m |
| 2026-05-18 | UAE9395 | DWC → ZAZ | May 18, 11:15 UTC | May 18, 15:30 UTC | 4h 15m |
| 2026-05-15 | UAE528 | DXB → HYD | May 15, 12:55 UTC | May 15, 18:00 UTC | 5h 4m |
| 2026-05-10 | UAE2594 | - | May 10, 09:24 UTC | May 10, 20:40 UTC | 11h 15m |
| 2026-05-08 | UAE7GV | AMS → DWC | May 8, 10:14 UTC | May 8, 16:15 UTC | 6h 0m |
| 2026-05-08 | UAE9989 | LCK → ORD | May 8, 02:44 UTC | May 8, 07:29 UTC | 4h 45m |
| 2026-05-03 | UAE305 | PVG → DXB | May 3, 08:55 UTC | May 3, 09:20 UTC | 25m |
| 2026-05-02 | UAE304 | DXB → PVG | May 2, 14:20 UTC | May 3, 05:35 UTC | 15h 14m |
| 2026-04-30 | UAE2585 | - | Apr 30, 22:15 UTC | Apr 30, 22:35 UTC | 20m |
| 2026-04-30 | UAE2585 | - | Apr 30, 16:00 UTC | Apr 30, 20:30 UTC | 4h 30m |
| 2026-04-30 | UAE2584 | - | Apr 30, 07:30 UTC | Apr 30, 13:55 UTC | 6h 25m |
| 2026-04-29 | UAE9392 | AMS → DXB | Apr 29, 18:00 UTC | Apr 30, 00:10 UTC | 6h 9m |
| 2026-04-29 | UAE9391 | DWC → DWC | Apr 29, 08:15 UTC | Apr 29, 15:45 UTC | 7h 31m |
| 2026-04-28 | UAE9436 | - | Apr 28, 13:05 UTC | Apr 28, 13:55 UTC | 50m |
| 2026-04-28 | UAE9435 | CPH → DXB | Apr 28, 10:30 UTC | Apr 28, 11:20 UTC | 50m |
| 2026-04-28 | UAE309 | PEK → DXB | Apr 28, 07:50 UTC | Apr 28, 08:10 UTC | 20m |
| 2026-04-27 | UAE308 | DXB → PEK | Apr 27, 21:05 UTC | Apr 27, 21:20 UTC | 15m |
| 2026-04-27 | UAE308 | DXB → PEK | Apr 27, 14:10 UTC | Apr 27, 14:30 UTC | 20m |
| 2026-04-26 | UAE2667 | - | Apr 26, 09:25 UTC | Apr 26, 16:20 UTC | 6h 55m |
| 2026-04-25 | UAE9314 | - | Apr 25, 23:55 UTC | Apr 26, 07:10 UTC | 7h 15m |
| 2026-04-24 | UAE9648 | - | Apr 24, 16:50 UTC | Apr 24, 17:10 UTC | 20m |
| 2026-04-24 | UAE9648 | - | Apr 24, 02:00 UTC | Apr 24, 02:25 UTC | 25m |
| 2026-04-23 | UAE72 | CDG → DXB | Apr 23, 11:01 UTC | Apr 23, 17:15 UTC | 6h 15m |
| 2026-04-22 | UAE71 | DXB → CDG | Apr 22, 23:45 UTC | Apr 23, 07:45 UTC | 8h 0m |
| 2026-04-21 | UAE9652 | - | Apr 21, 16:40 UTC | Apr 22, 01:05 UTC | 8h 25m |
| 2026-04-21 | UAE9937 | DXB → MIA | Apr 21, 04:15 UTC | Apr 21, 14:45 UTC | 10h 30m |
| 2026-04-20 | UAE2503 | DXB → LHR | Apr 20, 21:00 UTC | Apr 20, 21:10 UTC | 10m |
| 2026-04-20 | UAE21W | DEL → DXB | Apr 20, 01:55 UTC | Apr 20, 02:15 UTC | 20m |
| 2026-04-19 | UAE21W | DEL → DXB | Apr 19, 23:25 UTC | Apr 20, 00:00 UTC | 35m |
| 2026-04-19 | UAE512 | DXB → DEL | Apr 19, 20:40 UTC | Apr 19, 21:15 UTC | 35m |
| 2026-04-19 | UAE512 | DXB → DEL | Apr 19, 18:25 UTC | Apr 19, 18:45 UTC | 20m |
| 2026-04-19 | UAE2504 | LGW → DXB | Apr 19, 11:10 UTC | Apr 19, 11:30 UTC | 20m |
| 2026-04-18 | UAE72 | CDG → DXB | Apr 18, 11:10 UTC | Apr 18, 17:45 UTC | 6h 35m |
| 2026-04-18 | UAE71 | DXB → CDG | Apr 18, 07:25 UTC | Apr 18, 08:55 UTC | 1h 30m |
| 2026-04-18 | UAE71 | DXB → CDG | Apr 18, 06:30 UTC | Apr 18, 07:20 UTC | 50m |
| 2026-04-18 | UAE71 | DXB → CDG | Apr 18, 03:25 UTC | Apr 18, 04:25 UTC | 1h 0m |
| 2026-04-18 | UAE71 | DXB → CDG | Apr 18, 01:25 UTC | Apr 18, 03:20 UTC | 1h 55m |
| 2026-04-17 | UAE71 | DXB → CDG | Apr 17, 23:40 UTC | Apr 18, 00:45 UTC | 1h 5m |
| 2026-04-17 | UAE71 | DXB → CDG | Apr 17, 20:00 UTC | Apr 17, 21:00 UTC | 1h 0m |
| 2026-04-17 | UAE2568 | GRU → DXB | Apr 17, 11:50 UTC | Apr 17, 12:45 UTC | 55m |
| 2026-04-16 | UAE2568 | GRU → DXB | Apr 16, 23:30 UTC | Apr 17, 00:30 UTC | 1h 0m |
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-EGL page for operator, model, and routing details .