sensors Mode-S transponder
896617
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-EFY · BOEING 777-200LR
- Hex
- 896617
- Octal
- 42263027
- Decimal
- 9,004,567
- Country
- AE
- Tail
- A6-EFY
- Type
- B77L
- Flights observed
- 131
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 1h ago
Current position
Country allocation
The ICAO 24-bit address 896617 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 |
|---|---|---|---|
| UAE9942 | Emirates | 10 | 2026-05-21 |
| UAE9618 | - | 9 | 2026-04-16 |
| UAE9917 | Emirates | 8 | 2026-04-28 |
| UAE9913 | Emirates | 8 | 2026-04-17 |
| UAE9935 | Emirates | 7 | 2026-05-28 |
| UAE9936 | Emirates | 6 | 2026-05-30 |
| UAE9906 | Emirates | 6 | 2026-05-17 |
| UAE9941 | - | 5 | 2026-05-20 |
| UAE9820 | - | 4 | 2026-04-13 |
| UAE9658 | - | 4 | 2026-05-23 |
| UAE9657 | - | 4 | 2026-05-23 |
| UAE37N | - | 4 | 2026-04-29 |
| UAE9878 | Emirates | 3 | 2026-05-07 |
| UAE9858 | - | 3 | 2026-05-09 |
| UAE9827 | Emirates | 3 | 2026-05-04 |
| UAE9825 | Emirates | 3 | 2026-04-16 |
| UAE9815 | - | 3 | 2026-05-18 |
| UAE9656 | - | 3 | 2026-05-27 |
| UAE9616 | Emirates | 3 | 2026-05-03 |
| UAE6MR | Emirates | 3 | 2026-05-29 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | UAE9936 | JFK → AMS | May 30, 03:25 UTC | May 30, 03:45 UTC | 20m |
| 2026-05-29 | UAE9936 | JFK → AMS | May 29, 16:25 UTC | May 30, 01:50 UTC | 9h 25m |
| 2026-05-29 | UAE6MR | IAH → FRA | May 29, 10:45 UTC | May 29, 12:35 UTC | 1h 50m |
| 2026-05-28 | UAE9935 | FRA → MEX | May 28, 19:55 UTC | May 29, 07:00 UTC | 11h 5m |
| 2026-05-28 | UAE9935 | FRA → MEX | May 28, 00:00 UTC | May 28, 16:20 UTC | 16h 20m |
| 2026-05-27 | UAE9835 | HKG → DWC | May 27, 22:00 UTC | May 27, 22:15 UTC | 15m |
| 2026-05-27 | UAE9772 | - | May 27, 18:50 UTC | May 27, 19:20 UTC | 30m |
| 2026-05-27 | UAE9656 | - | May 27, 02:29 UTC | May 27, 16:20 UTC | 13h 51m |
| 2026-05-26 | UAE9656 | - | May 26, 15:39 UTC | May 27, 00:19 UTC | 8h 40m |
| 2026-05-26 | UAE9656 | - | May 26, 11:00 UTC | May 26, 13:15 UTC | 2h 15m |
| 2026-05-26 | UAE9989 | LCK → ORD | May 26, 00:19 UTC | May 26, 08:34 UTC | 8h 15m |
| 2026-05-25 | UAE9989 | LCK → ORD | May 25, 07:30 UTC | May 25, 21:19 UTC | 13h 49m |
| 2026-05-24 | UAE9795 | - | May 24, 15:10 UTC | May 24, 15:20 UTC | 10m |
| 2026-05-24 | UAE9794 | DWC → ICN | May 24, 12:10 UTC | May 24, 12:30 UTC | 20m |
| 2026-05-23 | UAE9658 | - | May 23, 15:05 UTC | May 23, 21:35 UTC | 6h 30m |
| 2026-05-23 | UAE9658 | AMS → OSL | May 23, 10:40 UTC | May 23, 12:00 UTC | 1h 20m |
| 2026-05-23 | UAE9657 | - | May 23, 04:10 UTC | May 23, 08:30 UTC | 4h 20m |
| 2026-05-22 | UAE9657 | - | May 22, 18:25 UTC | May 22, 18:50 UTC | 25m |
| 2026-05-21 | UAE9942 | JFK → AMS | May 21, 21:50 UTC | May 22, 16:10 UTC | 18h 20m |
| 2026-05-21 | UAE9942 | JFK → AMS | May 21, 20:05 UTC | May 22, 16:10 UTC | 20h 5m |
| 2026-05-21 | UAE9942 | JFK → AMS | May 21, 08:35 UTC | May 21, 16:40 UTC | 8h 5m |
| 2026-05-21 | UAE9942 | JFK → AMS | May 21, 03:30 UTC | May 21, 06:35 UTC | 3h 5m |
| 2026-05-20 | UAE9942 | JFK → AMS | May 20, 17:05 UTC | May 20, 23:10 UTC | 6h 5m |
| 2026-05-20 | UAE9941 | - | May 20, 12:05 UTC | May 20, 14:30 UTC | 2h 25m |
| 2026-05-19 | UAE9941 | - | May 19, 16:50 UTC | May 20, 09:55 UTC | 17h 6m |
| 2026-05-19 | UAE9941 | - | May 19, 12:30 UTC | May 20, 09:55 UTC | 21h 26m |
| 2026-05-18 | UAE9815 | - | May 18, 23:40 UTC | May 19, 17:20 UTC | 17h 40m |
| 2026-05-18 | UAE9815 | - | May 18, 20:40 UTC | May 19, 17:20 UTC | 20h 40m |
| 2026-05-18 | UAE9815 | - | May 18, 14:15 UTC | May 19, 13:00 UTC | 22h 44m |
| 2026-05-18 | UAE9814 | DWC → HAN | May 18, 12:10 UTC | May 19, 00:10 UTC | 11h 59m |
| 2026-05-17 | UAE9814 | DWC → HAN | May 17, 23:20 UTC | May 18, 21:45 UTC | 22h 24m |
| 2026-05-17 | UAE9906 | MAD → DWC | May 17, 19:50 UTC | May 18, 14:55 UTC | 19h 5m |
| 2026-05-17 | UAE9906 | MAD → DWC | May 17, 17:50 UTC | May 18, 14:55 UTC | 21h 5m |
| 2026-05-17 | UAE9906 | MAD → DWC | May 17, 13:55 UTC | May 17, 15:50 UTC | 1h 55m |
| 2026-05-16 | UAE9658 | - | May 16, 15:50 UTC | May 17, 11:01 UTC | 19h 10m |
| 2026-05-16 | UAE9658 | - | May 16, 10:50 UTC | May 16, 12:16 UTC | 1h 25m |
| 2026-05-16 | UAE9657 | - | May 16, 03:05 UTC | May 16, 07:51 UTC | 4h 46m |
| 2026-05-15 | UAE9657 | - | May 15, 16:45 UTC | May 15, 17:05 UTC | 20m |
| 2026-05-14 | UAE9942 | JFK → AMS | May 14, 19:50 UTC | May 15, 14:20 UTC | 18h 30m |
| 2026-05-14 | UAE9942 | JFK → AMS | May 14, 18:55 UTC | May 15, 14:20 UTC | 19h 25m |
| 2026-05-14 | UAE9942 | JFK → AMS | May 14, 07:35 UTC | May 14, 15:20 UTC | 7h 45m |
| 2026-05-14 | UAE9942 | JFK → AMS | May 14, 04:25 UTC | May 14, 04:55 UTC | 30m |
| 2026-05-13 | UAE9942 | JFK → AMS | May 13, 16:35 UTC | May 13, 21:35 UTC | 5h 0m |
| 2026-05-13 | UAE9941 | - | May 13, 10:50 UTC | May 13, 13:40 UTC | 2h 50m |
| 2026-05-13 | UAE9941 | - | May 13, 06:45 UTC | May 13, 08:15 UTC | 1h 30m |
| 2026-05-12 | UAE9936 | JFK → AMS | May 12, 03:40 UTC | May 12, 07:30 UTC | 3h 50m |
| 2026-05-11 | UAE9936 | JFK → AMS | May 11, 16:45 UTC | May 11, 20:05 UTC | 3h 20m |
| 2026-05-11 | UAE6MR | IAH → FRA | May 11, 10:55 UTC | May 11, 12:25 UTC | 1h 30m |
| 2026-05-10 | UAE9935 | FRA → MEX | May 10, 21:19 UTC | May 11, 08:55 UTC | 11h 35m |
| 2026-05-09 | UAE9935 | FRA → MEX | May 9, 21:50 UTC | May 10, 16:10 UTC | 18h 20m |
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-EFY page for operator, model, and routing details .