sensors Mode-S transponder
89617B
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-EGC · BOEING 777-300ER
- Hex
- 89617B
- Octal
- 42260573
- Decimal
- 9,003,387
- Country
- AE
- Tail
- A6-EGC
- Type
- B77W
- Flights observed
- 173
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 3h ago
Last known position
Country allocation
The ICAO 24-bit address 89617B 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 |
|---|---|---|---|
| UAE358 | Emirates | 10 | 2026-06-16 |
| UAE583 | - | 7 | 2026-07-13 |
| UAE3MX | Emirates | 7 | 2026-06-13 |
| UAE359 | - | 7 | 2026-06-16 |
| UAE333 | Emirates | 7 | 2026-05-14 |
| UAE332 | Emirates | 7 | 2026-05-08 |
| UAE508 | Emirates | 6 | 2026-05-08 |
| UAE348 | Emirates | 6 | 2026-06-18 |
| UAE9U | - | 5 | 2026-07-12 |
| UAE357 | Emirates | 5 | 2026-05-31 |
| UAE9Q | Emirates | 4 | 2026-04-27 |
| UAE8M | Emirates | 4 | 2026-04-27 |
| UAE7Y | Emirates | 4 | 2026-05-01 |
| UAE795 | Emirates | 4 | 2026-05-29 |
| UAE531 | Emirates | 4 | 2026-05-11 |
| UAE530 | Emirates | 4 | 2026-06-09 |
| UAE507 | - | 4 | 2026-06-17 |
| UAE232 | Emirates | 4 | 2026-06-14 |
| UAE784 | - | 3 | 2026-06-16 |
| UAE566 | Emirates | 3 | 2026-06-04 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | UAE793 | - | Jul 14, 06:25 UTC | Jul 14, 06:55 UTC | 30m |
| 2026-07-13 | UAE150 | - | Jul 13, 20:20 UTC | Jul 14, 02:35 UTC | 6h 15m |
| 2026-07-13 | UAE149 | - | Jul 13, 11:00 UTC | Jul 13, 18:05 UTC | 7h 5m |
| 2026-07-13 | UAE583 | - | Jul 13, 08:55 UTC | Jul 13, 09:15 UTC | 20m |
| 2026-07-13 | UAE583 | - | Jul 13, 05:10 UTC | Jul 13, 07:55 UTC | 2h 45m |
| 2026-07-12 | UAE9U | - | Jul 12, 22:35 UTC | Jul 13, 02:55 UTC | 4h 20m |
| 2026-07-12 | UAE790 | - | Jul 12, 00:05 UTC | Jul 12, 18:25 UTC | 18h 20m |
| 2026-07-10 | UAE180 | WAW → DXB | Jul 10, 13:25 UTC | Jul 10, 18:45 UTC | 5h 20m |
| 2026-07-10 | UAE98X | - | Jul 10, 04:25 UTC | Jul 10, 09:45 UTC | 5h 20m |
| 2026-07-09 | UAE96 | - | Jul 9, 20:35 UTC | Jul 10, 01:40 UTC | 5h 5m |
| 2026-07-09 | UAE95 | - | Jul 9, 12:15 UTC | Jul 9, 18:00 UTC | 5h 45m |
| 2026-07-08 | UAE331 | - | Jul 8, 19:30 UTC | Jul 9, 03:15 UTC | 7h 45m |
| 2026-07-08 | UAE330 | - | Jul 8, 08:40 UTC | Jul 8, 17:05 UTC | 8h 25m |
| 2026-07-07 | UAE4N | - | Jul 7, 23:55 UTC | Jul 8, 00:35 UTC | 40m |
| 2026-07-07 | UAE721 | - | Jul 7, 12:25 UTC | Jul 7, 13:00 UTC | 35m |
| 2026-07-07 | UAE8Y | - | Jul 7, 08:30 UTC | Jul 7, 08:40 UTC | 10m |
| 2026-07-07 | UAE8Y | - | Jul 7, 02:35 UTC | Jul 7, 06:55 UTC | 4h 20m |
| 2026-07-06 | UAE65T | - | Jul 6, 19:40 UTC | Jul 7, 00:30 UTC | 4h 50m |
| 2026-07-06 | UAE65T | - | Jul 6, 17:50 UTC | Jul 6, 18:15 UTC | 25m |
| 2026-06-20 | UAE2551 | DWC → DXB | Jun 20, 15:09 UTC | Jun 20, 15:24 UTC | 15m |
| 2026-06-19 | UAE806 | - | Jun 19, 03:29 UTC | Jun 19, 10:29 UTC | 7h 0m |
| 2026-06-18 | UAE349 | SIN → DXB | Jun 18, 17:55 UTC | Jun 18, 22:40 UTC | 4h 45m |
| 2026-06-18 | UAE348 | DXB → SIN | Jun 18, 08:10 UTC | Jun 18, 15:10 UTC | 7h 0m |
| 2026-06-18 | UAE348 | DXB → SIN | Jun 18, 00:50 UTC | Jun 18, 06:05 UTC | 5h 15m |
| 2026-06-17 | UAE507 | - | Jun 17, 10:50 UTC | Jun 17, 11:15 UTC | 25m |
| 2026-06-16 | UAE359 | - | Jun 16, 18:09 UTC | Jun 17, 08:30 UTC | 14h 21m |
| 2026-06-16 | UAE358 | DXB → CGK | Jun 16, 09:04 UTC | Jun 16, 15:15 UTC | 6h 10m |
| 2026-06-16 | UAE358 | DXB → CGK | Jun 16, 07:15 UTC | Jun 16, 07:40 UTC | 25m |
| 2026-06-16 | UAE784 | - | Jun 16, 01:10 UTC | Jun 16, 01:35 UTC | 25m |
| 2026-06-14 | UAE232 | IAD → DXB | Jun 14, 15:15 UTC | Jun 15, 03:45 UTC | 12h 29m |
| 2026-06-13 | UAE3MX | DXB → IAD | Jun 13, 16:50 UTC | Jun 14, 12:40 UTC | 19h 50m |
| 2026-06-13 | UAE3MX | DXB → IAD | Jun 13, 14:50 UTC | Jun 14, 12:40 UTC | 21h 50m |
| 2026-06-13 | UAE3MX | DXB → IAD | Jun 13, 14:05 UTC | Jun 14, 12:40 UTC | 22h 35m |
| 2026-06-13 | UAE135 | DXB → VCE | Jun 13, 07:10 UTC | Jun 13, 10:40 UTC | 3h 30m |
| 2026-06-12 | UAE359 | CGK → DXB | Jun 12, 18:20 UTC | Jun 13, 01:35 UTC | 7h 15m |
| 2026-06-12 | UAE358 | DXB → CGK | Jun 12, 15:00 UTC | Jun 12, 15:15 UTC | 15m |
| 2026-06-12 | UAE358 | DXB → CGK | Jun 12, 02:15 UTC | Jun 12, 14:25 UTC | 12h 10m |
| 2026-06-11 | UAE358 | DXB → CGK | Jun 11, 18:15 UTC | Jun 12, 14:25 UTC | 20h 11m |
| 2026-06-11 | UAE797 | DXB → DKR | Jun 11, 05:05 UTC | Jun 11, 16:20 UTC | 11h 15m |
| 2026-06-10 | UAE375 | BKK → DXB | Jun 10, 03:05 UTC | Jun 10, 07:25 UTC | 4h 20m |
| 2026-06-09 | UAE374 | DXB → BKK | Jun 9, 05:25 UTC | Jun 10, 00:35 UTC | 19h 10m |
| 2026-06-09 | UAE530 | DXB → COK | Jun 9, 03:15 UTC | Jun 9, 03:25 UTC | 10m |
| 2026-06-08 | UAE158 | ARN → DXB | Jun 8, 13:50 UTC | Jun 8, 20:35 UTC | 6h 45m |
| 2026-06-08 | UAE4T | DXB → ARN | Jun 8, 11:25 UTC | Jun 8, 11:45 UTC | 20m |
| 2026-06-07 | UAE1CL | LGW → DXB | Jun 7, 14:50 UTC | Jun 8, 10:15 UTC | 19h 25m |
| 2026-06-07 | UAE1CL | LGW → DXB | Jun 7, 14:05 UTC | Jun 8, 10:15 UTC | 20h 10m |
| 2026-06-06 | UAE72V | DXB → LGW | Jun 6, 23:19 UTC | Jun 7, 11:40 UTC | 12h 20m |
| 2026-06-06 | UAE784 | LOS → DXB | Jun 6, 07:00 UTC | Jun 7, 06:40 UTC | 23h 40m |
| 2026-06-04 | UAE31T | BLR → DXB | Jun 4, 15:45 UTC | Jun 4, 17:00 UTC | 1h 15m |
| 2026-06-04 | UAE566 | DXB → BLR | Jun 4, 12:05 UTC | Jun 4, 13:30 UTC | 1h 25m |
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-EGC page for operator, model, and routing details .