sensors Mode-S transponder
89610F
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-ECH · BOEING 777-300ER
- Hex
- 89610F
- Octal
- 42260417
- Decimal
- 9,003,279
- Country
- AE
- Tail
- A6-ECH
- Type
- B77W
- Flights observed
- 93
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address 89610F 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 | 7 | 2026-05-28 |
| UAE348 | Emirates | 7 | 2026-06-05 |
| UAE2J | Emirates | 5 | 2026-05-25 |
| UAE247 | Emirates | 5 | 2026-06-13 |
| UAE8M | Emirates | 4 | 2026-06-03 |
| UAE797 | Emirates | 4 | 2026-05-09 |
| UAE232 | Emirates | 4 | 2026-06-02 |
| UAE9Q | Emirates | 3 | 2026-05-13 |
| UAE566 | Emirates | 3 | 2026-05-20 |
| UAE359 | Emirates | 3 | 2026-05-28 |
| UAE349 | Emirates | 3 | 2026-06-05 |
| UAE795 | Emirates | 2 | 2026-05-15 |
| UAE784 | Emirates | 2 | 2026-05-22 |
| UAE648 | Emirates | 2 | 2026-05-01 |
| UAE508 | Emirates | 2 | 2026-06-01 |
| UAE3MX | Emirates | 2 | 2026-06-01 |
| UAE333 | Emirates | 2 | 2026-05-07 |
| UAE332 | Emirates | 2 | 2026-05-23 |
| UAE330 | - | 2 | 2026-04-29 |
| UAE248 | Emirates | 2 | 2026-06-09 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-13 | UAE247 | GIG → EZE | Jun 13, 17:35 UTC | Jun 13, 17:45 UTC | 10m |
| 2026-06-12 | UAE375 | BKK → DXB | Jun 12, 03:05 UTC | Jun 12, 07:20 UTC | 4h 15m |
| 2026-06-11 | UAE374 | DXB → BKK | Jun 11, 10:55 UTC | Jun 12, 00:45 UTC | 13h 51m |
| 2026-06-11 | UAE18V | DXB → BOM | Jun 11, 07:10 UTC | Jun 11, 08:30 UTC | 1h 20m |
| 2026-06-09 | UAE248 | GIG → DXB | Jun 9, 06:30 UTC | Jun 9, 07:10 UTC | 40m |
| 2026-06-09 | UAE248 | GIG → DXB | Jun 9, 02:20 UTC | Jun 9, 04:30 UTC | 2h 10m |
| 2026-06-08 | UAE247 | GIG → EZE | Jun 8, 21:20 UTC | Jun 9, 00:30 UTC | 3h 10m |
| 2026-06-08 | UAE247 | GIG → EZE | Jun 8, 05:05 UTC | Jun 8, 19:05 UTC | 14h 0m |
| 2026-06-07 | UAE136 | VCE → DXB | Jun 7, 14:05 UTC | Jun 8, 05:10 UTC | 15h 5m |
| 2026-06-07 | UAE135 | DXB → VCE | Jun 7, 07:25 UTC | Jun 7, 11:00 UTC | 3h 35m |
| 2026-06-05 | UAE349 | SIN → DXB | Jun 5, 18:20 UTC | Jun 5, 23:00 UTC | 4h 40m |
| 2026-06-05 | UAE348 | DXB → SIN | Jun 5, 08:00 UTC | Jun 5, 15:20 UTC | 7h 20m |
| 2026-06-04 | UAE348 | DXB → SIN | Jun 4, 16:55 UTC | Jun 5, 05:45 UTC | 12h 50m |
| 2026-06-04 | UAE112 | BUD → DXB | Jun 4, 14:15 UTC | Jun 4, 16:50 UTC | 2h 35m |
| 2026-06-03 | UAE76J | DXB → BUD | Jun 3, 23:15 UTC | Jun 4, 11:30 UTC | 12h 15m |
| 2026-06-03 | UAE8M | DXB → COK | Jun 3, 02:25 UTC | Jun 3, 21:10 UTC | 18h 45m |
| 2026-06-02 | UAE232 | IAD → DXB | Jun 2, 23:50 UTC | Jun 3, 21:10 UTC | 21h 20m |
| 2026-06-02 | UAE232 | IAD → DXB | Jun 2, 21:50 UTC | Jun 3, 21:10 UTC | 23h 20m |
| 2026-06-02 | UAE232 | IAD → DXB | Jun 2, 20:35 UTC | Jun 3, 19:45 UTC | 23h 10m |
| 2026-06-02 | UAE232 | IAD → DXB | Jun 2, 15:10 UTC | Jun 3, 03:05 UTC | 11h 55m |
| 2026-06-01 | UAE3MX | DXB → IAD | Jun 1, 17:50 UTC | Jun 2, 12:00 UTC | 18h 10m |
| 2026-06-01 | UAE3MX | DXB → IAD | Jun 1, 17:35 UTC | Jun 2, 12:00 UTC | 18h 25m |
| 2026-06-01 | UAE508 | DXB → BOM | Jun 1, 14:15 UTC | Jun 1, 15:10 UTC | 55m |
| 2026-06-01 | UAE531 | COK → DXB | Jun 1, 05:35 UTC | Jun 1, 05:45 UTC | 10m |
| 2026-05-30 | UAE247 | GIG → EZE | May 30, 21:20 UTC | May 31, 00:15 UTC | 2h 55m |
| 2026-05-30 | UAE247 | GIG → EZE | May 30, 11:40 UTC | May 30, 19:30 UTC | 7h 50m |
| 2026-05-28 | UAE359 | CGK → DXB | May 28, 17:50 UTC | May 28, 22:15 UTC | 4h 25m |
| 2026-05-28 | UAE358 | DXB → CGK | May 28, 14:45 UTC | May 28, 14:55 UTC | 10m |
| 2026-05-28 | UAE358 | DXB → CGK | May 28, 09:00 UTC | May 28, 14:10 UTC | 5h 10m |
| 2026-05-27 | UAE358 | DXB → CGK | May 27, 18:05 UTC | May 28, 14:10 UTC | 20h 5m |
| 2026-05-27 | UAE358 | DXB → CGK | May 27, 17:15 UTC | May 28, 14:10 UTC | 20h 55m |
| 2026-05-27 | UAE508 | DXB → BOM | May 27, 05:29 UTC | May 27, 15:00 UTC | 9h 30m |
| 2026-05-26 | UAE220 | MCO → DXB | May 26, 08:15 UTC | May 27, 03:29 UTC | 19h 15m |
| 2026-05-26 | UAE220 | MCO → DXB | May 26, 01:20 UTC | May 26, 14:55 UTC | 13h 35m |
| 2026-05-25 | UAE2J | DXB → MCO | May 25, 02:15 UTC | May 25, 14:10 UTC | 11h 55m |
| 2026-05-24 | UAE2J | DXB → MCO | May 24, 16:35 UTC | May 25, 14:10 UTC | 21h 35m |
| 2026-05-24 | UAE2J | DXB → MCO | May 24, 13:50 UTC | May 25, 13:45 UTC | 23h 55m |
| 2026-05-24 | UAE2J | DXB → MCO | May 24, 12:55 UTC | May 25, 06:50 UTC | 17h 55m |
| 2026-05-24 | UAE2J | DXB → MCO | May 24, 10:45 UTC | May 25, 06:50 UTC | 20h 5m |
| 2026-05-23 | UAE332 | DXB → MNL | May 23, 17:15 UTC | May 24, 08:30 UTC | 15h 16m |
| 2026-05-23 | UAE332 | DXB → MNL | May 23, 10:40 UTC | May 24, 08:30 UTC | 21h 51m |
| 2026-05-23 | UAE98N | DXB → CCU | May 23, 09:35 UTC | May 23, 09:45 UTC | 10m |
| 2026-05-22 | UAE784 | LOS → DXB | May 22, 22:55 UTC | May 22, 23:25 UTC | 30m |
| 2026-05-21 | UAE349 | SIN → DXB | May 21, 18:10 UTC | May 21, 23:05 UTC | 4h 55m |
| 2026-05-20 | UAE348 | DXB → SIN | May 20, 15:50 UTC | May 21, 05:35 UTC | 13h 45m |
| 2026-05-20 | UAE566 | DXB → BLR | May 20, 11:45 UTC | May 20, 13:15 UTC | 1h 30m |
| 2026-05-18 | UAE784 | LOS → DXB | May 18, 02:10 UTC | May 18, 11:10 UTC | 9h 0m |
| 2026-05-15 | UAE795 | DSS → DXB | May 15, 19:35 UTC | May 16, 12:55 UTC | 17h 21m |
| 2026-05-15 | UAE795 | DSS → DXB | May 15, 16:35 UTC | May 15, 17:05 UTC | 30m |
| 2026-05-14 | UAE24E | - | May 14, 13:05 UTC | May 15, 01:05 UTC | 12h 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-ECH page for operator, model, and routing details .