sensors Mode-S transponder
0C43B9
ICAO 24-bit transponder address · allocated to Dominican Republic
- Hex
- 0C43B9
- Octal
- 03041671
- Decimal
- 803,769
- Country
- DO
- Flights observed
- 37
- Distinct callsigns
- 13
- Country
- DO
- Last broadcast
- 2h ago
Last known position
Country allocation
The ICAO 24-bit address 0C43B9 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 13 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| DWI5974 | - | 6 | 2026-06-18 |
| DWI6021 | - | 4 | 2026-06-16 |
| BOE123 | - | 4 | 2026-05-01 |
| DWI6087 | - | 3 | 2026-06-14 |
| DWI6086 | - | 3 | 2026-06-13 |
| DWI6020 | - | 3 | 2026-06-15 |
| DWI5862 | - | 3 | 2026-06-16 |
| BOE056 | - | 3 | 2026-05-22 |
| DWI6088 | Arajet | 2 | 2026-06-18 |
| DWI6080 | Arajet | 2 | 2026-06-09 |
| DWI5975 | - | 2 | 2026-06-19 |
| DWI5863 | Arajet | 1 | 2026-06-17 |
| DWI1142 | Arajet | 1 | 2026-05-30 |
Recent flights last 37
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-19 | DWI5975 | - | Jun 19, 11:20 UTC | Jun 19, 23:44 UTC | 12h 25m |
| 2026-06-18 | DWI5974 | - | Jun 18, 15:00 UTC | Jun 19, 04:19 UTC | 13h 19m |
| 2026-06-18 | DWI6088 | PUJ → GRU | Jun 18, 06:45 UTC | Jun 18, 12:05 UTC | 5h 20m |
| 2026-06-17 | DWI6088 | PUJ → GRU | Jun 17, 12:20 UTC | Jun 18, 12:05 UTC | 23h 45m |
| 2026-06-17 | DWI5863 | YYZ → PUJ | Jun 17, 10:50 UTC | Jun 18, 10:15 UTC | 23h 25m |
| 2026-06-16 | DWI5862 | - | Jun 16, 08:39 UTC | Jun 17, 03:50 UTC | 19h 11m |
| 2026-06-16 | DWI5862 | - | Jun 16, 06:20 UTC | Jun 17, 03:50 UTC | 21h 31m |
| 2026-06-16 | DWI6021 | - | Jun 16, 04:20 UTC | Jun 17, 03:50 UTC | 23h 31m |
| 2026-06-15 | DWI6020 | - | Jun 15, 11:10 UTC | Jun 16, 01:40 UTC | 14h 30m |
| 2026-06-14 | DWI6087 | - | Jun 14, 08:20 UTC | Jun 15, 03:40 UTC | 19h 19m |
| 2026-06-14 | DWI6087 | - | Jun 14, 07:50 UTC | Jun 15, 03:40 UTC | 19h 50m |
| 2026-06-13 | DWI6086 | - | Jun 13, 17:45 UTC | Jun 14, 06:05 UTC | 12h 20m |
| 2026-06-13 | DWI6021 | - | Jun 13, 03:25 UTC | Jun 13, 16:05 UTC | 12h 39m |
| 2026-06-12 | DWI6020 | PUJ → GRU | Jun 12, 11:20 UTC | Jun 13, 01:20 UTC | 14h 0m |
| 2026-06-11 | DWI5974 | PUJ → YUL | Jun 11, 09:05 UTC | Jun 12, 04:10 UTC | 19h 6m |
| 2026-06-11 | DWI5974 | PUJ → YUL | Jun 11, 06:20 UTC | Jun 12, 04:10 UTC | 21h 51m |
| 2026-06-11 | DWI6021 | - | Jun 11, 04:20 UTC | Jun 12, 04:10 UTC | 23h 51m |
| 2026-06-10 | DWI6020 | PUJ → GRU | Jun 10, 10:55 UTC | Jun 11, 01:20 UTC | 14h 25m |
| 2026-06-09 | DWI5862 | PUJ → YYZ | Jun 9, 14:20 UTC | Jun 10, 04:10 UTC | 13h 50m |
| 2026-06-09 | DWI6080 | PUJ → GRU | Jun 9, 06:10 UTC | Jun 9, 11:15 UTC | 5h 5m |
| 2026-06-08 | DWI6080 | PUJ → GRU | Jun 8, 12:20 UTC | Jun 9, 11:15 UTC | 22h 55m |
| 2026-06-08 | DWI5975 | YUL → PUJ | Jun 8, 11:15 UTC | Jun 9, 09:50 UTC | 22h 35m |
| 2026-06-07 | DWI5974 | PUJ → YUL | Jun 7, 12:25 UTC | Jun 8, 05:10 UTC | 16h 45m |
| 2026-06-07 | DWI5974 | PUJ → YUL | Jun 7, 08:20 UTC | Jun 8, 05:10 UTC | 20h 50m |
| 2026-06-07 | DWI5974 | PUJ → YUL | Jun 7, 07:50 UTC | Jun 8, 05:10 UTC | 21h 20m |
| 2026-06-06 | DWI6086 | PUJ → GRU | Jun 6, 18:29 UTC | Jun 7, 06:15 UTC | 11h 45m |
| 2026-06-06 | DWI6021 | - | Jun 6, 03:20 UTC | Jun 6, 16:24 UTC | 13h 5m |
| 2026-06-05 | DWI6087 | GRU → PUJ | Jun 5, 07:45 UTC | Jun 6, 01:25 UTC | 17h 40m |
| 2026-06-05 | DWI6086 | PUJ → GRU | Jun 5, 00:55 UTC | Jun 5, 06:00 UTC | 5h 5m |
| 2026-05-30 | DWI1142 | PAE → STI | May 30, 09:20 UTC | May 30, 14:55 UTC | 5h 35m |
| 2026-05-22 | BOE056 | - | May 22, 16:40 UTC | May 22, 18:45 UTC | 2h 5m |
| 2026-05-15 | BOE056 | - | May 15, 19:45 UTC | May 15, 22:05 UTC | 2h 20m |
| 2026-05-05 | BOE056 | - | May 5, 18:50 UTC | May 5, 21:55 UTC | 3h 5m |
| 2026-05-01 | BOE123 | RNT → RNT | May 1, 04:00 UTC | May 1, 04:10 UTC | 10m |
| 2026-05-01 | BOE123 | RNT → RNT | May 1, 03:40 UTC | May 1, 03:55 UTC | 15m |
| 2026-05-01 | BOE123 | RNT → RNT | May 1, 03:15 UTC | May 1, 03:35 UTC | 20m |
| 2026-05-01 | BOE123 | RNT → RNT | May 1, 02:55 UTC | May 1, 03:05 UTC | 10m |
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.