sensors Mode-S transponder
0C4153
ICAO 24-bit transponder address · allocated to Dominican Republic
Currently assigned to HI1045 · CESSNA 525B Citation CJ3
- Hex
- 0C4153
- Octal
- 03040523
- Decimal
- 803,155
- Country
- DO
- Tail
- HI1045
- Type
- C25B
- Flights observed
- 53
- Distinct callsigns
- 1
- Country
- DO
- Last broadcast
- 2h ago
Last known position
Country allocation
The ICAO 24-bit address 0C4153 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 1 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| HI1045 | - | 53 | 2026-06-02 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | HI1045 | - | Jun 2, 13:55 UTC | Jun 2, 16:30 UTC | 2h 35m |
| 2026-06-01 | HI1045 | - | Jun 1, 20:00 UTC | Jun 1, 23:05 UTC | 3h 5m |
| 2026-06-01 | HI1045 | - | Jun 1, 16:50 UTC | Jun 1, 17:20 UTC | 30m |
| 2026-05-21 | HI1045 | - | May 21, 03:25 UTC | May 21, 05:25 UTC | 2h 0m |
| 2026-05-20 | HI1045 | - | May 20, 21:15 UTC | May 21, 00:05 UTC | 2h 50m |
| 2026-05-20 | HI1045 | - | May 20, 00:45 UTC | May 20, 00:55 UTC | 10m |
| 2026-05-17 | HI1045 | - | May 17, 13:50 UTC | May 17, 15:25 UTC | 1h 35m |
| 2026-05-15 | HI1045 | - | May 15, 14:45 UTC | May 15, 17:35 UTC | 2h 49m |
| 2026-05-15 | HI1045 | - | May 15, 12:50 UTC | May 15, 13:05 UTC | 15m |
| 2026-05-15 | HI1045 | - | May 15, 02:10 UTC | May 15, 03:50 UTC | 1h 40m |
| 2026-05-14 | HI1045 | - | May 14, 19:00 UTC | May 15, 00:25 UTC | 5h 25m |
| 2026-05-13 | HI1045 | - | May 13, 23:40 UTC | May 14, 19:30 UTC | 19h 50m |
| 2026-05-12 | HI1045 | - | May 12, 20:50 UTC | May 13, 14:00 UTC | 17h 10m |
| 2026-05-12 | HI1045 | - | May 12, 11:30 UTC | May 12, 21:01 UTC | 9h 30m |
| 2026-05-11 | HI1045 | - | May 11, 19:05 UTC | May 12, 11:55 UTC | 16h 50m |
| 2026-05-10 | HI1045 | - | May 10, 18:35 UTC | May 10, 20:30 UTC | 1h 55m |
| 2026-05-09 | HI1045 | - | May 9, 16:50 UTC | May 9, 18:20 UTC | 1h 30m |
| 2026-05-09 | HI1045 | - | May 9, 12:45 UTC | May 9, 14:40 UTC | 1h 55m |
| 2026-05-08 | HI1045 | - | May 8, 17:45 UTC | May 8, 18:00 UTC | 15m |
| 2026-05-08 | HI1045 | - | May 8, 16:50 UTC | May 8, 17:05 UTC | 15m |
| 2026-05-08 | HI1045 | - | May 8, 12:04 UTC | May 8, 12:20 UTC | 15m |
| 2026-05-08 | HI1045 | - | May 8, 10:49 UTC | May 8, 10:59 UTC | 10m |
| 2026-05-07 | HI1045 | - | May 7, 16:50 UTC | May 7, 17:05 UTC | 15m |
| 2026-05-05 | HI1045 | - | May 5, 22:45 UTC | May 5, 23:00 UTC | 15m |
| 2026-05-05 | HI1045 | - | May 5, 17:50 UTC | May 5, 18:00 UTC | 10m |
| 2026-05-04 | HI1045 | - | May 4, 19:05 UTC | May 5, 04:10 UTC | 9h 5m |
| 2026-05-04 | HI1045 | - | May 4, 16:00 UTC | May 4, 16:20 UTC | 20m |
| 2026-05-03 | HI1045 | - | May 3, 18:09 UTC | May 4, 16:20 UTC | 22h 10m |
| 2026-05-03 | HI1045 | - | May 3, 15:35 UTC | May 3, 16:40 UTC | 1h 5m |
| 2026-05-02 | HI1045 | - | May 2, 16:50 UTC | May 3, 16:40 UTC | 23h 49m |
| 2026-05-02 | HI1045 | - | May 2, 15:15 UTC | May 2, 17:05 UTC | 1h 50m |
| 2026-05-01 | HI1045 | - | May 1, 20:15 UTC | May 2, 01:20 UTC | 5h 5m |
| 2026-04-30 | HI1045 | - | Apr 30, 16:50 UTC | Apr 30, 22:05 UTC | 5h 15m |
| 2026-04-30 | HI1045 | - | Apr 30, 15:25 UTC | Apr 30, 15:35 UTC | 10m |
| 2026-04-30 | HI1045 | - | Apr 30, 05:40 UTC | Apr 30, 05:50 UTC | 10m |
| 2026-04-29 | HI1045 | - | Apr 29, 22:00 UTC | Apr 30, 05:00 UTC | 6h 59m |
| 2026-04-29 | HI1045 | - | Apr 29, 00:45 UTC | Apr 29, 00:54 UTC | 10m |
| 2026-04-25 | HI1045 | - | Apr 25, 15:30 UTC | Apr 25, 22:25 UTC | 6h 55m |
| 2026-04-22 | HI1045 | - | Apr 22, 23:40 UTC | Apr 23, 00:20 UTC | 40m |
| 2026-04-22 | HI1045 | - | Apr 22, 21:40 UTC | Apr 22, 21:50 UTC | 10m |
| 2026-04-21 | HI1045 | - | Apr 21, 22:35 UTC | Apr 22, 00:05 UTC | 1h 30m |
| 2026-04-19 | HI1045 | - | Apr 19, 23:40 UTC | Apr 20, 00:00 UTC | 20m |
| 2026-04-19 | HI1045 | - | Apr 19, 03:30 UTC | Apr 19, 22:15 UTC | 18h 45m |
| 2026-04-18 | HI1045 | - | Apr 18, 15:05 UTC | Apr 19, 01:10 UTC | 10h 5m |
| 2026-04-17 | HI1045 | - | Apr 17, 22:10 UTC | Apr 17, 23:10 UTC | 1h 0m |
| 2026-04-17 | HI1045 | - | Apr 17, 20:25 UTC | Apr 18, 11:55 UTC | 15h 31m |
| 2026-04-17 | HI1045 | - | Apr 17, 18:10 UTC | Apr 17, 18:55 UTC | 45m |
| 2026-04-17 | HI1045 | - | Apr 17, 16:45 UTC | Apr 17, 17:00 UTC | 15m |
| 2026-04-16 | HI1045 | - | Apr 16, 23:35 UTC | Apr 17, 00:05 UTC | 30m |
| 2026-04-14 | HI1045 | - | Apr 14, 21:35 UTC | Apr 14, 22:00 UTC | 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.
Prefer a tail-number view? See the HI1045 page for operator, model, and routing details .