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 25d ago
Flights observed
107
Distinct callsigns
20
Country
AE
Last broadcast
25d 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 - 4 2026-07-12
FDB75L - 3 2026-07-13
FDB756 - 3 2026-07-02
FDB733 Fly Dubai 3 2026-07-26
FDB3VG - 3 2026-07-02
FDB3HP - 3 2026-07-17
FDB1808 Fly Dubai 3 2026-05-29
FDB15L - 3 2026-07-13
FDB9JZ Fly Dubai 2 2026-07-25
FDB920 - 2 2026-07-06
FDB876 - 2 2026-07-06
FDB867 - 2 2026-07-12
FDB830 Fly Dubai 2 2026-07-01
FDB760 - 2 2026-07-04
FDB759 - 2 2026-07-04
FDB71T - 2 2026-07-14
FDB4PD - 2 2026-07-03
FDB43F - 2 2026-07-11
FDB435 Fly Dubai 2 2026-07-19
FDB2RK Fly Dubai 2 2026-07-17

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-26 FDB733 DXB → GYD Jul 26, 12:55 UTCJul 26, 16:10 UTC3h 15m
2026-07-26 FDB932 NUM → DXB Jul 26, 04:50 UTCJul 26, 11:10 UTC6h 21m
2026-07-25 FDB9JZ GYD → DXB Jul 25, 23:00 UTCJul 25, 23:15 UTC15m
2026-07-25 FDB733 DXB → GYD Jul 25, 13:25 UTCJul 25, 16:45 UTC3h 20m
2026-07-25 FDB5WB BEY → DXB Jul 25, 07:25 UTCJul 25, 10:25 UTC3h 0m
2026-07-25 FDB5JA DXB → BEY Jul 25, 03:20 UTCJul 25, 05:50 UTC2h 30m
2026-07-24 FDB2RG OTP → DXB Jul 24, 12:20 UTCJul 24, 17:45 UTC5h 25m
2026-07-24 FDB3PL DXB → OTP Jul 24, 06:30 UTCJul 24, 11:00 UTC4h 30m
2026-07-23 FDB872 - Jul 23, 19:45 UTCJul 24, 01:10 UTC5h 25m
2026-07-23 FDB1114 DAM → DXB Jul 23, 13:40 UTCJul 23, 17:05 UTC3h 25m
2026-07-23 FDB1113 DXB → DAM Jul 23, 09:10 UTCJul 23, 11:35 UTC2h 25m
2026-07-22 FDB2MF - Jul 22, 16:25 UTCJul 22, 20:20 UTC3h 55m
2026-07-21 FDB201 DXB → EBL Jul 21, 12:05 UTCJul 22, 10:25 UTC22h 20m
2026-07-20 FDB1114 - Jul 20, 14:30 UTCJul 20, 18:00 UTC3h 30m
2026-07-20 FDB1113 DXB → DAM Jul 20, 10:05 UTCJul 20, 12:30 UTC2h 25m
2026-07-19 FDB435 DXB → HYD Jul 19, 17:00 UTCJul 19, 23:05 UTC6h 5m
2026-07-17 FDB3HP - Jul 17, 22:10 UTCJul 18, 15:55 UTC17h 46m
2026-07-17 FDB9RF DXB → COK Jul 17, 17:09 UTCJul 17, 17:30 UTC20m
2026-07-17 FDB2RK GYD → DXB Jul 17, 03:25 UTCJul 17, 13:10 UTC9h 45m
2026-07-16 FDB1ND - Jul 16, 14:50 UTCJul 16, 19:05 UTC4h 15m
2026-07-16 FDB707 - Jul 16, 09:35 UTCJul 16, 12:49 UTC3h 15m
2026-07-15 FDB9JZ - Jul 15, 13:55 UTCJul 15, 23:05 UTC9h 10m
2026-07-15 FDB1550 - Jul 15, 08:15 UTCJul 15, 08:55 UTC40m
2026-07-15 FDB1549 - Jul 15, 03:30 UTCJul 15, 06:20 UTC2h 50m
2026-07-14 FDB71T - Jul 14, 13:05 UTCJul 14, 16:45 UTC3h 40m
2026-07-14 FDB3WJ - Jul 14, 07:50 UTCJul 14, 08:45 UTC55m
2026-07-13 FDB20 - Jul 13, 19:45 UTCJul 13, 20:35 UTC50m
2026-07-13 FDB2KF - Jul 13, 17:30 UTCJul 13, 18:15 UTC45m
2026-07-13 FDB75L - Jul 13, 12:45 UTCJul 13, 13:40 UTC55m
2026-07-13 FDB15L - Jul 13, 10:40 UTCJul 13, 11:25 UTC45m
2026-07-12 FDB868 - Jul 12, 17:10 UTCJul 12, 18:10 UTC1h 0m
2026-07-12 FDB867 - Jul 12, 14:25 UTCJul 12, 15:20 UTC55m
2026-07-12 FDB1636 - Jul 12, 08:45 UTCJul 12, 09:25 UTC40m
2026-07-12 FDB1635 - Jul 12, 04:15 UTCJul 12, 07:05 UTC2h 50m
2026-07-11 FDB43F - Jul 11, 15:55 UTCJul 11, 21:05 UTC5h 10m
2026-07-11 FDB75L - Jul 11, 12:45 UTCJul 11, 13:35 UTC50m
2026-07-11 FDB15L - Jul 11, 10:45 UTCJul 11, 11:30 UTC45m
2026-07-10 FDB793 - Jul 10, 19:15 UTCJul 11, 03:55 UTC8h 41m
2026-07-10 FDB3HP - Jul 10, 09:40 UTCJul 10, 15:40 UTC6h 0m
2026-07-09 FDB7KL AMM → DXB Jul 9, 19:50 UTCJul 9, 22:30 UTC2h 40m
2026-07-09 FDB143 - Jul 9, 15:25 UTCJul 9, 18:10 UTC2h 45m
2026-07-09 FDB2RK - Jul 9, 03:45 UTCJul 9, 13:55 UTC10h 10m
2026-07-08 FDB71T - Jul 8, 13:20 UTCJul 8, 17:55 UTC4h 35m
2026-07-08 FDB2WK - Jul 8, 08:00 UTCJul 8, 11:50 UTC3h 50m
2026-07-07 FDB75L - Jul 7, 13:00 UTCJul 7, 14:00 UTC1h 0m
2026-07-07 FDB15L - Jul 7, 10:40 UTCJul 7, 11:25 UTC45m
2026-07-06 FDB920 - Jul 6, 22:05 UTCJul 7, 04:50 UTC6h 45m
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

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 25d 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, FDB75L, FDB756, FDB733, FDB3VG.