sensors Mode-S transponder
89617E
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-EGF · BOEING 777-300ER
- Hex
- 89617E
- Octal
- 42260576
- Decimal
- 9,003,390
- Country
- AE
- Tail
- A6-EGF
- Type
- B77W
- Flights observed
- 151
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 2h ago
Last known position
Country allocation
The ICAO 24-bit address 89617E 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 |
|---|---|---|---|
| UAE247 | - | 17 | 2026-07-04 |
| UAE248 | Emirates | 15 | 2026-07-05 |
| UAE333 | Emirates | 9 | 2026-07-06 |
| UAE332 | - | 9 | 2026-07-06 |
| UAE3MX | - | 7 | 2026-07-13 |
| UAE232 | Emirates | 7 | 2026-07-02 |
| UAE359 | - | 6 | 2026-07-10 |
| UAE1DM | Emirates | 5 | 2026-05-29 |
| UAE9U | Emirates | 4 | 2026-04-28 |
| UAE72 | Emirates | 4 | 2026-04-15 |
| UAE71 | Emirates | 4 | 2026-04-15 |
| UAE349 | Emirates | 4 | 2026-05-26 |
| UAE583 | Emirates | 3 | 2026-04-28 |
| UAE508 | Emirates | 3 | 2026-04-28 |
| UAE35Q | Emirates | 3 | 2026-05-29 |
| UAE358 | - | 3 | 2026-07-10 |
| UAE7Y | Emirates | 2 | 2026-04-28 |
| UAE566 | Emirates | 2 | 2026-05-02 |
| UAE507 | Emirates | 2 | 2026-05-24 |
| UAE49K | Emirates | 2 | 2026-04-29 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | UAE3MX | - | Jul 13, 23:05 UTC | Jul 14, 12:25 UTC | 13h 20m |
| 2026-07-13 | UAE112 | - | Jul 13, 14:15 UTC | Jul 13, 19:15 UTC | 5h 0m |
| 2026-07-13 | UAE76J | - | Jul 13, 06:20 UTC | Jul 13, 11:45 UTC | 5h 25m |
| 2026-07-12 | UAE922 | - | Jul 12, 15:01 UTC | Jul 12, 15:20 UTC | 20m |
| 2026-07-12 | UAE921 | - | Jul 12, 08:40 UTC | Jul 12, 11:25 UTC | 2h 45m |
| 2026-07-12 | UAE24E | - | Jul 12, 00:40 UTC | Jul 12, 01:05 UTC | 25m |
| 2026-07-11 | UAE793 | - | Jul 11, 06:05 UTC | Jul 11, 12:55 UTC | 6h 50m |
| 2026-07-10 | UAE359 | - | Jul 10, 22:15 UTC | Jul 11, 01:20 UTC | 3h 5m |
| 2026-07-10 | UAE359 | - | Jul 10, 18:10 UTC | Jul 10, 18:25 UTC | 15m |
| 2026-07-10 | UAE358 | - | Jul 10, 09:05 UTC | Jul 10, 14:20 UTC | 5h 15m |
| 2026-07-09 | UAE331 | - | Jul 9, 19:20 UTC | Jul 10, 01:50 UTC | 6h 30m |
| 2026-07-09 | UAE330 | - | Jul 9, 08:50 UTC | Jul 9, 17:10 UTC | 8h 20m |
| 2026-07-06 | UAE333 | MNL → DXB | Jul 6, 11:20 UTC | Jul 6, 19:20 UTC | 8h 0m |
| 2026-07-06 | UAE332 | - | Jul 6, 00:05 UTC | Jul 6, 08:45 UTC | 8h 40m |
| 2026-07-05 | UAE248 | GIG → DXB | Jul 5, 06:25 UTC | Jul 5, 20:00 UTC | 13h 35m |
| 2026-07-05 | UAE248 | GIG → DXB | Jul 5, 01:55 UTC | Jul 5, 04:05 UTC | 2h 10m |
| 2026-07-04 | UAE247 | - | Jul 4, 20:35 UTC | Jul 4, 23:50 UTC | 3h 15m |
| 2026-07-04 | UAE247 | - | Jul 4, 04:30 UTC | Jul 4, 18:25 UTC | 13h 55m |
| 2026-07-03 | UAE784 | - | Jul 3, 06:50 UTC | Jul 4, 00:20 UTC | 17h 30m |
| 2026-07-02 | UAE232 | IAD → DXB | Jul 2, 15:05 UTC | Jul 3, 03:20 UTC | 12h 15m |
| 2026-07-02 | UAE3MX | DXB → IAD | Jul 2, 10:10 UTC | Jul 2, 12:10 UTC | 2h 0m |
| 2026-07-01 | UAE3MX | DXB → IAD | Jul 1, 22:25 UTC | Jul 2, 10:05 UTC | 11h 40m |
| 2026-07-01 | UAE333 | MNL → DXB | Jul 1, 18:00 UTC | Jul 1, 18:20 UTC | 20m |
| 2026-07-01 | UAE333 | MNL → DXB | Jul 1, 10:30 UTC | Jul 1, 17:00 UTC | 6h 30m |
| 2026-06-30 | UAE332 | - | Jun 30, 23:50 UTC | Jul 1, 08:25 UTC | 8h 35m |
| 2026-06-30 | UAE248 | GIG → DXB | Jun 30, 06:20 UTC | Jun 30, 20:05 UTC | 13h 45m |
| 2026-06-30 | UAE248 | GIG → DXB | Jun 30, 01:40 UTC | Jun 30, 04:05 UTC | 2h 25m |
| 2026-06-29 | UAE247 | - | Jun 29, 20:35 UTC | Jun 29, 23:29 UTC | 2h 55m |
| 2026-06-29 | UAE247 | - | Jun 29, 04:30 UTC | Jun 29, 18:44 UTC | 14h 15m |
| 2026-06-28 | UAE6RM | IST → DXB | Jun 28, 17:00 UTC | Jun 28, 20:50 UTC | 3h 50m |
| 2026-06-28 | UAE121 | - | Jun 28, 10:10 UTC | Jun 28, 14:14 UTC | 4h 5m |
| 2026-06-26 | UAE2611 | - | Jun 26, 21:15 UTC | Jun 27, 04:00 UTC | 6h 45m |
| 2026-05-31 | UAE2610 | - | May 31, 21:55 UTC | Jun 1, 13:50 UTC | 15h 55m |
| 2026-05-31 | UAE359 | CGK → DXB | May 31, 17:45 UTC | May 31, 18:00 UTC | 15m |
| 2026-05-30 | UAE331 | - | May 30, 20:25 UTC | May 31, 14:10 UTC | 17h 45m |
| 2026-05-29 | UAE330 | - | May 29, 21:35 UTC | May 30, 17:30 UTC | 19h 55m |
| 2026-05-29 | UAE35Q | MUC → DXB | May 29, 20:55 UTC | May 30, 17:30 UTC | 20h 35m |
| 2026-05-29 | UAE1DM | DXB → MUC | May 29, 15:15 UTC | May 29, 18:25 UTC | 3h 11m |
| 2026-05-28 | UAE1DM | DXB → MUC | May 28, 19:35 UTC | May 29, 18:25 UTC | 22h 50m |
| 2026-05-28 | UAE1DM | DXB → MUC | May 28, 19:25 UTC | May 29, 17:30 UTC | 22h 5m |
| 2026-05-28 | UAE248 | GIG → DXB | May 28, 06:50 UTC | May 28, 19:45 UTC | 12h 55m |
| 2026-05-28 | UAE248 | GIG → DXB | May 28, 02:20 UTC | May 28, 04:45 UTC | 2h 25m |
| 2026-05-27 | UAE247 | GIG → EZE | May 27, 21:50 UTC | May 28, 00:40 UTC | 2h 50m |
| 2026-05-26 | UAE247 | GIG → EZE | May 26, 21:40 UTC | May 27, 19:30 UTC | 21h 50m |
| 2026-05-26 | UAE349 | SIN → DXB | May 26, 18:14 UTC | May 27, 05:35 UTC | 11h 20m |
| 2026-05-25 | UAE333 | MNL → DXB | May 25, 12:50 UTC | May 26, 05:59 UTC | 17h 9m |
| 2026-05-25 | UAE333 | MNL → DXB | May 25, 10:45 UTC | May 26, 05:59 UTC | 19h 14m |
| 2026-05-25 | UAE332 | DXB → MNL | May 25, 02:00 UTC | May 25, 08:45 UTC | 6h 45m |
| 2026-05-24 | UAE822 | DMM → DXB | May 24, 20:00 UTC | May 24, 20:55 UTC | 55m |
| 2026-05-24 | UAE507 | BOM → DXB | May 24, 10:50 UTC | May 24, 11:20 UTC | 30m |
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-EGF page for operator, model, and routing details .