sensors Mode-S transponder
89611F
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-ECX · BOEING 777-300ER
- Hex
- 89611F
- Octal
- 42260437
- Decimal
- 9,003,295
- Country
- AE
- Tail
- A6-ECX
- Type
- B77W
- Flights observed
- 94
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 3h ago
Current position
Country allocation
The ICAO 24-bit address 89611F 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 |
|---|---|---|---|
| UAE232 | Emirates | 10 | 2026-05-10 |
| UAE248 | Emirates | 9 | 2026-05-17 |
| UAE247 | Emirates | 9 | 2026-05-16 |
| UAE3MX | Emirates | 8 | 2026-05-09 |
| UAE348 | Emirates | 7 | 2026-05-30 |
| UAE331 | - | 4 | 2026-05-23 |
| UAE176 | Emirates | 4 | 2026-05-25 |
| UAE349 | Emirates | 3 | 2026-05-28 |
| UAE1KM | Emirates | 3 | 2026-05-08 |
| UAE788 | Emirates | 2 | 2026-04-23 |
| UAE566 | Emirates | 2 | 2026-05-12 |
| UAE367 | Emirates | 2 | 2026-04-19 |
| UAE366 | Emirates | 2 | 2026-04-19 |
| UAE359 | Emirates | 2 | 2026-05-19 |
| UAE333 | Emirates | 2 | 2026-05-04 |
| UAE332 | Emirates | 2 | 2026-05-04 |
| UAE330 | - | 2 | 2026-05-23 |
| UAE31T | Emirates | 2 | 2026-04-18 |
| UAE9Y | Emirates | 1 | 2026-04-18 |
| UAE9W | Emirates | 1 | 2026-05-07 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | UAE348 | DXB → SIN | May 30, 00:30 UTC | May 30, 01:55 UTC | 1h 25m |
| 2026-05-28 | UAE349 | SIN → DXB | May 28, 18:05 UTC | May 28, 22:50 UTC | 4h 45m |
| 2026-05-28 | UAE348 | DXB → SIN | May 28, 00:45 UTC | May 28, 06:00 UTC | 5h 15m |
| 2026-05-25 | UAE176 | LED → DXB | May 25, 12:20 UTC | May 26, 02:29 UTC | 14h 9m |
| 2026-05-25 | UAE176 | LED → DXB | May 25, 02:00 UTC | May 25, 23:00 UTC | 20h 59m |
| 2026-05-24 | UAE176 | LED → DXB | May 24, 15:55 UTC | May 25, 12:20 UTC | 20h 25m |
| 2026-05-23 | UAE331 | - | May 23, 21:50 UTC | May 24, 16:10 UTC | 18h 20m |
| 2026-05-23 | UAE331 | - | May 23, 19:50 UTC | May 24, 16:10 UTC | 20h 20m |
| 2026-05-23 | UAE331 | - | May 23, 19:40 UTC | May 24, 16:10 UTC | 20h 30m |
| 2026-05-23 | UAE330 | - | May 23, 10:35 UTC | May 23, 17:10 UTC | 6h 35m |
| 2026-05-23 | UAE330 | - | May 23, 09:20 UTC | May 23, 09:30 UTC | 10m |
| 2026-05-22 | UAE35Q | MUC → DXB | May 22, 20:55 UTC | May 23, 02:25 UTC | 5h 30m |
| 2026-05-22 | UAE1DM | DXB → MUC | May 22, 05:10 UTC | May 22, 18:30 UTC | 13h 20m |
| 2026-05-22 | UAE530 | DXB → COK | May 22, 03:10 UTC | May 22, 03:20 UTC | 10m |
| 2026-05-19 | UAE359 | CGK → DXB | May 19, 21:30 UTC | May 19, 23:10 UTC | 1h 40m |
| 2026-05-19 | UAE359 | CGK → DXB | May 19, 17:40 UTC | May 19, 17:55 UTC | 15m |
| 2026-05-19 | UAE358 | DXB → CGK | May 19, 09:10 UTC | May 19, 14:20 UTC | 5h 10m |
| 2026-05-18 | UAE8M | DXB → COK | May 18, 21:15 UTC | May 18, 21:35 UTC | 20m |
| 2026-05-17 | UAE248 | GIG → DXB | May 17, 07:50 UTC | May 18, 03:25 UTC | 19h 35m |
| 2026-05-17 | UAE248 | GIG → DXB | May 17, 07:10 UTC | May 18, 03:25 UTC | 20h 15m |
| 2026-05-17 | UAE248 | GIG → DXB | May 17, 02:00 UTC | May 17, 04:20 UTC | 2h 20m |
| 2026-05-16 | UAE247 | GIG → EZE | May 16, 20:55 UTC | May 16, 23:45 UTC | 2h 50m |
| 2026-05-16 | UAE247 | GIG → EZE | May 16, 05:00 UTC | May 16, 18:50 UTC | 13h 51m |
| 2026-05-15 | UAE247 | GIG → EZE | May 15, 22:10 UTC | May 16, 18:50 UTC | 20h 41m |
| 2026-05-15 | UAE349 | SIN → DXB | May 15, 17:55 UTC | May 16, 17:45 UTC | 23h 51m |
| 2026-05-15 | UAE349 | SIN → DXB | May 15, 15:00 UTC | May 15, 15:20 UTC | 20m |
| 2026-05-15 | UAE348 | DXB → SIN | May 15, 07:55 UTC | May 15, 08:15 UTC | 20m |
| 2026-05-15 | UAE348 | DXB → SIN | May 15, 01:35 UTC | May 15, 05:45 UTC | 4h 10m |
| 2026-05-14 | UAE348 | DXB → SIN | May 14, 22:50 UTC | May 14, 23:10 UTC | 20m |
| 2026-05-14 | UAE112 | BUD → DXB | May 14, 14:20 UTC | May 14, 19:45 UTC | 5h 25m |
| 2026-05-13 | UAE76J | DXB → BUD | May 13, 17:50 UTC | May 14, 11:01 UTC | 17h 10m |
| 2026-05-13 | UAE348 | DXB → SIN | May 13, 08:10 UTC | May 13, 15:15 UTC | 7h 5m |
| 2026-05-12 | UAE348 | DXB → SIN | May 12, 15:50 UTC | May 13, 05:30 UTC | 13h 40m |
| 2026-05-12 | UAE566 | DXB → BLR | May 12, 13:00 UTC | May 12, 13:20 UTC | 20m |
| 2026-05-11 | UAE331 | - | May 11, 19:40 UTC | May 11, 22:35 UTC | 2h 54m |
| 2026-05-10 | UAE232 | IAD → DXB | May 10, 21:49 UTC | May 11, 17:35 UTC | 19h 46m |
| 2026-05-10 | UAE232 | IAD → DXB | May 10, 20:35 UTC | May 11, 17:35 UTC | 21h 1m |
| 2026-05-10 | UAE232 | IAD → DXB | May 10, 15:49 UTC | May 11, 14:20 UTC | 22h 30m |
| 2026-05-10 | UAE232 | IAD → DXB | May 10, 15:19 UTC | May 11, 13:45 UTC | 22h 25m |
| 2026-05-09 | UAE3MX | DXB → IAD | May 9, 22:10 UTC | May 10, 12:25 UTC | 14h 15m |
| 2026-05-09 | UAE6AQ | MAN → DXB | May 9, 09:05 UTC | May 9, 13:35 UTC | 4h 30m |
| 2026-05-08 | UAE1KM | DXB → MAN | May 8, 11:49 UTC | May 9, 06:10 UTC | 18h 20m |
| 2026-05-08 | UAE1KM | DXB → MAN | May 8, 09:49 UTC | May 9, 06:10 UTC | 20h 20m |
| 2026-05-08 | UAE1KM | DXB → MAN | May 8, 09:39 UTC | May 9, 06:10 UTC | 20h 30m |
| 2026-05-07 | UAE9W | DXB → LGW | May 7, 14:15 UTC | May 8, 06:20 UTC | 16h 5m |
| 2026-05-06 | UAE176 | LED → DXB | May 6, 22:00 UTC | May 7, 01:20 UTC | 3h 20m |
| 2026-05-05 | UAE232 | IAD → DXB | May 5, 16:35 UTC | May 6, 05:40 UTC | 13h 5m |
| 2026-05-05 | UAE3MX | DXB → IAD | May 5, 00:05 UTC | May 5, 14:30 UTC | 14h 25m |
| 2026-05-04 | UAE333 | MNL → DXB | May 4, 19:00 UTC | May 4, 19:15 UTC | 15m |
| 2026-05-04 | UAE333 | MNL → DXB | May 4, 10:50 UTC | May 4, 17:00 UTC | 6h 10m |
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-ECX page for operator, model, and routing details .