sensors Mode-S transponder

896515

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

Currently assigned to A6-FNB · BOEING 737 MAX 9

Hex
896515
Octal
42262425
Decimal
9,004,309
Country
AE
Tail
A6-FNB
Type
B39M
No current signal · last broadcast 2h ago
Flights observed
222
Distinct callsigns
20
Country
AE
Last broadcast
2h ago

Last known position

Most recent position reported by Mode-S 896515.

Country allocation

The ICAO 24-bit address 896515 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
FDB856 - 24 2026-07-13
FDB1126 - 24 2026-07-09
FDB846 - 21 2026-07-09
FDB1125 - 18 2026-07-09
FDB848 - 16 2026-07-12
FDB842 - 14 2026-07-13
FDB855 - 9 2026-07-02
FDB841 - 9 2026-06-18
FDB847 - 8 2026-07-14
FDB868 Fly Dubai 5 2026-07-03
FDB845 - 5 2026-07-03
FDB1815 Fly Dubai 4 2026-06-21
FDB1082 Fly Dubai 4 2026-05-28
FDB867 - 3 2026-07-03
FDB7RC Fly Dubai 3 2026-06-21
FDB2FL Fly Dubai 3 2026-04-16
FDB1550 Fly Dubai 3 2026-06-07
FDB884 Fly Dubai 2 2026-04-17
FDB869 Fly Dubai 2 2026-04-18
FDB864 Fly Dubai 2 2026-04-14

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-14 FDB847 - Jul 14, 04:00 UTCJul 14, 04:50 UTC50m
2026-07-13 FDB856 - Jul 13, 15:20 UTCJul 13, 20:10 UTC4h 50m
2026-07-13 FDB842 - Jul 13, 07:40 UTCJul 13, 12:20 UTC4h 40m
2026-07-12 FDB856 - Jul 12, 15:15 UTCJul 12, 20:05 UTC4h 50m
2026-07-12 FDB75L - Jul 12, 12:50 UTCJul 12, 13:45 UTC55m
2026-07-12 FDB15L - Jul 12, 11:10 UTCJul 12, 11:30 UTC20m
2026-07-12 FDB848 - Jul 12, 04:01 UTCJul 12, 08:50 UTC4h 50m
2026-07-11 FDB856 - Jul 11, 15:10 UTCJul 11, 20:15 UTC5h 5m
2026-07-11 FDB842 - Jul 11, 07:20 UTCJul 11, 11:55 UTC4h 35m
2026-07-10 FDB856 - Jul 10, 15:25 UTCJul 10, 20:15 UTC4h 50m
2026-07-10 FDB842 - Jul 10, 08:25 UTCJul 10, 12:20 UTC3h 55m
2026-07-09 FDB846 - Jul 9, 21:00 UTCJul 10, 01:20 UTC4h 20m
2026-07-09 FDB1126 - Jul 9, 15:10 UTCJul 9, 18:05 UTC2h 55m
2026-07-09 FDB1125 - Jul 9, 09:55 UTCJul 9, 12:50 UTC2h 55m
2026-07-09 FDB3UF MCT → DXB Jul 9, 05:35 UTCJul 9, 05:50 UTC15m
2026-07-08 FDB856 - Jul 8, 15:10 UTCJul 8, 21:00 UTC5h 50m
2026-07-08 FDB848 - Jul 8, 04:05 UTCJul 8, 08:50 UTC4h 45m
2026-07-07 FDB1626 - Jul 7, 17:05 UTCJul 7, 19:55 UTC2h 50m
2026-07-07 FDB1625 DXB → TLV Jul 7, 12:20 UTCJul 7, 15:15 UTC2h 55m
2026-07-07 FDB848 - Jul 7, 04:25 UTCJul 7, 09:10 UTC4h 45m
2026-07-06 FDB856 RUH → DXB Jul 6, 15:20 UTCJul 6, 20:00 UTC4h 40m
2026-07-06 FDB842 - Jul 6, 07:25 UTCJul 6, 12:05 UTC4h 40m
2026-07-05 FDB856 RUH → DXB Jul 5, 15:15 UTCJul 5, 20:05 UTC4h 50m
2026-07-05 FDB848 - Jul 5, 03:55 UTCJul 5, 08:45 UTC4h 50m
2026-07-04 FDB1626 TLV → DXB Jul 4, 17:00 UTCJul 4, 19:55 UTC2h 55m
2026-07-04 FDB1625 - Jul 4, 11:55 UTCJul 4, 14:55 UTC3h 0m
2026-07-04 FDB848 - Jul 4, 04:05 UTCJul 4, 08:35 UTC4h 30m
2026-07-03 FDB846 - Jul 3, 23:55 UTCJul 4, 01:00 UTC1h 5m
2026-07-03 FDB845 - Jul 3, 20:20 UTCJul 3, 21:10 UTC50m
2026-07-03 FDB868 DMM → DXB Jul 3, 17:00 UTCJul 3, 18:00 UTC1h 0m
2026-07-03 FDB867 - Jul 3, 14:25 UTCJul 3, 15:20 UTC55m
2026-07-03 FDB7UE - Jul 3, 10:55 UTCJul 3, 12:00 UTC1h 5m
2026-07-03 FDB59G - Jul 3, 03:20 UTCJul 3, 06:35 UTC3h 15m
2026-07-02 FDB855 - Jul 2, 15:30 UTCJul 2, 20:15 UTC4h 45m
2026-07-02 FDB842 - Jul 2, 07:55 UTCJul 2, 12:50 UTC4h 55m
2026-06-30 FDB856 RUH → DXB Jun 30, 15:10 UTCJun 30, 20:20 UTC5h 10m
2026-06-30 FDB848 - Jun 30, 03:50 UTCJun 30, 08:45 UTC4h 55m
2026-06-29 FDB846 - Jun 29, 20:19 UTCJun 30, 01:14 UTC4h 55m
2026-06-29 FDB59J - Jun 29, 15:49 UTCJun 29, 16:39 UTC50m
2026-06-29 FDB5AY DXB → BAH Jun 29, 13:34 UTCJun 29, 14:19 UTC45m
2026-06-29 FDB848 - Jun 29, 03:49 UTCJun 29, 08:29 UTC4h 40m
2026-06-28 FDB1054 - Jun 28, 21:59 UTCJun 28, 23:04 UTC1h 5m
2026-06-28 FDB1054 - Jun 28, 20:14 UTCJun 28, 20:34 UTC20m
2026-06-28 FDB1053 - Jun 28, 15:34 UTCJun 28, 18:34 UTC3h 0m
2026-06-28 FDB842 - Jun 28, 08:00 UTCJun 28, 12:44 UTC4h 45m
2026-06-27 FDB842 - Jun 27, 07:30 UTCJun 27, 12:04 UTC4h 35m
2026-06-26 FDB856 RUH → DXB Jun 26, 15:39 UTCJun 26, 20:15 UTC4h 35m
2026-06-26 FDB842 - Jun 26, 07:14 UTCJun 26, 12:00 UTC4h 45m
2026-06-25 FDB846 - Jun 25, 20:14 UTCJun 26, 01:05 UTC4h 50m
2026-06-25 FDB1126 - Jun 25, 16:45 UTCJun 25, 17:49 UTC1h 5m

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

Mode-S 896515 frequently asked

What is Mode-S code 896515?
896515 is an ICAO 24-bit transponder address. Allocated to United Arab Emirates. Assigned to A6-FNB.
Where is Mode-S 896515 registered?
Mode-S code 896515 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 896515 broadcasting right now?
No active broadcast right now. Last signal was 2h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 896515, octal 42262425, decimal 9,004,309.
What flights does 896515 operate?
Mode-S 896515 has broadcast 20 distinct callsigns, including FDB856, FDB1126, FDB846, FDB1125, FDB848.