sensors Mode-S transponder
8940C0
ICAO 24-bit transponder address · allocated to Bahrain
Currently assigned to A9C-BHR · GULFSTREAM G600 · operated by Bahrain Royal Flight
- Hex
- 8940C0
- Octal
- 42240300
- Decimal
- 8,995,008
- Country
- BH
- Tail
- A9C-BHR
- Type
- GA6C
- Flights observed
- 49
- Distinct callsigns
- 1
- Country
- BH
- Last broadcast
- 6h ago
Last known position
Country allocation
The ICAO 24-bit address 8940C0 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 1 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| BAH16 | - | 49 | 2026-07-26 |
Recent flights last 49
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | BAH16 | - | Jul 26, 17:00 UTC | Jul 26, 17:20 UTC | 20m |
| 2026-07-26 | BAH16 | - | Jul 26, 10:50 UTC | Jul 26, 14:55 UTC | 4h 5m |
| 2026-07-22 | BAH16 | - | Jul 22, 13:35 UTC | Jul 22, 18:35 UTC | 5h 0m |
| 2026-07-21 | BAH16 | - | Jul 21, 16:30 UTC | Jul 21, 16:50 UTC | 20m |
| 2026-07-21 | BAH16 | - | Jul 21, 14:40 UTC | Jul 21, 15:15 UTC | 35m |
| 2026-07-21 | BAH16 | - | Jul 21, 07:05 UTC | Jul 21, 09:00 UTC | 1h 55m |
| 2026-07-20 | BAH16 | - | Jul 20, 15:20 UTC | Jul 20, 16:05 UTC | 45m |
| 2026-07-20 | BAH16 | - | Jul 20, 10:00 UTC | Jul 20, 12:55 UTC | 2h 55m |
| 2026-07-19 | BAH16 | - | Jul 19, 09:30 UTC | Jul 19, 13:10 UTC | 3h 40m |
| 2026-07-15 | BAH16 | - | Jul 15, 16:35 UTC | Jul 15, 16:55 UTC | 20m |
| 2026-07-15 | BAH16 | - | Jul 15, 10:15 UTC | Jul 15, 14:40 UTC | 4h 25m |
| 2026-06-25 | BAH16 | - | Jun 25, 16:45 UTC | Jun 25, 17:34 UTC | 50m |
| 2026-06-25 | BAH16 | - | Jun 25, 14:14 UTC | Jun 25, 15:40 UTC | 1h 25m |
| 2026-06-25 | BAH16 | - | Jun 25, 07:25 UTC | Jun 25, 13:00 UTC | 5h 35m |
| 2026-06-19 | BAH16 | - | Jun 19, 02:09 UTC | Jun 19, 02:24 UTC | 15m |
| 2026-06-18 | BAH16 | - | Jun 18, 19:55 UTC | Jun 19, 00:05 UTC | 4h 10m |
| 2026-06-16 | BAH16 | - | Jun 16, 12:30 UTC | Jun 16, 12:55 UTC | 25m |
| 2026-06-15 | BAH16 | - | Jun 15, 03:24 UTC | Jun 15, 10:24 UTC | 7h 0m |
| 2026-06-14 | BAH16 | - | Jun 14, 14:55 UTC | Jun 14, 15:15 UTC | 20m |
| 2026-06-14 | BAH16 | - | Jun 14, 09:20 UTC | Jun 14, 12:55 UTC | 3h 35m |
| 2026-06-10 | BAH16 | - | Jun 10, 15:00 UTC | Jun 10, 15:50 UTC | 50m |
| 2026-06-07 | BAH16 | BAH → FAB | Jun 7, 09:05 UTC | Jun 7, 16:05 UTC | 7h 0m |
| 2026-06-06 | BAH16 | - | Jun 6, 21:30 UTC | Jun 6, 21:54 UTC | 25m |
| 2026-06-06 | BAH16 | - | Jun 6, 15:25 UTC | Jun 6, 19:34 UTC | 4h 10m |
| 2026-06-05 | BAH16 | BAH → FAB | Jun 5, 07:35 UTC | Jun 5, 14:25 UTC | 6h 50m |
| 2026-06-03 | BAH16 | - | Jun 3, 17:20 UTC | Jun 3, 17:30 UTC | 10m |
| 2026-06-03 | BAH16 | - | Jun 3, 11:05 UTC | Jun 3, 15:15 UTC | 4h 10m |
| 2026-06-01 | BAH16 | NCE → FAB | Jun 1, 18:10 UTC | Jun 1, 19:50 UTC | 1h 40m |
| 2026-06-01 | BAH16 | - | Jun 1, 11:20 UTC | Jun 1, 17:10 UTC | 5h 50m |
| 2026-05-31 | BAH16 | - | May 31, 22:15 UTC | May 31, 22:40 UTC | 25m |
| 2026-05-31 | BAH16 | - | May 31, 16:50 UTC | May 31, 20:25 UTC | 3h 35m |
| 2026-05-31 | BAH16 | - | May 31, 12:10 UTC | May 31, 14:45 UTC | 2h 35m |
| 2026-05-28 | BAH16 | - | May 28, 16:00 UTC | May 28, 18:25 UTC | 2h 25m |
| 2026-05-28 | BAH16 | - | May 28, 09:45 UTC | May 28, 14:35 UTC | 4h 50m |
| 2026-05-26 | BAH16 | - | May 26, 14:09 UTC | May 26, 14:20 UTC | 10m |
| 2026-05-26 | BAH16 | - | May 26, 08:15 UTC | May 26, 12:10 UTC | 3h 55m |
| 2026-05-25 | BAH16 | - | May 25, 09:35 UTC | May 25, 13:45 UTC | 4h 10m |
| 2026-05-19 | BAH16 | - | May 19, 06:05 UTC | May 19, 06:30 UTC | 25m |
| 2026-05-18 | BAH16 | - | May 18, 13:00 UTC | May 18, 13:10 UTC | 10m |
| 2026-05-18 | BAH16 | - | May 18, 10:55 UTC | May 18, 11:25 UTC | 30m |
| 2026-05-17 | BAH16 | - | May 17, 10:10 UTC | May 17, 13:35 UTC | 3h 25m |
| 2026-05-13 | BAH16 | - | May 13, 06:50 UTC | May 13, 14:10 UTC | 7h 20m |
| 2026-05-02 | BAH16 | - | May 2, 10:30 UTC | May 2, 13:25 UTC | 2h 55m |
| 2026-05-01 | BAH16 | - | May 1, 07:15 UTC | May 1, 14:25 UTC | 7h 10m |
| 2026-04-27 | BAH16 | - | Apr 27, 15:50 UTC | Apr 27, 16:10 UTC | 20m |
| 2026-04-27 | BAH16 | - | Apr 27, 11:10 UTC | Apr 27, 13:55 UTC | 2h 45m |
| 2026-04-26 | BAH16 | BAH → NCE | Apr 26, 06:50 UTC | Apr 26, 13:00 UTC | 6h 10m |
| 2026-04-15 | BAH16 | - | Apr 15, 11:00 UTC | Apr 15, 12:15 UTC | 1h 15m |
| 2026-04-15 | BAH16 | - | Apr 15, 09:00 UTC | Apr 15, 10:55 UTC | 1h 55m |
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-BHR page for operator, model, and routing details .