sensors Mode-S transponder
8940CC
ICAO 24-bit transponder address · allocated to Bahrain
Currently assigned to A9C-DHAA · BOEING 767-300
- Hex
- 8940CC
- Octal
- 42240314
- Decimal
- 8,995,020
- Country
- BH
- Tail
- A9C-DHAA
- Type
- B763
- Flights observed
- 71
- Distinct callsigns
- 20
- Country
- BH
- Last broadcast
- 17d ago
Last known position
Country allocation
The ICAO 24-bit address 8940CC falls within the block assigned to Bahrain (BH) by ICAO Annex 10, Volume III. Every aircraft registered in Bahrain 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 |
|---|---|---|---|
| DHX856 | - | 10 | 2026-05-02 |
| DHX865 | - | 9 | 2026-05-08 |
| DHX832 | DHL International | 4 | 2026-04-27 |
| DHX820 | - | 4 | 2026-05-02 |
| DHX821 | DHL International | 3 | 2026-04-16 |
| DHX810 | - | 3 | 2026-04-26 |
| DHX696 | DHL International | 3 | 2026-05-10 |
| DHX112 | - | 3 | 2026-05-11 |
| DHX867 | - | 2 | 2026-04-14 |
| DHX836 | - | 2 | 2026-04-22 |
| DHX811 | - | 2 | 2026-04-25 |
| DHX803 | - | 2 | 2026-04-29 |
| DHX729 | - | 2 | 2026-05-05 |
| DHX728 | DHL International | 2 | 2026-05-06 |
| DHX721 | DHL International | 2 | 2026-05-04 |
| DHX720 | DHL International | 2 | 2026-05-05 |
| DHX202 | DHL International | 2 | 2026-04-29 |
| DHX171 | - | 2 | 2026-05-11 |
| DHX878 | - | 1 | 2026-04-29 |
| DHX877 | - | 1 | 2026-04-30 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-12 | DHX723 | - | May 12, 11:30 UTC | May 12, 17:15 UTC | 5h 45m |
| 2026-05-11 | DHX171 | - | May 11, 15:25 UTC | May 11, 15:40 UTC | 15m |
| 2026-05-11 | DHX113 | - | May 11, 04:10 UTC | May 11, 04:30 UTC | 20m |
| 2026-05-11 | DHX112 | - | May 11, 00:54 UTC | May 11, 01:10 UTC | 15m |
| 2026-05-10 | DHX696 | HKG → BAH | May 10, 16:00 UTC | May 10, 16:10 UTC | 10m |
| 2026-05-10 | DHX696 | HKG → BAH | May 10, 09:50 UTC | May 10, 14:04 UTC | 4h 15m |
| 2026-05-10 | DHX696 | HKG → BAH | May 10, 07:45 UTC | May 10, 08:00 UTC | 15m |
| 2026-05-09 | DHX835 | - | May 9, 13:05 UTC | May 9, 23:50 UTC | 10h 45m |
| 2026-05-09 | DHX171 | - | May 9, 11:15 UTC | May 9, 11:35 UTC | 20m |
| 2026-05-09 | DHX172 | - | May 9, 08:15 UTC | May 9, 08:25 UTC | 10m |
| 2026-05-08 | DHX865 | - | May 8, 04:44 UTC | May 8, 08:19 UTC | 3h 35m |
| 2026-05-07 | DHX758 | LEJ → BAH | May 7, 18:55 UTC | May 7, 23:09 UTC | 4h 14m |
| 2026-05-07 | DHX510 | - | May 7, 14:35 UTC | May 7, 14:55 UTC | 20m |
| 2026-05-06 | DHX511 | - | May 6, 18:50 UTC | May 7, 10:55 UTC | 16h 5m |
| 2026-05-06 | DHX265 | BAH → DXB | May 6, 07:20 UTC | May 7, 05:35 UTC | 22h 14m |
| 2026-05-06 | DHX728 | HKG → HKG | May 6, 01:15 UTC | May 6, 19:20 UTC | 18h 4m |
| 2026-05-05 | DHX728 | HKG → HKG | May 5, 23:05 UTC | May 5, 23:15 UTC | 10m |
| 2026-05-05 | DHX729 | - | May 5, 20:25 UTC | May 5, 20:35 UTC | 10m |
| 2026-05-05 | DHX729 | - | May 5, 12:10 UTC | May 5, 18:40 UTC | 6h 30m |
| 2026-05-05 | DHX720 | HKG → HKG | May 5, 08:20 UTC | May 5, 08:40 UTC | 20m |
| 2026-05-04 | DHX720 | HKG → HKG | May 4, 22:55 UTC | May 5, 07:30 UTC | 8h 35m |
| 2026-05-04 | DHX721 | BAH → HKG | May 4, 19:55 UTC | May 4, 20:00 UTC | 5m |
| 2026-05-04 | DHX721 | BAH → HKG | May 4, 11:45 UTC | May 4, 18:15 UTC | 6h 30m |
| 2026-05-03 | DHX111 | - | May 3, 22:09 UTC | May 3, 22:34 UTC | 25m |
| 2026-05-03 | DHX865 | - | May 3, 14:05 UTC | May 3, 18:00 UTC | 3h 55m |
| 2026-05-02 | DHX856 | - | May 2, 04:20 UTC | May 2, 21:20 UTC | 17h 0m |
| 2026-05-02 | DHX820 | - | May 2, 02:05 UTC | May 2, 02:20 UTC | 15m |
| 2026-05-01 | DHX865 | - | May 1, 05:05 UTC | May 1, 23:05 UTC | 18h 0m |
| 2026-05-01 | DHX865 | - | May 1, 04:10 UTC | May 1, 23:05 UTC | 18h 55m |
| 2026-04-30 | DHX856 | - | Apr 30, 04:45 UTC | Apr 30, 21:30 UTC | 16h 45m |
| 2026-04-30 | DHX877 | - | Apr 30, 00:25 UTC | Apr 30, 00:50 UTC | 25m |
| 2026-04-29 | DHX878 | - | Apr 29, 22:00 UTC | Apr 29, 22:20 UTC | 20m |
| 2026-04-29 | DHX803 | - | Apr 29, 10:50 UTC | Apr 29, 11:45 UTC | 55m |
| 2026-04-29 | DHX112 | - | Apr 29, 07:24 UTC | Apr 29, 07:40 UTC | 15m |
| 2026-04-29 | DHX202 | MCT → BAH | Apr 29, 04:10 UTC | Apr 29, 05:15 UTC | 1h 5m |
| 2026-04-28 | DHX803 | - | Apr 28, 15:20 UTC | Apr 28, 16:25 UTC | 1h 5m |
| 2026-04-28 | DHX112 | - | Apr 28, 11:55 UTC | Apr 28, 12:15 UTC | 20m |
| 2026-04-28 | DHX202 | MCT → BAH | Apr 28, 08:35 UTC | Apr 28, 09:40 UTC | 1h 5m |
| 2026-04-27 | DHX832 | HKG → MCT | Apr 27, 09:05 UTC | Apr 28, 09:00 UTC | 23h 55m |
| 2026-04-27 | DHX832 | HKG → MCT | Apr 27, 06:00 UTC | Apr 27, 06:15 UTC | 15m |
| 2026-04-27 | DHX831 | - | Apr 27, 02:40 UTC | Apr 27, 03:05 UTC | 25m |
| 2026-04-26 | DHX810 | - | Apr 26, 05:15 UTC | Apr 27, 00:30 UTC | 19h 15m |
| 2026-04-26 | DHX810 | - | Apr 26, 04:50 UTC | Apr 27, 00:30 UTC | 19h 40m |
| 2026-04-26 | DHX810 | - | Apr 26, 02:30 UTC | Apr 26, 02:45 UTC | 15m |
| 2026-04-25 | DHX811 | - | Apr 25, 23:35 UTC | Apr 26, 00:00 UTC | 25m |
| 2026-04-25 | DHX832 | HKG → MCT | Apr 25, 05:10 UTC | Apr 25, 21:40 UTC | 16h 30m |
| 2026-04-25 | DHX832 | HKG → MCT | Apr 25, 02:50 UTC | Apr 25, 03:00 UTC | 10m |
| 2026-04-24 | DHX865 | LEJ → HKG | Apr 24, 05:20 UTC | Apr 25, 00:05 UTC | 18h 45m |
| 2026-04-23 | DHX856 | - | Apr 23, 13:55 UTC | Apr 23, 21:20 UTC | 7h 24m |
| 2026-04-22 | DHX836 | - | Apr 22, 06:40 UTC | Apr 22, 22:40 UTC | 16h 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 A9C-DHAA page for operator, model, and routing details .