sensors Mode-S transponder
896188
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-EEI · AIRBUS A-380-800
- Hex
- 896188
- Octal
- 42260610
- Decimal
- 9,003,400
- Country
- AE
- Tail
- A6-EEI
- Type
- A388
- Flights observed
- 148
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 2h ago
Current position
Country allocation
The ICAO 24-bit address 896188 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 |
|---|---|---|---|
| UAE323 | Emirates | 15 | 2026-06-14 |
| UAE322 | - | 15 | 2026-06-13 |
| UAE752 | - | 8 | 2026-07-08 |
| UAE751 | - | 8 | 2026-07-08 |
| UAE385 | Emirates | 8 | 2026-06-29 |
| UAE384 | Emirates | 7 | 2026-06-29 |
| UAE7AM | - | 6 | 2026-07-11 |
| UAE51P | - | 6 | 2026-07-11 |
| UAE303 | - | 6 | 2026-07-13 |
| UAE54J | - | 5 | 2026-07-12 |
| UAE4DU | - | 5 | 2026-06-22 |
| UAE67V | - | 4 | 2026-07-12 |
| UAE52M | Emirates | 4 | 2026-06-08 |
| UAE46 | Emirates | 4 | 2026-06-08 |
| UAE362 | Emirates | 4 | 2026-05-31 |
| UAE2AR | Emirates | 4 | 2026-06-23 |
| UAE65W | Emirates | 3 | 2026-06-27 |
| UAE363 | Emirates | 3 | 2026-05-31 |
| UAE93P | - | 2 | 2026-07-06 |
| UAE7Q | - | 2 | 2026-07-10 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | UAE62T | - | Jul 14, 06:30 UTC | Jul 14, 07:20 UTC | 50m |
| 2026-07-13 | UAE303 | - | Jul 13, 19:25 UTC | Jul 14, 00:15 UTC | 4h 50m |
| 2026-07-13 | UAE303 | - | Jul 13, 04:05 UTC | Jul 14, 00:15 UTC | 20h 10m |
| 2026-07-13 | UAE303 | - | Jul 13, 02:05 UTC | Jul 14, 00:15 UTC | 22h 10m |
| 2026-07-13 | UAE302 | - | Jul 13, 00:05 UTC | Jul 14, 00:00 UTC | 23h 55m |
| 2026-07-12 | UAE302 | - | Jul 12, 23:55 UTC | Jul 13, 21:05 UTC | 21h 10m |
| 2026-07-12 | UAE54J | - | Jul 12, 14:10 UTC | Jul 12, 19:25 UTC | 5h 15m |
| 2026-07-12 | UAE67V | - | Jul 12, 06:20 UTC | Jul 12, 11:45 UTC | 5h 25m |
| 2026-07-11 | UAE51P | MAD → DXB | Jul 11, 13:55 UTC | Jul 11, 20:50 UTC | 6h 55m |
| 2026-07-11 | UAE7AM | - | Jul 11, 04:10 UTC | Jul 11, 11:25 UTC | 7h 15m |
| 2026-07-10 | UAE7Q | - | Jul 10, 00:30 UTC | Jul 10, 00:50 UTC | 20m |
| 2026-07-09 | UAE7Q | - | Jul 9, 18:50 UTC | Jul 9, 23:05 UTC | 4h 15m |
| 2026-07-09 | UAE5JM | - | Jul 9, 07:15 UTC | Jul 9, 13:55 UTC | 6h 40m |
| 2026-07-08 | UAE752 | - | Jul 8, 19:55 UTC | Jul 9, 02:45 UTC | 6h 50m |
| 2026-07-08 | UAE751 | - | Jul 8, 10:00 UTC | Jul 8, 17:20 UTC | 7h 20m |
| 2026-07-07 | UAE51P | MAD → DXB | Jul 7, 13:55 UTC | Jul 7, 20:40 UTC | 6h 45m |
| 2026-07-07 | UAE7AM | - | Jul 7, 04:20 UTC | Jul 7, 11:25 UTC | 7h 5m |
| 2026-07-06 | UAE54J | VIE → DXB | Jul 6, 13:45 UTC | Jul 6, 19:00 UTC | 5h 15m |
| 2026-07-06 | UAE67V | - | Jul 6, 05:45 UTC | Jul 6, 11:00 UTC | 5h 15m |
| 2026-07-06 | UAE93P | - | Jul 6, 00:35 UTC | Jul 6, 02:45 UTC | 2h 10m |
| 2026-07-05 | UAE93P | - | Jul 5, 20:35 UTC | Jul 6, 00:30 UTC | 3h 55m |
| 2026-07-05 | UAE7V | DXB → CDG | Jul 5, 11:15 UTC | Jul 5, 18:05 UTC | 6h 50m |
| 2026-06-29 | UAE385 | BKK → DXB | Jun 29, 23:49 UTC | Jun 30, 00:20 UTC | 30m |
| 2026-06-29 | UAE385 | BKK → DXB | Jun 29, 18:49 UTC | Jun 29, 22:55 UTC | 4h 5m |
| 2026-06-29 | UAE385 | BKK → DXB | Jun 29, 14:50 UTC | Jun 29, 16:10 UTC | 1h 20m |
| 2026-06-29 | UAE385 | BKK → DXB | Jun 29, 13:54 UTC | Jun 29, 14:09 UTC | 15m |
| 2026-06-29 | UAE384 | BKK → HKG | Jun 29, 10:00 UTC | Jun 29, 10:20 UTC | 20m |
| 2026-06-29 | UAE384 | BKK → HKG | Jun 29, 07:50 UTC | Jun 29, 09:20 UTC | 1h 30m |
| 2026-06-29 | UAE384 | BKK → HKG | Jun 29, 01:20 UTC | Jun 29, 05:45 UTC | 4h 25m |
| 2026-06-28 | UAE384 | BKK → HKG | Jun 28, 23:29 UTC | Jun 28, 23:50 UTC | 20m |
| 2026-06-28 | UAE96R | - | Jun 28, 14:09 UTC | Jun 28, 20:19 UTC | 6h 10m |
| 2026-06-28 | UAE84N | DXB → AMS | Jun 28, 04:20 UTC | Jun 28, 10:55 UTC | 6h 35m |
| 2026-06-27 | UAE65W | CDG → DXB | Jun 27, 18:09 UTC | Jun 28, 00:25 UTC | 6h 15m |
| 2026-06-27 | UAE73 | - | Jun 27, 09:34 UTC | Jun 27, 15:49 UTC | 6h 15m |
| 2026-06-26 | UAE802 | - | Jun 26, 20:40 UTC | Jun 27, 03:34 UTC | 6h 55m |
| 2026-06-26 | UAE25K | - | Jun 26, 10:25 UTC | Jun 26, 16:44 UTC | 6h 20m |
| 2026-06-26 | UAE3Q | - | Jun 26, 00:24 UTC | Jun 26, 06:54 UTC | 6h 30m |
| 2026-06-24 | UAE806 | - | Jun 24, 03:24 UTC | Jun 24, 10:25 UTC | 7h 0m |
| 2026-06-23 | UAE9YT | MRU → DXB | Jun 23, 07:09 UTC | Jun 24, 00:15 UTC | 17h 5m |
| 2026-06-23 | UAE2AR | JNB → DXB | Jun 23, 00:35 UTC | Jun 23, 01:04 UTC | 30m |
| 2026-06-22 | UAE2AR | JNB → DXB | Jun 22, 17:44 UTC | Jun 22, 18:04 UTC | 20m |
| 2026-06-22 | UAE4DU | - | Jun 22, 13:35 UTC | Jun 22, 14:19 UTC | 45m |
| 2026-06-22 | UAE4DU | - | Jun 22, 06:19 UTC | Jun 22, 06:39 UTC | 20m |
| 2026-06-17 | UAE51P | MAD → DXB | Jun 17, 13:55 UTC | Jun 17, 20:55 UTC | 7h 0m |
| 2026-06-17 | UAE7AM | - | Jun 17, 03:50 UTC | Jun 17, 10:50 UTC | 7h 0m |
| 2026-06-15 | UAE5W | - | Jun 15, 21:50 UTC | Jun 15, 23:04 UTC | 1h 15m |
| 2026-06-15 | UAE903 | DXB → AMM | Jun 15, 14:34 UTC | Jun 15, 14:50 UTC | 15m |
| 2026-06-14 | UAE54J | VIE → DXB | Jun 14, 14:10 UTC | Jun 14, 19:40 UTC | 5h 30m |
| 2026-06-14 | UAE67V | - | Jun 14, 05:40 UTC | Jun 14, 10:45 UTC | 5h 5m |
| 2026-06-14 | UAE323 | ICN → DXB | Jun 14, 00:05 UTC | Jun 14, 00:25 UTC | 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-EEI page for operator, model, and routing details .