sensors Mode-S transponder

896378

ICAO 24-bit transponder address · allocated to United Arab Emirates

Currently assigned to A6-FEG · BOEING 737-800

Hex
896378
Octal
42261570
Decimal
9,003,896
Country
AE
Tail
A6-FEG
Type
B738
No current signal · last broadcast 3h ago
Flights observed
60
Distinct callsigns
20
Country
AE
Last broadcast
3h ago

Last known position

Most recent position reported by Mode-S 896378.

Country allocation

The ICAO 24-bit address 896378 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
FDB868 Fly Dubai 3 2026-06-28
FDB756 - 3 2026-07-02
FDB3VG - 3 2026-07-02
FDB1808 Fly Dubai 3 2026-05-29
FDB876 - 2 2026-07-06
FDB830 Fly Dubai 2 2026-07-01
FDB760 - 2 2026-07-04
FDB759 - 2 2026-07-04
FDB4PD - 2 2026-07-03
FDB2AP - 2 2026-07-03
FDB1KF - 2 2026-07-01
FDB1212 - 2 2026-07-02
FDB1211 - 2 2026-07-02
FDB920 - 1 2026-07-04
FDB914 Fly Dubai 1 2026-06-01
FDB8876 - 1 2026-05-02
FDB867 - 1 2026-06-28
FDB846 - 1 2026-06-28
FDB842 Fly Dubai 1 2026-05-15
FDB816 - 1 2026-07-05

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-06 FDB876 - Jul 6, 12:30 UTCJul 6, 17:30 UTC5h 0m
2026-07-05 FDB816 - Jul 5, 06:45 UTCJul 5, 12:50 UTC6h 5m
2026-07-04 FDB920 - Jul 4, 22:15 UTCJul 5, 04:45 UTC6h 30m
2026-07-04 FDB760 - Jul 4, 13:40 UTCJul 4, 17:05 UTC3h 25m
2026-07-04 FDB759 - Jul 4, 08:10 UTCJul 4, 12:05 UTC3h 55m
2026-07-03 FDB43F - Jul 3, 15:55 UTCJul 3, 20:55 UTC5h 0m
2026-07-03 FDB4PD - Jul 3, 13:15 UTCJul 3, 13:50 UTC35m
2026-07-03 FDB2AP - Jul 3, 10:55 UTCJul 3, 11:20 UTC25m
2026-07-03 FDB1YT - Jul 3, 07:45 UTCJul 3, 08:35 UTC50m
2026-07-03 FDB4JZ - Jul 3, 05:45 UTCJul 3, 06:30 UTC45m
2026-07-02 FDB756 - Jul 2, 23:20 UTCJul 3, 03:25 UTC4h 5m
2026-07-02 FDB3VG - Jul 2, 17:05 UTCJul 2, 21:10 UTC4h 5m
2026-07-02 FDB1212 - Jul 2, 10:40 UTCJul 2, 13:25 UTC2h 45m
2026-07-02 FDB1211 DXB → TLV Jul 2, 06:20 UTCJul 2, 09:15 UTC2h 55m
2026-07-01 FDB830 JED → DXB Jul 1, 11:10 UTCJul 1, 17:15 UTC6h 5m
2026-07-01 FDB1KF - Jul 1, 03:50 UTCJul 1, 08:35 UTC4h 45m
2026-06-30 FDB876 TIF → DXB Jun 30, 13:55 UTCJun 30, 18:40 UTC4h 45m
2026-06-29 FDB435 - Jun 29, 17:30 UTCJun 30, 01:19 UTC7h 50m
2026-06-28 FDB846 - Jun 28, 20:14 UTCJun 29, 01:00 UTC4h 45m
2026-06-28 FDB868 DMM → DXB Jun 28, 16:45 UTCJun 28, 17:44 UTC1h 0m
2026-06-28 FDB867 - Jun 28, 14:14 UTCJun 28, 15:05 UTC50m
2026-06-27 FDB3HP DXB → DXB Jun 27, 08:49 UTCJun 27, 15:49 UTC7h 0m
2026-06-26 FDB1941 - Jun 26, 18:09 UTCJun 27, 03:04 UTC8h 55m
2026-06-26 FDB1212 TLV → DXB Jun 26, 11:34 UTCJun 26, 14:29 UTC2h 55m
2026-06-26 FDB1211 DXB → TLV Jun 26, 07:14 UTCJun 26, 10:05 UTC2h 50m
2026-06-25 FDB808 JED → DXB Jun 25, 16:14 UTCJun 25, 22:54 UTC6h 40m
2026-06-25 FDB59K - Jun 25, 08:55 UTCJun 25, 13:45 UTC4h 50m
2026-06-24 FDB756 - Jun 24, 23:45 UTCJun 25, 03:44 UTC4h 0m
2026-06-24 FDB3VG - Jun 24, 17:34 UTCJun 24, 21:54 UTC4h 20m
2026-06-24 FDB4PD - Jun 24, 13:20 UTCJun 24, 13:40 UTC20m
2026-06-24 FDB2AP - Jun 24, 10:55 UTCJun 24, 11:20 UTC25m
2026-06-24 FDB2GT - Jun 24, 08:14 UTCJun 24, 08:30 UTC15m
2026-06-24 FDB1KF - Jun 24, 03:50 UTCJun 24, 04:15 UTC25m
2026-06-23 FDB662 - Jun 23, 11:49 UTCJun 23, 12:20 UTC30m
2026-06-23 FDB661 - Jun 23, 04:50 UTCJun 23, 05:04 UTC15m
2026-06-17 FDB3YK DXB → DOH Jun 17, 13:35 UTCJun 17, 14:25 UTC50m
2026-06-16 FDB830 JED → DXB Jun 16, 16:15 UTCJun 16, 16:55 UTC40m
2026-06-15 FDB7XZ BGW → DXB Jun 15, 07:05 UTCJun 15, 12:39 UTC5h 35m
2026-06-13 FDB756 IST → DXB Jun 13, 23:40 UTCJun 14, 00:55 UTC1h 15m
2026-06-13 FDB3VG DXB → IST Jun 13, 18:15 UTCJun 13, 21:55 UTC3h 40m
2026-06-08 FDB2MF IST → DXB Jun 8, 17:25 UTCJun 9, 10:00 UTC16h 35m
2026-06-05 FDB760 AYT → DXB Jun 5, 13:30 UTCJun 5, 17:25 UTC3h 55m
2026-06-05 FDB759 DXB → AYT Jun 5, 11:15 UTCJun 5, 11:35 UTC20m
2026-06-03 FDB733 DXB → GYD Jun 3, 16:05 UTCJun 3, 17:00 UTC55m
2026-06-01 FDB914 AJF → DXB Jun 1, 10:40 UTCJun 1, 11:15 UTC35m
2026-05-31 FDB1550 TLV → DXB May 31, 08:35 UTCMay 31, 08:55 UTC20m
2026-05-30 FDB1082 TLV → DXB May 30, 13:10 UTCMay 30, 15:45 UTC2h 35m
2026-05-30 FDB1081 DXB → TLV May 30, 11:10 UTCMay 30, 11:35 UTC25m
2026-05-29 FDB1808 TLV → DXB May 29, 14:15 UTCMay 29, 14:55 UTC40m
2026-05-29 FDB1808 TLV → DXB May 29, 12:20 UTCMay 29, 12:45 UTC25m

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-FEG page for operator, model, and routing details .

Mode-S 896378 frequently asked

What is Mode-S code 896378?
896378 is an ICAO 24-bit transponder address. Allocated to United Arab Emirates. Assigned to A6-FEG.
Where is Mode-S 896378 registered?
Mode-S code 896378 is allocated to United Arab Emirates (AE). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 896378 broadcasting right now?
No active broadcast right now. Last signal was 3h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 896378, octal 42261570, decimal 9,003,896.
What flights does 896378 operate?
Mode-S 896378 has broadcast 20 distinct callsigns, including FDB868, FDB756, FDB3VG, FDB1808, FDB876.