sensors Mode-S transponder
0C4349
ICAO 24-bit transponder address · allocated to Dominican Republic
Currently assigned to HI1074 · EMBRAER ERJ-190-100
- Hex
- 0C4349
- Octal
- 03041511
- Decimal
- 803,657
- Country
- DO
- Tail
- HI1074
- Type
- E190
- Flights observed
- 137
- Distinct callsigns
- 20
- Country
- DO
- Last broadcast
- 18h ago
Last known position
Country allocation
The ICAO 24-bit address 0C4349 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 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| SHH861 | - | 11 | 2026-07-13 |
| SHH763 | Airshare Holdings | 11 | 2026-06-17 |
| SHH851 | - | 9 | 2026-07-08 |
| SHH780 | Airshare Holdings | 9 | 2026-05-07 |
| SHH905 | - | 7 | 2026-07-06 |
| SHH860 | Airshare Holdings | 7 | 2026-05-24 |
| SHH1919 | - | 6 | 2026-07-12 |
| SHH992 | Airshare Holdings | 5 | 2026-07-07 |
| SHH781 | Airshare Holdings | 5 | 2026-04-22 |
| SHH956 | Airshare Holdings | 4 | 2026-06-30 |
| SHH913 | Airshare Holdings | 4 | 2026-07-03 |
| SHH850 | Airshare Holdings | 4 | 2026-04-20 |
| SHH1923 | - | 4 | 2026-07-12 |
| SHH1917 | Airshare Holdings | 4 | 2026-07-11 |
| SHH993 | - | 3 | 2026-07-07 |
| SHH981 | Airshare Holdings | 3 | 2026-06-15 |
| SHH906 | - | 3 | 2026-06-29 |
| SHH812 | Airshare Holdings | 3 | 2026-07-02 |
| SHH765 | Airshare Holdings | 3 | 2026-06-17 |
| SHH762 | Airshare Holdings | 3 | 2026-06-16 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | SHH861 | - | Jul 13, 22:35 UTC | Jul 13, 22:55 UTC | 20m |
| 2026-07-13 | SHH801 | - | Jul 13, 00:45 UTC | Jul 13, 01:15 UTC | 30m |
| 2026-07-12 | SHH1923 | - | Jul 12, 17:20 UTC | Jul 12, 22:30 UTC | 5h 10m |
| 2026-07-12 | SHH1919 | - | Jul 12, 10:35 UTC | Jul 12, 15:45 UTC | 5h 10m |
| 2026-07-11 | SHH1921 | - | Jul 11, 17:20 UTC | Jul 11, 22:55 UTC | 5h 35m |
| 2026-07-11 | SHH1917 | PUJ → MIA | Jul 11, 13:45 UTC | Jul 11, 15:20 UTC | 1h 35m |
| 2026-07-08 | SHH851 | - | Jul 8, 19:20 UTC | Jul 8, 22:55 UTC | 3h 35m |
| 2026-07-07 | SHH993 | - | Jul 7, 19:20 UTC | Jul 7, 19:45 UTC | 25m |
| 2026-07-07 | SHH992 | SDQ → AXA | Jul 7, 17:05 UTC | Jul 7, 17:30 UTC | 25m |
| 2026-07-06 | SHH905 | - | Jul 6, 00:15 UTC | Jul 6, 01:40 UTC | 1h 25m |
| 2026-07-05 | SHH1923 | - | Jul 5, 22:15 UTC | Jul 5, 22:40 UTC | 25m |
| 2026-07-05 | SHH1922 | MIA → PUJ | Jul 5, 17:15 UTC | Jul 5, 21:15 UTC | 4h 0m |
| 2026-07-05 | SHH1919 | - | Jul 5, 10:20 UTC | Jul 5, 15:35 UTC | 5h 15m |
| 2026-07-04 | SHH1921 | - | Jul 4, 17:20 UTC | Jul 4, 22:45 UTC | 5h 25m |
| 2026-07-04 | SHH1917 | PUJ → MIA | Jul 4, 10:05 UTC | Jul 4, 15:35 UTC | 5h 30m |
| 2026-07-03 | SHH913 | PUJ → MIA | Jul 3, 17:10 UTC | Jul 3, 22:25 UTC | 5h 15m |
| 2026-07-03 | SHH1919 | - | Jul 3, 10:15 UTC | Jul 3, 15:20 UTC | 5h 5m |
| 2026-07-03 | SHH800 | - | Jul 3, 04:30 UTC | Jul 3, 04:55 UTC | 25m |
| 2026-07-02 | SHH812 | SDQ → HAV | Jul 2, 18:05 UTC | Jul 2, 18:20 UTC | 15m |
| 2026-06-30 | SHH956 | SDQ → ANU | Jun 30, 14:25 UTC | Jun 30, 22:30 UTC | 8h 5m |
| 2026-06-29 | SHH956 | SDQ → ANU | Jun 29, 22:19 UTC | Jun 30, 22:15 UTC | 23h 56m |
| 2026-06-29 | SHH956 | SDQ → ANU | Jun 29, 22:05 UTC | Jun 30, 19:50 UTC | 21h 46m |
| 2026-06-29 | SHH906 | - | Jun 29, 00:24 UTC | Jun 29, 19:29 UTC | 19h 5m |
| 2026-06-28 | SHH1923 | - | Jun 28, 17:04 UTC | Jun 28, 22:49 UTC | 5h 45m |
| 2026-06-28 | SHH1919 | - | Jun 28, 10:10 UTC | Jun 28, 15:20 UTC | 5h 10m |
| 2026-06-27 | SHH1920 | MIA → PUJ | Jun 27, 16:59 UTC | Jun 27, 22:45 UTC | 5h 45m |
| 2026-06-27 | SHH1917 | PUJ → MIA | Jun 27, 10:00 UTC | Jun 27, 15:30 UTC | 5h 30m |
| 2026-06-26 | SHH905 | SDQ → MIA | Jun 26, 17:25 UTC | Jun 26, 22:40 UTC | 5h 15m |
| 2026-06-26 | SHH1918 | MIA → PUJ | Jun 26, 10:20 UTC | Jun 26, 15:34 UTC | 5h 15m |
| 2026-06-26 | SHH800 | - | Jun 26, 02:09 UTC | Jun 26, 02:34 UTC | 25m |
| 2026-06-25 | SHH812 | SDQ → HAV | Jun 25, 18:15 UTC | Jun 25, 18:24 UTC | 10m |
| 2026-06-23 | SHH956 | SDQ → ANU | Jun 23, 14:04 UTC | Jun 23, 21:59 UTC | 7h 55m |
| 2026-06-22 | SHH906 | MIA → SDQ | Jun 22, 00:24 UTC | Jun 22, 00:55 UTC | 30m |
| 2026-06-21 | SHH1923 | - | Jun 21, 17:45 UTC | Jun 21, 22:54 UTC | 5h 10m |
| 2026-06-21 | SHH1919 | - | Jun 21, 10:14 UTC | Jun 21, 15:49 UTC | 5h 35m |
| 2026-06-20 | SHH1921 | - | Jun 20, 17:39 UTC | Jun 20, 23:10 UTC | 5h 30m |
| 2026-06-20 | SHH1917 | PUJ → MIA | Jun 20, 09:54 UTC | Jun 20, 15:29 UTC | 5h 35m |
| 2026-06-19 | SHH913 | PUJ → MIA | Jun 19, 16:55 UTC | Jun 19, 22:09 UTC | 5h 15m |
| 2026-06-19 | SHH1916 | MIA → PUJ | Jun 19, 10:04 UTC | Jun 19, 15:29 UTC | 5h 25m |
| 2026-06-18 | SHH905 | SDQ → MIA | Jun 18, 17:45 UTC | Jun 18, 19:30 UTC | 1h 45m |
| 2026-06-17 | SHH765 | GEO → SDQ | Jun 17, 22:55 UTC | Jun 18, 04:10 UTC | 5h 15m |
| 2026-06-17 | SHH763 | GEO → SDQ | Jun 17, 02:35 UTC | Jun 17, 21:25 UTC | 18h 50m |
| 2026-06-17 | SHH763 | GEO → SDQ | Jun 17, 01:10 UTC | Jun 17, 21:25 UTC | 20h 15m |
| 2026-06-16 | SHH763 | GEO → SDQ | Jun 16, 22:55 UTC | Jun 17, 21:25 UTC | 22h 30m |
| 2026-06-16 | SHH762 | SDQ → GEO | Jun 16, 21:50 UTC | Jun 17, 12:40 UTC | 14h 50m |
| 2026-06-16 | SHH762 | SDQ → GEO | Jun 16, 17:45 UTC | Jun 17, 12:40 UTC | 18h 56m |
| 2026-06-15 | SHH851 | FDF → SDQ | Jun 15, 22:15 UTC | Jun 16, 15:50 UTC | 17h 35m |
| 2026-06-15 | SHH851 | FDF → SDQ | Jun 15, 18:55 UTC | Jun 16, 15:50 UTC | 20h 55m |
| 2026-06-15 | SHH981 | SKB → SDQ | Jun 15, 13:25 UTC | Jun 15, 22:35 UTC | 9h 10m |
| 2026-06-14 | SHH981 | SKB → SDQ | Jun 14, 18:20 UTC | Jun 15, 16:15 UTC | 21h 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 HI1074 page for operator, model, and routing details .