sensors Mode-S transponder
896475
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-EUK · AIRBUS A-380-800
- Hex
- 896475
- Octal
- 42262165
- Decimal
- 9,004,149
- Country
- AE
- Tail
- A6-EUK
- Type
- A388
- Flights observed
- 141
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 5h ago
Last known position
Country allocation
The ICAO 24-bit address 896475 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 |
|---|---|---|---|
| UAE261 | Emirates | 19 | 2026-06-24 |
| UAE319 | Emirates | 18 | 2026-06-12 |
| UAE262 | Emirates | 16 | 2026-06-25 |
| UAE318 | Emirates | 9 | 2026-06-04 |
| UAE62P | - | 7 | 2026-07-13 |
| UAE373 | Emirates | 7 | 2026-07-03 |
| UAE67M | - | 6 | 2026-07-13 |
| UAE7CN | - | 5 | 2026-07-12 |
| UAE7 | - | 5 | 2026-07-11 |
| UAE2VL | - | 5 | 2026-07-10 |
| UAE1Y | - | 5 | 2026-07-09 |
| UAE83M | Emirates | 4 | 2026-06-26 |
| UAE51N | Emirates | 4 | 2026-06-05 |
| UAE2 | Emirates | 4 | 2026-06-19 |
| UAE1 | - | 4 | 2026-06-19 |
| UAE372 | - | 3 | 2026-07-03 |
| UAE216 | Emirates | 3 | 2026-06-27 |
| UAE501 | Emirates | 2 | 2026-05-11 |
| UAE41P | Emirates | 2 | 2026-06-06 |
| UAE414 | - | 2 | 2026-07-01 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | UAE67M | - | Jul 13, 19:25 UTC | Jul 13, 20:45 UTC | 1h 20m |
| 2026-07-13 | UAE62P | - | Jul 13, 09:20 UTC | Jul 13, 12:35 UTC | 3h 15m |
| 2026-07-13 | UAE62P | - | Jul 13, 00:01 UTC | Jul 13, 00:20 UTC | 20m |
| 2026-07-12 | UAE7CN | - | Jul 12, 08:50 UTC | Jul 12, 16:15 UTC | 7h 25m |
| 2026-07-11 | UAE7 | - | Jul 11, 23:10 UTC | Jul 12, 06:01 UTC | 6h 50m |
| 2026-07-11 | UAE5W | - | Jul 11, 15:30 UTC | Jul 11, 18:10 UTC | 2h 40m |
| 2026-07-11 | UAE903 | - | Jul 11, 10:10 UTC | Jul 11, 12:35 UTC | 2h 25m |
| 2026-07-10 | UAE2VL | - | Jul 10, 01:05 UTC | Jul 10, 15:40 UTC | 14h 35m |
| 2026-07-09 | UAE1Y | - | Jul 9, 06:15 UTC | Jul 9, 22:00 UTC | 15h 45m |
| 2026-07-08 | UAE39L | - | Jul 8, 20:35 UTC | Jul 9, 02:10 UTC | 5h 35m |
| 2026-07-08 | UAE9LT | - | Jul 8, 12:00 UTC | Jul 8, 18:05 UTC | 6h 5m |
| 2026-07-07 | UAE67M | - | Jul 7, 19:25 UTC | Jul 8, 08:15 UTC | 12h 50m |
| 2026-07-07 | UAE62P | - | Jul 7, 02:20 UTC | Jul 7, 12:05 UTC | 9h 45m |
| 2026-07-06 | UAE62P | - | Jul 6, 23:25 UTC | Jul 6, 23:50 UTC | 25m |
| 2026-07-06 | UAE7CN | - | Jul 6, 13:50 UTC | Jul 6, 14:45 UTC | 55m |
| 2026-07-06 | UAE7CN | - | Jul 6, 08:25 UTC | Jul 6, 12:45 UTC | 4h 20m |
| 2026-07-05 | UAE7 | - | Jul 5, 23:00 UTC | Jul 6, 06:00 UTC | 7h 0m |
| 2026-07-03 | UAE373 | BKK → DXB | Jul 3, 20:15 UTC | Jul 3, 20:50 UTC | 35m |
| 2026-07-03 | UAE373 | BKK → DXB | Jul 3, 14:55 UTC | Jul 3, 19:10 UTC | 4h 15m |
| 2026-07-03 | UAE372 | - | Jul 3, 06:10 UTC | Jul 3, 12:05 UTC | 5h 55m |
| 2026-07-03 | UAE569 | - | Jul 3, 00:40 UTC | Jul 3, 03:50 UTC | 3h 10m |
| 2026-07-02 | UAE568 | DXB → BLR | Jul 2, 19:15 UTC | Jul 2, 22:35 UTC | 3h 20m |
| 2026-07-01 | UAE1DP | SYD → DXB | Jul 1, 20:25 UTC | Jul 2, 10:25 UTC | 14h 0m |
| 2026-07-01 | UAE414 | - | Jul 1, 10:55 UTC | Jul 1, 11:30 UTC | 35m |
| 2026-06-30 | UAE414 | - | Jun 30, 22:40 UTC | Jun 30, 23:00 UTC | 20m |
| 2026-06-27 | UAE216 | LAX → DXB | Jun 27, 00:00 UTC | Jun 27, 15:55 UTC | 15h 55m |
| 2026-06-26 | UAE83M | DXB → LAX | Jun 26, 18:04 UTC | Jun 26, 21:04 UTC | 3h 0m |
| 2026-06-26 | UAE83M | DXB → LAX | Jun 26, 04:59 UTC | Jun 26, 05:19 UTC | 20m |
| 2026-06-25 | UAE262 | GRU → DXB | Jun 25, 05:29 UTC | Jun 25, 19:54 UTC | 14h 25m |
| 2026-06-24 | UAE261 | DXB → GRU | Jun 24, 05:24 UTC | Jun 24, 20:05 UTC | 14h 40m |
| 2026-06-23 | UAE262 | GRU → DXB | Jun 23, 04:29 UTC | Jun 23, 18:39 UTC | 14h 10m |
| 2026-06-22 | UAE261 | DXB → GRU | Jun 22, 04:59 UTC | Jun 22, 19:29 UTC | 14h 30m |
| 2026-06-21 | UAE262 | GRU → DXB | Jun 21, 04:49 UTC | Jun 21, 19:05 UTC | 14h 15m |
| 2026-06-20 | UAE261 | DXB → GRU | Jun 20, 04:59 UTC | Jun 20, 19:40 UTC | 14h 40m |
| 2026-06-19 | UAE2 | LHR → DXB | Jun 19, 13:50 UTC | Jun 19, 21:04 UTC | 7h 15m |
| 2026-06-19 | UAE1 | - | Jun 19, 04:14 UTC | Jun 19, 11:09 UTC | 6h 55m |
| 2026-06-18 | UAE67M | MEL → DXB | Jun 18, 08:30 UTC | Jun 18, 08:50 UTC | 20m |
| 2026-06-17 | UAE67M | MEL → DXB | Jun 17, 19:35 UTC | Jun 18, 05:50 UTC | 10h 15m |
| 2026-06-17 | UAE62P | DXB → MEL | Jun 17, 10:55 UTC | Jun 17, 12:10 UTC | 1h 15m |
| 2026-06-16 | UAE62P | DXB → MEL | Jun 16, 23:15 UTC | Jun 16, 23:40 UTC | 25m |
| 2026-06-16 | UAE67M | MEL → DXB | Jun 16, 08:39 UTC | Jun 16, 09:00 UTC | 20m |
| 2026-06-15 | UAE67M | MEL → DXB | Jun 15, 19:25 UTC | Jun 16, 06:10 UTC | 10h 45m |
| 2026-06-15 | UAE62P | DXB → MEL | Jun 15, 02:15 UTC | Jun 15, 12:00 UTC | 9h 45m |
| 2026-06-14 | UAE2VL | IAH → DXB | Jun 14, 00:50 UTC | Jun 14, 15:25 UTC | 14h 35m |
| 2026-06-13 | UAE1Y | DXB → IAH | Jun 13, 09:30 UTC | Jun 13, 22:05 UTC | 12h 35m |
| 2026-06-12 | UAE319 | NRT → DXB | Jun 12, 23:45 UTC | Jun 13, 00:00 UTC | 15m |
| 2026-06-12 | UAE319 | NRT → DXB | Jun 12, 13:40 UTC | Jun 12, 22:40 UTC | 9h 0m |
| 2026-06-10 | UAE216 | LAX → DXB | Jun 10, 23:55 UTC | Jun 11, 15:50 UTC | 15h 55m |
| 2026-06-10 | UAE83M | DXB → LAX | Jun 10, 18:20 UTC | Jun 10, 21:05 UTC | 2h 45m |
| 2026-06-09 | UAE2 | LHR → DXB | Jun 9, 14:00 UTC | Jun 9, 21:00 UTC | 7h 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-EUK page for operator, model, and routing details .