sensors Mode-S transponder
501DC4
ICAO 24-bit transponder address · allocated to Croatia
Currently assigned to 9A-CQC · DE HAVILLAND DHC-8-400 Dash 8
- Hex
- 501DC4
- Octal
- 24016704
- Decimal
- 5,250,500
- Country
- HR
- Tail
- 9A-CQC
- Type
- DH8D
- Flights observed
- 141
- Distinct callsigns
- 20
- Country
- HR
- Last broadcast
- 24d ago
Last known position
Country allocation
The ICAO 24-bit address 501DC4 falls within the block assigned to Croatia (HR) by ICAO Annex 10, Volume III. Every aircraft registered in Croatia 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 |
|---|---|---|---|
| CTN632 | - | 10 | 2026-05-05 |
| CTN3T | Croatia Airlines | 10 | 2026-05-06 |
| CTN345 | Croatia Airlines | 10 | 2026-05-03 |
| CTN344 | Croatia Airlines | 10 | 2026-05-03 |
| CTN441 | Croatia Airlines | 9 | 2026-05-06 |
| CTN4AT | Croatia Airlines | 8 | 2026-05-06 |
| CTN4W | Croatia Airlines | 7 | 2026-05-01 |
| CTN465 | Croatia Airlines | 6 | 2026-05-02 |
| CTN6CH | Croatia Airlines | 5 | 2026-05-02 |
| CTN442 | Croatia Airlines | 5 | 2026-04-24 |
| CTN5V | Croatia Airlines | 4 | 2026-05-03 |
| CTN4437 | Croatia Airlines | 4 | 2026-05-01 |
| CTN443 | Croatia Airlines | 4 | 2026-04-24 |
| CTN327 | Croatia Airlines | 4 | 2026-05-04 |
| CTN4Z | Croatia Airlines | 3 | 2026-05-01 |
| CTN436R | Croatia Airlines | 3 | 2026-04-29 |
| CTN341 | Croatia Airlines | 3 | 2026-04-25 |
| CTN326 | Croatia Airlines | 3 | 2026-05-03 |
| CTN724D | - | 2 | 2026-04-14 |
| CTN654 | Croatia Airlines | 2 | 2026-04-27 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-06 | CTN441 | VIE → ZAG | May 6, 08:05 UTC | May 6, 08:35 UTC | 30m |
| 2026-05-06 | CTN4AT | ZAG → VIE | May 6, 06:05 UTC | May 6, 06:45 UTC | 40m |
| 2026-05-06 | CTN3T | PUY → ZAG | May 6, 04:55 UTC | May 6, 05:25 UTC | 30m |
| 2026-05-06 | CTN3T | PUY → ZAG | May 6, 04:00 UTC | May 6, 04:10 UTC | 10m |
| 2026-05-05 | CTN632 | - | May 5, 20:35 UTC | May 5, 20:50 UTC | 15m |
| 2026-05-05 | CTN632 | - | May 5, 19:40 UTC | May 5, 19:55 UTC | 15m |
| 2026-05-04 | CTN327 | OMO → ZAG | May 4, 04:15 UTC | May 4, 04:39 UTC | 25m |
| 2026-05-03 | CTN326 | ZAG → OMO | May 3, 21:10 UTC | May 3, 21:39 UTC | 30m |
| 2026-05-03 | CTN5V | SPU → ZAG | May 3, 19:20 UTC | May 3, 19:34 UTC | 15m |
| 2026-05-03 | CTN658 | ZAG → SPU | May 3, 17:54 UTC | May 3, 18:09 UTC | 15m |
| 2026-05-03 | CTN345 | SJJ → ZAG | May 3, 16:20 UTC | May 3, 16:45 UTC | 25m |
| 2026-05-03 | CTN344 | ZAG → SJJ | May 3, 15:15 UTC | May 3, 15:40 UTC | 25m |
| 2026-05-02 | CTN465 | ZRH → ZAG | May 2, 18:15 UTC | May 2, 19:20 UTC | 1h 5m |
| 2026-05-02 | CTN6CH | ZAG → ZRH | May 2, 16:05 UTC | May 2, 17:15 UTC | 1h 10m |
| 2026-05-01 | CTN465 | ZRH → ZAG | May 1, 18:20 UTC | May 1, 19:40 UTC | 1h 20m |
| 2026-05-01 | CTN6CH | ZAG → ZRH | May 1, 16:10 UTC | May 1, 17:25 UTC | 1h 15m |
| 2026-05-01 | CTN4Z | PUY → ZAG | May 1, 14:40 UTC | May 1, 15:05 UTC | 25m |
| 2026-05-01 | CTN4W | ZAG → ZAD | May 1, 13:45 UTC | May 1, 13:55 UTC | 10m |
| 2026-05-01 | CTN4W | ZAG → ZAD | May 1, 12:25 UTC | May 1, 12:55 UTC | 30m |
| 2026-05-01 | CTN4437 | MUC → ZAG | May 1, 08:35 UTC | May 1, 09:25 UTC | 50m |
| 2026-05-01 | CTN4430 | OSI → MUC | May 1, 06:00 UTC | May 1, 07:10 UTC | 1h 10m |
| 2026-04-30 | CTN627 | SPU → OSI | Apr 30, 17:30 UTC | Apr 30, 17:55 UTC | 25m |
| 2026-04-30 | CTN1W | ZAG → SPU | Apr 30, 16:00 UTC | Apr 30, 16:15 UTC | 15m |
| 2026-04-30 | CTN345 | SJJ → ZAG | Apr 30, 14:20 UTC | Apr 30, 14:45 UTC | 25m |
| 2026-04-30 | CTN344 | ZAG → SJJ | Apr 30, 13:00 UTC | Apr 30, 13:20 UTC | 20m |
| 2026-04-30 | CTN441 | VIE → ZAG | Apr 30, 08:00 UTC | Apr 30, 08:30 UTC | 30m |
| 2026-04-30 | CTN4AT | ZAG → VIE | Apr 30, 06:20 UTC | Apr 30, 07:00 UTC | 40m |
| 2026-04-30 | CTN3T | PUY → ZAG | Apr 30, 05:05 UTC | Apr 30, 05:20 UTC | 15m |
| 2026-04-30 | CTN3T | PUY → ZAG | Apr 30, 04:05 UTC | Apr 30, 04:20 UTC | 15m |
| 2026-04-29 | CTN632 | - | Apr 29, 20:10 UTC | Apr 29, 20:30 UTC | 20m |
| 2026-04-29 | CTN632 | - | Apr 29, 19:15 UTC | Apr 29, 19:35 UTC | 20m |
| 2026-04-29 | CTN345 | SJJ → ZAG | Apr 29, 14:55 UTC | Apr 29, 15:30 UTC | 35m |
| 2026-04-29 | CTN344 | ZAG → SJJ | Apr 29, 13:40 UTC | Apr 29, 14:00 UTC | 20m |
| 2026-04-29 | CTN4437 | MUC → ZAG | Apr 29, 11:55 UTC | Apr 29, 12:40 UTC | 45m |
| 2026-04-29 | CTN436R | ZAG → MUC | Apr 29, 09:45 UTC | Apr 29, 10:40 UTC | 55m |
| 2026-04-28 | CTN301 | ATH → DBV | Apr 28, 19:25 UTC | Apr 28, 20:10 UTC | 45m |
| 2026-04-28 | CTN301 | ATH → DBV | Apr 28, 17:15 UTC | Apr 28, 18:45 UTC | 1h 30m |
| 2026-04-28 | CTN3RC | DBV → ATH | Apr 28, 14:50 UTC | Apr 28, 16:10 UTC | 1h 20m |
| 2026-04-28 | CTN3RC | DBV → ATH | Apr 28, 13:10 UTC | Apr 28, 13:55 UTC | 45m |
| 2026-04-28 | CTN441 | VIE → ZAG | Apr 28, 07:55 UTC | Apr 28, 08:35 UTC | 40m |
| 2026-04-28 | CTN4AT | ZAG → VIE | Apr 28, 06:10 UTC | Apr 28, 06:45 UTC | 35m |
| 2026-04-28 | CTN3T | PUY → ZAG | Apr 28, 05:00 UTC | Apr 28, 05:15 UTC | 15m |
| 2026-04-28 | CTN3T | PUY → ZAG | Apr 28, 04:05 UTC | Apr 28, 04:15 UTC | 10m |
| 2026-04-27 | CTN632 | - | Apr 27, 20:35 UTC | Apr 27, 20:45 UTC | 10m |
| 2026-04-27 | CTN632 | - | Apr 27, 19:35 UTC | Apr 27, 19:50 UTC | 15m |
| 2026-04-27 | CTN437 | MUC → ZAG | Apr 27, 17:50 UTC | Apr 27, 18:30 UTC | 40m |
| 2026-04-27 | CTN436 | ZAG → MUC | Apr 27, 15:45 UTC | Apr 27, 16:40 UTC | 55m |
| 2026-04-27 | CTN345 | SJJ → ZAG | Apr 27, 14:15 UTC | Apr 27, 14:45 UTC | 30m |
| 2026-04-27 | CTN344 | ZAG → SJJ | Apr 27, 12:55 UTC | Apr 27, 13:25 UTC | 30m |
| 2026-04-27 | CTN5V | SPU → ZAG | Apr 27, 11:45 UTC | Apr 27, 11:55 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.
Prefer a tail-number view? See the 9A-CQC page for operator, model, and routing details .