sensors Mode-S transponder
0C43BF
ICAO 24-bit transponder address · allocated to Dominican Republic
- Hex
- 0C43BF
- Octal
- 03041677
- Decimal
- 803,775
- Country
- DO
- Flights observed
- 70
- Distinct callsigns
- 16
- Country
- DO
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address 0C43BF falls within the block assigned to Dominican Republic (DO) by ICAO Annex 10, Volume III. Every aircraft registered in Dominican Republic 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 16 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| SHH781 | Airshare Holdings | 19 | 2026-06-22 |
| SHH780 | Airshare Holdings | 14 | 2026-06-22 |
| SHH860 | - | 8 | 2026-06-21 |
| SHH761 | - | 5 | 2026-05-28 |
| SHH980 | Airshare Holdings | 4 | 2026-06-07 |
| SHH851 | Airshare Holdings | 4 | 2026-06-20 |
| SHH956 | Airshare Holdings | 3 | 2026-06-06 |
| SHH816 | - | 3 | 2026-06-19 |
| SHH850 | - | 2 | 2026-06-13 |
| SHH765 | Airshare Holdings | 2 | 2026-06-11 |
| SHH981 | Airshare Holdings | 1 | 2026-06-07 |
| SHH957 | Airshare Holdings | 1 | 2026-06-06 |
| SHH861 | Airshare Holdings | 1 | 2026-05-10 |
| SHH817 | - | 1 | 2026-06-26 |
| SHH812 | Airshare Holdings | 1 | 2026-05-30 |
| SHH649 | - | 1 | 2026-06-23 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-26 | SHH817 | - | Jun 26, 16:39 UTC | Jun 26, 16:54 UTC | 15m |
| 2026-06-23 | SHH649 | - | Jun 23, 12:35 UTC | Jun 24, 04:55 UTC | 16h 20m |
| 2026-06-22 | SHH780 | SDQ → HAV | Jun 22, 18:54 UTC | Jun 23, 14:39 UTC | 19h 45m |
| 2026-06-22 | SHH781 | HAV → GEO | Jun 22, 17:10 UTC | Jun 23, 14:39 UTC | 21h 30m |
| 2026-06-22 | SHH781 | HAV → GEO | Jun 22, 12:30 UTC | Jun 22, 19:24 UTC | 6h 55m |
| 2026-06-21 | SHH781 | HAV → GEO | Jun 21, 23:24 UTC | Jun 22, 19:24 UTC | 20h 0m |
| 2026-06-21 | SHH781 | HAV → GEO | Jun 21, 20:29 UTC | Jun 22, 19:24 UTC | 22h 55m |
| 2026-06-21 | SHH860 | - | Jun 21, 17:05 UTC | Jun 22, 12:34 UTC | 19h 30m |
| 2026-06-21 | SHH860 | - | Jun 21, 12:35 UTC | Jun 21, 23:44 UTC | 11h 10m |
| 2026-06-20 | SHH851 | FDF → SDQ | Jun 20, 23:50 UTC | Jun 21, 20:50 UTC | 21h 0m |
| 2026-06-20 | SHH851 | FDF → SDQ | Jun 20, 20:49 UTC | Jun 21, 17:10 UTC | 20h 20m |
| 2026-06-20 | SHH851 | FDF → SDQ | Jun 20, 17:34 UTC | Jun 21, 12:44 UTC | 19h 10m |
| 2026-06-20 | SHH851 | FDF → SDQ | Jun 20, 12:54 UTC | Jun 21, 00:10 UTC | 11h 15m |
| 2026-06-19 | SHH816 | - | Jun 19, 21:04 UTC | Jun 20, 13:09 UTC | 16h 5m |
| 2026-06-16 | SHH780 | SDQ → HAV | Jun 16, 11:55 UTC | Jun 16, 14:15 UTC | 2h 20m |
| 2026-06-15 | SHH780 | SDQ → HAV | Jun 15, 18:55 UTC | Jun 16, 14:15 UTC | 19h 20m |
| 2026-06-15 | SHH781 | HAV → GEO | Jun 15, 17:15 UTC | Jun 16, 14:15 UTC | 21h 0m |
| 2026-06-15 | SHH781 | HAV → GEO | Jun 15, 12:35 UTC | Jun 15, 19:20 UTC | 6h 45m |
| 2026-06-14 | SHH781 | HAV → GEO | Jun 14, 23:05 UTC | Jun 15, 19:20 UTC | 20h 14m |
| 2026-06-14 | SHH781 | HAV → GEO | Jun 14, 20:25 UTC | Jun 15, 19:20 UTC | 22h 55m |
| 2026-06-14 | SHH860 | SDQ → PTP | Jun 14, 16:30 UTC | Jun 15, 12:45 UTC | 20h 15m |
| 2026-06-14 | SHH860 | SDQ → PTP | Jun 14, 12:05 UTC | Jun 14, 23:25 UTC | 11h 20m |
| 2026-06-14 | SHH860 | SDQ → PTP | Jun 14, 00:15 UTC | Jun 14, 23:25 UTC | 23h 10m |
| 2026-06-13 | SHH850 | - | Jun 13, 21:20 UTC | Jun 14, 16:40 UTC | 19h 20m |
| 2026-06-13 | SHH850 | - | Jun 13, 17:20 UTC | Jun 14, 12:15 UTC | 18h 55m |
| 2026-06-13 | SHH816 | - | Jun 13, 12:35 UTC | Jun 14, 00:30 UTC | 11h 55m |
| 2026-06-12 | SHH816 | - | Jun 12, 16:40 UTC | Jun 13, 12:55 UTC | 20h 14m |
| 2026-06-11 | SHH765 | GEO → SDQ | Jun 11, 23:10 UTC | Jun 12, 16:55 UTC | 17h 46m |
| 2026-06-11 | SHH765 | GEO → SDQ | Jun 11, 20:05 UTC | Jun 12, 16:55 UTC | 20h 50m |
| 2026-06-09 | SHH780 | SDQ → HAV | Jun 9, 12:25 UTC | Jun 9, 19:15 UTC | 6h 50m |
| 2026-06-08 | SHH780 | SDQ → HAV | Jun 8, 19:20 UTC | Jun 9, 14:40 UTC | 19h 20m |
| 2026-06-08 | SHH781 | HAV → GEO | Jun 8, 12:40 UTC | Jun 8, 19:45 UTC | 7h 5m |
| 2026-06-07 | SHH781 | HAV → GEO | Jun 7, 21:50 UTC | Jun 8, 19:45 UTC | 21h 55m |
| 2026-06-07 | SHH860 | SDQ → PTP | Jun 7, 19:10 UTC | Jun 8, 12:50 UTC | 17h 40m |
| 2026-06-07 | SHH981 | SKB → SDQ | Jun 7, 17:05 UTC | Jun 8, 12:50 UTC | 19h 45m |
| 2026-06-07 | SHH980 | SDQ → SKB | Jun 7, 14:15 UTC | Jun 8, 12:50 UTC | 22h 35m |
| 2026-06-06 | SHH980 | SDQ → SKB | Jun 6, 21:50 UTC | Jun 7, 21:45 UTC | 23h 55m |
| 2026-06-06 | SHH980 | SDQ → SKB | Jun 6, 21:44 UTC | Jun 7, 19:30 UTC | 21h 45m |
| 2026-06-06 | SHH980 | SDQ → SKB | Jun 6, 18:39 UTC | Jun 7, 17:30 UTC | 22h 50m |
| 2026-06-06 | SHH957 | ANU → SDQ | Jun 6, 16:10 UTC | Jun 7, 14:40 UTC | 22h 30m |
| 2026-06-06 | SHH956 | SDQ → ANU | Jun 6, 13:39 UTC | Jun 6, 22:05 UTC | 8h 25m |
| 2026-06-05 | SHH956 | SDQ → ANU | Jun 5, 20:10 UTC | Jun 6, 18:59 UTC | 22h 50m |
| 2026-06-05 | SHH956 | SDQ → ANU | Jun 5, 17:50 UTC | Jun 6, 16:34 UTC | 22h 45m |
| 2026-06-05 | SHH860 | SDQ → PTP | Jun 5, 17:30 UTC | Jun 6, 14:09 UTC | 20h 40m |
| 2026-06-05 | SHH860 | SDQ → PTP | Jun 5, 14:50 UTC | Jun 6, 13:44 UTC | 22h 55m |
| 2026-06-03 | SHH781 | HAV → GEO | Jun 3, 12:45 UTC | Jun 3, 22:50 UTC | 10h 5m |
| 2026-06-02 | SHH780 | SDQ → HAV | Jun 2, 12:35 UTC | Jun 2, 14:45 UTC | 2h 10m |
| 2026-06-01 | SHH780 | SDQ → HAV | Jun 1, 18:50 UTC | Jun 2, 14:45 UTC | 19h 55m |
| 2026-06-01 | SHH781 | HAV → GEO | Jun 1, 12:20 UTC | Jun 1, 19:20 UTC | 7h 0m |
| 2026-05-30 | SHH812 | SDQ → HAV | May 30, 12:45 UTC | May 30, 17:10 UTC | 4h 25m |
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.