sensors Mode-S transponder
501D13
ICAO 24-bit transponder address · allocated to Croatia
Currently assigned to 9A-CRO · BOMBARDIER CL-600 Challenger
- Hex
- 501D13
- Octal
- 24016423
- Decimal
- 5,250,323
- Country
- HR
- Tail
- 9A-CRO
- Type
- CL60
- Flights observed
- 53
- Distinct callsigns
- 1
- Country
- HR
- Last broadcast
- 7d ago
Last known position
Country allocation
The ICAO 24-bit address 501D13 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 1 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| 9ACRO | - | 53 | 2026-07-20 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-20 | 9ACRO | - | Jul 20, 05:10 UTC | Jul 20, 06:05 UTC | 55m |
| 2026-07-16 | 9ACRO | - | Jul 16, 05:15 UTC | Jul 16, 06:15 UTC | 1h 0m |
| 2026-07-14 | 9ACRO | - | Jul 14, 15:55 UTC | Jul 14, 17:40 UTC | 1h 45m |
| 2026-07-14 | 9ACRO | - | Jul 14, 11:55 UTC | Jul 14, 13:45 UTC | 1h 50m |
| 2026-07-09 | 9ACRO | - | Jul 9, 20:45 UTC | Jul 9, 21:15 UTC | 30m |
| 2026-07-09 | 9ACRO | - | Jul 9, 11:35 UTC | Jul 9, 12:05 UTC | 30m |
| 2026-07-08 | 9ACRO | - | Jul 8, 13:40 UTC | Jul 8, 15:30 UTC | 1h 50m |
| 2026-07-07 | 9ACRO | - | Jul 7, 07:05 UTC | Jul 7, 08:40 UTC | 1h 35m |
| 2026-06-29 | 9ACRO | - | Jun 29, 15:49 UTC | Jun 29, 17:14 UTC | 1h 25m |
| 2026-06-27 | 9ACRO | - | Jun 27, 12:29 UTC | Jun 27, 13:55 UTC | 1h 25m |
| 2026-06-26 | 9ACRO | - | Jun 26, 12:19 UTC | Jun 26, 12:59 UTC | 40m |
| 2026-06-19 | 9ACRO | - | Jun 19, 15:09 UTC | Jun 19, 16:29 UTC | 1h 20m |
| 2026-06-17 | 9ACRO | - | Jun 17, 10:15 UTC | Jun 17, 11:45 UTC | 1h 30m |
| 2026-06-09 | 9ACRO | - | Jun 9, 13:55 UTC | Jun 9, 14:40 UTC | 45m |
| 2026-06-09 | 9ACRO | - | Jun 9, 11:50 UTC | Jun 9, 12:25 UTC | 35m |
| 2026-06-08 | 9ACRO | - | Jun 8, 16:55 UTC | Jun 8, 17:15 UTC | 20m |
| 2026-06-08 | 9ACRO | - | Jun 8, 08:50 UTC | Jun 8, 09:10 UTC | 20m |
| 2026-06-08 | 9ACRO | - | Jun 8, 07:00 UTC | Jun 8, 07:40 UTC | 40m |
| 2026-06-08 | 9ACRO | - | Jun 8, 05:35 UTC | Jun 8, 06:10 UTC | 35m |
| 2026-06-05 | 9ACRO | - | Jun 5, 15:05 UTC | Jun 5, 15:35 UTC | 30m |
| 2026-06-04 | 9ACRO | - | Jun 4, 14:05 UTC | Jun 4, 14:45 UTC | 40m |
| 2026-06-01 | 9ACRO | - | Jun 1, 20:00 UTC | Jun 1, 20:20 UTC | 20m |
| 2026-06-01 | 9ACRO | - | Jun 1, 08:30 UTC | Jun 1, 08:45 UTC | 15m |
| 2026-05-28 | 9ACRO | - | May 28, 16:40 UTC | May 28, 17:20 UTC | 40m |
| 2026-05-28 | 9ACRO | - | May 28, 15:10 UTC | May 28, 15:55 UTC | 45m |
| 2026-05-28 | 9ACRO | - | May 28, 11:55 UTC | May 28, 14:25 UTC | 2h 30m |
| 2026-05-27 | 9ACRO | - | May 27, 13:20 UTC | May 27, 15:45 UTC | 2h 25m |
| 2026-05-26 | 9ACRO | - | May 26, 16:00 UTC | May 26, 16:45 UTC | 45m |
| 2026-05-26 | 9ACRO | - | May 26, 12:40 UTC | May 26, 13:29 UTC | 50m |
| 2026-05-26 | 9ACRO | - | May 26, 11:09 UTC | May 26, 11:54 UTC | 45m |
| 2026-05-26 | 9ACRO | - | May 26, 08:45 UTC | May 26, 09:35 UTC | 50m |
| 2026-05-26 | 9ACRO | - | May 26, 07:15 UTC | May 26, 07:59 UTC | 45m |
| 2026-05-13 | 9ACRO | - | May 13, 17:15 UTC | May 13, 18:35 UTC | 1h 20m |
| 2026-05-13 | 9ACRO | ATH → MST | May 13, 13:20 UTC | May 13, 16:25 UTC | 3h 5m |
| 2026-05-12 | 9ACRO | - | May 12, 16:50 UTC | May 12, 18:25 UTC | 1h 35m |
| 2026-05-12 | 9ACRO | - | May 12, 15:35 UTC | May 12, 16:10 UTC | 35m |
| 2026-05-12 | 9ACRO | - | May 12, 14:10 UTC | May 12, 14:50 UTC | 40m |
| 2026-05-12 | 9ACRO | - | May 12, 07:30 UTC | May 12, 08:05 UTC | 35m |
| 2026-05-06 | 9ACRO | - | May 6, 12:40 UTC | May 6, 13:00 UTC | 20m |
| 2026-05-06 | 9ACRO | - | May 6, 05:50 UTC | May 6, 06:05 UTC | 15m |
| 2026-05-05 | 9ACRO | - | May 5, 10:45 UTC | May 5, 12:15 UTC | 1h 30m |
| 2026-05-05 | 9ACRO | - | May 5, 08:15 UTC | May 5, 10:00 UTC | 1h 45m |
| 2026-05-04 | 9ACRO | - | May 4, 13:10 UTC | May 4, 16:10 UTC | 3h 0m |
| 2026-05-04 | 9ACRO | - | May 4, 11:05 UTC | May 4, 11:25 UTC | 20m |
| 2026-05-03 | 9ACRO | - | May 3, 18:05 UTC | May 3, 18:25 UTC | 20m |
| 2026-05-03 | 9ACRO | - | May 3, 13:55 UTC | May 3, 16:30 UTC | 2h 35m |
| 2026-05-03 | 9ACRO | - | May 3, 06:10 UTC | May 3, 09:35 UTC | 3h 25m |
| 2026-04-29 | 9ACRO | - | Apr 29, 10:45 UTC | Apr 29, 11:20 UTC | 35m |
| 2026-04-28 | 9ACRO | - | Apr 28, 06:50 UTC | Apr 28, 07:20 UTC | 30m |
| 2026-04-24 | 9ACRO | - | Apr 24, 14:40 UTC | Apr 24, 17:10 UTC | 2h 30m |
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-CRO page for operator, model, and routing details .