sensors Mode-S transponder
89620A
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-EGI · BOEING 777-300ER
- Hex
- 89620A
- Octal
- 42261012
- Decimal
- 9,003,530
- Country
- AE
- Tail
- A6-EGI
- Type
- B77W
- Flights observed
- 112
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 5h ago
Current position
Country allocation
The ICAO 24-bit address 89620A 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 |
|---|---|---|---|
| UAE3MX | Emirates | 12 | 2026-05-30 |
| UAE358 | Emirates | 11 | 2026-05-26 |
| UAE232 | Emirates | 8 | 2026-05-30 |
| UAE359 | Emirates | 6 | 2026-05-26 |
| UAE330 | - | 5 | 2026-05-26 |
| UAE57X | Emirates | 4 | 2026-04-14 |
| UAE331 | - | 4 | 2026-05-27 |
| UAE1N | Emirates | 4 | 2026-05-18 |
| UAE19 | Emirates | 4 | 2026-05-07 |
| UAE67V | Emirates | 3 | 2026-04-17 |
| UAE59 | - | 3 | 2026-04-13 |
| UAE54J | Emirates | 3 | 2026-04-17 |
| UAE507 | Emirates | 3 | 2026-05-23 |
| UAE378 | Emirates | 3 | 2026-05-13 |
| UAE9Q | Emirates | 2 | 2026-04-16 |
| UAE8M | Emirates | 2 | 2026-04-15 |
| UAE788 | Emirates | 2 | 2026-04-18 |
| UAE66V | Emirates | 2 | 2026-05-06 |
| UAE508 | Emirates | 2 | 2026-05-18 |
| UAE371 | Emirates | 2 | 2026-05-16 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | UAE232 | IAD → DXB | May 30, 15:25 UTC | May 30, 16:15 UTC | 50m |
| 2026-05-30 | UAE3MX | DXB → IAD | May 30, 02:15 UTC | May 30, 12:50 UTC | 10h 35m |
| 2026-05-29 | UAE3MX | DXB → IAD | May 29, 17:30 UTC | May 30, 12:50 UTC | 19h 20m |
| 2026-05-29 | UAE3MX | DXB → IAD | May 29, 14:35 UTC | May 30, 12:50 UTC | 22h 15m |
| 2026-05-29 | UAE3MX | DXB → IAD | May 29, 13:55 UTC | May 30, 12:30 UTC | 22h 35m |
| 2026-05-29 | UAE3MX | DXB → IAD | May 29, 11:30 UTC | May 30, 06:50 UTC | 19h 20m |
| 2026-05-29 | UAE332 | DXB → MNL | May 29, 02:20 UTC | May 29, 09:15 UTC | 6h 55m |
| 2026-05-27 | UAE331 | - | May 27, 19:45 UTC | May 28, 02:30 UTC | 6h 45m |
| 2026-05-26 | UAE330 | - | May 26, 22:44 UTC | May 27, 17:25 UTC | 18h 40m |
| 2026-05-26 | UAE330 | - | May 26, 21:20 UTC | May 27, 17:25 UTC | 20h 5m |
| 2026-05-26 | UAE330 | - | May 26, 18:19 UTC | May 27, 13:10 UTC | 18h 51m |
| 2026-05-26 | UAE359 | CGK → DXB | May 26, 17:30 UTC | May 26, 17:44 UTC | 15m |
| 2026-05-26 | UAE358 | DXB → CGK | May 26, 14:55 UTC | May 26, 15:05 UTC | 10m |
| 2026-05-26 | UAE358 | DXB → CGK | May 26, 09:09 UTC | May 26, 14:20 UTC | 5h 10m |
| 2026-05-23 | UAE507 | BOM → DXB | May 23, 13:00 UTC | May 23, 13:20 UTC | 20m |
| 2026-05-23 | UAE507 | BOM → DXB | May 23, 11:00 UTC | May 23, 11:20 UTC | 20m |
| 2026-05-23 | UAE18V | DXB → BOM | May 23, 06:15 UTC | May 23, 09:00 UTC | 2h 45m |
| 2026-05-21 | UAE331 | - | May 21, 19:35 UTC | May 22, 02:15 UTC | 6h 40m |
| 2026-05-20 | UAE330 | - | May 20, 22:35 UTC | May 21, 17:00 UTC | 18h 25m |
| 2026-05-20 | UAE232 | IAD → DXB | May 20, 20:50 UTC | May 21, 17:00 UTC | 20h 10m |
| 2026-05-20 | UAE232 | IAD → DXB | May 20, 16:35 UTC | May 21, 16:30 UTC | 23h 55m |
| 2026-05-20 | UAE232 | IAD → DXB | May 20, 15:10 UTC | May 21, 13:15 UTC | 22h 5m |
| 2026-05-20 | UAE3MX | DXB → IAD | May 20, 10:35 UTC | May 20, 12:35 UTC | 2h 0m |
| 2026-05-19 | UAE3MX | DXB → IAD | May 19, 23:15 UTC | May 20, 10:30 UTC | 11h 16m |
| 2026-05-19 | UAE3MX | DXB → IAD | May 19, 06:35 UTC | May 20, 05:45 UTC | 23h 11m |
| 2026-05-19 | UAE3MX | DXB → IAD | May 19, 05:15 UTC | May 20, 04:30 UTC | 23h 15m |
| 2026-05-18 | UAE1N | DXB → BLR | May 18, 17:25 UTC | May 19, 03:05 UTC | 9h 39m |
| 2026-05-18 | UAE508 | DXB → BOM | May 18, 14:10 UTC | May 18, 15:05 UTC | 55m |
| 2026-05-17 | UAE507 | BOM → DXB | May 17, 11:01 UTC | May 17, 11:35 UTC | 35m |
| 2026-05-16 | UAE371 | BKK → DXB | May 16, 20:20 UTC | May 17, 08:40 UTC | 12h 20m |
| 2026-05-16 | UAE371 | BKK → DXB | May 16, 17:10 UTC | May 16, 17:40 UTC | 30m |
| 2026-05-16 | UAE370 | DXB → BKK | May 16, 13:21 UTC | May 16, 13:41 UTC | 20m |
| 2026-05-15 | UAE1J | LHR → DXB | May 15, 19:10 UTC | May 16, 10:55 UTC | 15h 46m |
| 2026-05-14 | UAE4PY | DXB → LHR | May 14, 20:50 UTC | May 15, 14:35 UTC | 17h 45m |
| 2026-05-14 | UAE232 | IAD → DXB | May 14, 16:35 UTC | May 15, 14:35 UTC | 22h 0m |
| 2026-05-14 | UAE232 | IAD → DXB | May 14, 15:15 UTC | May 15, 14:30 UTC | 23h 15m |
| 2026-05-14 | UAE3MX | DXB → IAD | May 14, 01:50 UTC | May 14, 12:45 UTC | 10h 55m |
| 2026-05-13 | UAE378 | DXB → HKT | May 13, 02:35 UTC | May 14, 02:30 UTC | 23h 55m |
| 2026-05-13 | UAE378 | DXB → HKT | May 13, 00:25 UTC | May 13, 02:55 UTC | 2h 30m |
| 2026-05-12 | UAE378 | DXB → HKT | May 12, 05:20 UTC | May 13, 02:55 UTC | 21h 35m |
| 2026-05-12 | UAE1N | DXB → BLR | May 12, 02:45 UTC | May 12, 03:10 UTC | 25m |
| 2026-05-11 | UAE158 | ARN → DXB | May 11, 13:50 UTC | May 11, 20:45 UTC | 6h 56m |
| 2026-05-10 | UAE4T | DXB → ARN | May 10, 17:34 UTC | May 11, 11:25 UTC | 17h 50m |
| 2026-05-09 | UAE331 | - | May 9, 21:30 UTC | May 10, 15:15 UTC | 17h 45m |
| 2026-05-09 | UAE331 | - | May 9, 19:30 UTC | May 10, 15:15 UTC | 19h 45m |
| 2026-05-08 | UAE330 | - | May 8, 22:35 UTC | May 9, 16:40 UTC | 18h 5m |
| 2026-05-08 | UAE20 | MAN → DXB | May 8, 20:35 UTC | May 9, 16:40 UTC | 20h 5m |
| 2026-05-08 | UAE20 | MAN → DXB | May 8, 20:25 UTC | May 9, 16:40 UTC | 20h 15m |
| 2026-05-07 | UAE19 | DXB → MAN | May 7, 22:35 UTC | May 8, 17:35 UTC | 19h 0m |
| 2026-05-07 | UAE19 | DXB → MAN | May 7, 21:45 UTC | May 8, 17:35 UTC | 19h 50m |
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-EGI page for operator, model, and routing details .