sensors Mode-S transponder
4CAC0B
ICAO 24-bit transponder address · allocated to Ireland
Currently assigned to EI-KDD · AIRBUS A-321neo
- Hex
- 4CAC0B
- Octal
- 23126013
- Decimal
- 5,024,779
- Country
- IE
- Tail
- EI-KDD
- Type
- A21N
- Flights observed
- 144
- Distinct callsigns
- 20
- Country
- IE
- Last broadcast
- 19h ago
Last known position
Country allocation
The ICAO 24-bit address 4CAC0B falls within the block assigned to Ireland (IE) by ICAO Annex 10, Volume III. Every aircraft registered in Ireland 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 |
|---|---|---|---|
| KZR215 | - | 14 | 2026-07-03 |
| KZR925 | - | 10 | 2026-07-10 |
| KZR139 | Air Astana | 9 | 2026-05-31 |
| KZR140 | Air Astana | 8 | 2026-05-31 |
| KZR915 | - | 7 | 2026-06-16 |
| KZR963 | Air Astana | 6 | 2026-05-25 |
| KZR558 | - | 6 | 2026-06-30 |
| KZR557 | - | 6 | 2026-06-30 |
| KZR216 | - | 6 | 2026-07-03 |
| KZR908 | - | 5 | 2026-07-08 |
| KZR661 | Air Astana | 5 | 2026-07-01 |
| KZR926 | - | 4 | 2026-07-11 |
| KZR591 | - | 4 | 2026-06-19 |
| KZR292 | Air Astana | 4 | 2026-05-29 |
| KZR291 | Air Astana | 4 | 2026-05-28 |
| KZR964 | Air Astana | 3 | 2026-05-25 |
| KZR917 | Air Astana | 3 | 2026-06-06 |
| KZR907 | - | 3 | 2026-06-21 |
| KZR859 | Air Astana | 3 | 2026-06-11 |
| KZR267 | - | 3 | 2026-07-11 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | KZR590 | - | Jul 13, 08:35 UTC | Jul 13, 10:30 UTC | 1h 55m |
| 2026-07-12 | KZR660 | BJV → ALA | Jul 12, 13:10 UTC | Jul 13, 06:20 UTC | 17h 10m |
| 2026-07-11 | KZR659 | ALA → BJV | Jul 11, 22:50 UTC | Jul 12, 11:40 UTC | 12h 50m |
| 2026-07-11 | KZR267 | - | Jul 11, 20:20 UTC | Jul 11, 20:35 UTC | 15m |
| 2026-07-11 | KZR926 | - | Jul 11, 08:10 UTC | Jul 11, 10:05 UTC | 1h 55m |
| 2026-07-10 | KZR925 | - | Jul 10, 11:00 UTC | Jul 11, 06:30 UTC | 19h 30m |
| 2026-07-10 | KZR925 | - | Jul 10, 09:50 UTC | Jul 11, 06:30 UTC | 20h 40m |
| 2026-07-10 | KZR925 | - | Jul 10, 05:35 UTC | Jul 10, 08:15 UTC | 2h 40m |
| 2026-07-09 | KZR925 | - | Jul 9, 10:50 UTC | Jul 10, 08:15 UTC | 21h 25m |
| 2026-07-09 | KZR925 | - | Jul 9, 09:20 UTC | Jul 10, 08:15 UTC | 22h 55m |
| 2026-07-08 | KZR925 | - | Jul 8, 21:05 UTC | Jul 9, 07:50 UTC | 10h 45m |
| 2026-07-08 | KZR908 | - | Jul 8, 06:20 UTC | Jul 8, 19:25 UTC | 13h 5m |
| 2026-07-07 | KZR926 | - | Jul 7, 09:15 UTC | Jul 8, 04:45 UTC | 19h 30m |
| 2026-07-07 | KZR925 | - | Jul 7, 05:10 UTC | Jul 7, 07:45 UTC | 2h 35m |
| 2026-07-06 | KZR925 | - | Jul 6, 08:50 UTC | Jul 7, 07:45 UTC | 22h 55m |
| 2026-07-06 | KZR590 | - | Jul 6, 08:30 UTC | Jul 7, 06:25 UTC | 21h 55m |
| 2026-07-05 | KZR589 | - | Jul 5, 13:20 UTC | Jul 6, 06:35 UTC | 17h 15m |
| 2026-07-04 | KZR659 | ALA → BJV | Jul 4, 22:30 UTC | Jul 5, 11:30 UTC | 13h 0m |
| 2026-07-04 | KZR267 | - | Jul 4, 20:20 UTC | Jul 4, 20:40 UTC | 20m |
| 2026-07-03 | KZR216 | - | Jul 3, 08:35 UTC | Jul 3, 10:25 UTC | 1h 50m |
| 2026-07-03 | KZR215 | - | Jul 3, 06:40 UTC | Jul 3, 07:10 UTC | 30m |
| 2026-07-02 | KZR215 | - | Jul 2, 10:50 UTC | Jul 3, 06:00 UTC | 19h 10m |
| 2026-07-02 | KZR216 | - | Jul 2, 09:15 UTC | Jul 3, 06:00 UTC | 20h 45m |
| 2026-07-01 | KZR215 | - | Jul 1, 12:50 UTC | Jul 2, 07:40 UTC | 18h 50m |
| 2026-07-01 | KZR215 | - | Jul 1, 12:20 UTC | Jul 2, 07:40 UTC | 19h 20m |
| 2026-07-01 | KZR661 | NQZ → BJV | Jul 1, 08:05 UTC | Jul 1, 10:40 UTC | 2h 35m |
| 2026-06-30 | KZR661 | NQZ → BJV | Jun 30, 11:20 UTC | Jul 1, 10:40 UTC | 23h 20m |
| 2026-06-30 | KZR558 | - | Jun 30, 09:35 UTC | Jul 1, 08:45 UTC | 23h 10m |
| 2026-06-30 | KZR557 | - | Jun 30, 04:30 UTC | Jun 30, 07:25 UTC | 2h 55m |
| 2026-06-29 | KZR557 | - | Jun 29, 08:54 UTC | Jun 30, 07:25 UTC | 22h 30m |
| 2026-06-29 | KZR215 | - | Jun 29, 05:00 UTC | Jun 29, 07:30 UTC | 2h 30m |
| 2026-06-28 | KZR215 | - | Jun 28, 08:59 UTC | Jun 29, 07:30 UTC | 22h 30m |
| 2026-06-28 | KZR226 | - | Jun 28, 08:05 UTC | Jun 29, 06:19 UTC | 22h 15m |
| 2026-06-28 | KZR225 | - | Jun 28, 04:10 UTC | Jun 28, 06:24 UTC | 2h 15m |
| 2026-06-26 | KZR215 | - | Jun 26, 05:05 UTC | Jun 26, 10:30 UTC | 5h 25m |
| 2026-06-25 | KZR215 | - | Jun 25, 08:50 UTC | Jun 26, 06:54 UTC | 22h 5m |
| 2026-06-25 | KZR558 | - | Jun 25, 07:09 UTC | Jun 26, 06:15 UTC | 23h 5m |
| 2026-06-25 | KZR557 | - | Jun 25, 02:14 UTC | Jun 25, 05:00 UTC | 2h 45m |
| 2026-06-23 | KZR314 | SCO → NQZ | Jun 23, 18:20 UTC | Jun 23, 18:29 UTC | 10m |
| 2026-06-23 | KZR216 | - | Jun 23, 09:09 UTC | Jun 23, 10:59 UTC | 1h 50m |
| 2026-06-23 | KZR215 | - | Jun 23, 05:29 UTC | Jun 23, 07:45 UTC | 2h 15m |
| 2026-06-21 | KZR908 | - | Jun 21, 06:35 UTC | Jun 21, 07:14 UTC | 40m |
| 2026-06-21 | KZR907 | - | Jun 21, 04:14 UTC | Jun 21, 05:04 UTC | 50m |
| 2026-06-20 | KZR8226 | - | Jun 20, 08:59 UTC | Jun 21, 05:04 UTC | 20h 5m |
| 2026-06-20 | KZR8226 | - | Jun 20, 08:14 UTC | Jun 21, 05:04 UTC | 20h 50m |
| 2026-06-19 | KZR592 | - | Jun 19, 10:54 UTC | Jun 20, 04:44 UTC | 17h 50m |
| 2026-06-19 | KZR591 | - | Jun 19, 05:59 UTC | Jun 19, 08:14 UTC | 2h 15m |
| 2026-06-18 | KZR591 | - | Jun 18, 09:00 UTC | Jun 19, 08:14 UTC | 23h 14m |
| 2026-06-17 | KZR215 | NQZ → AYT | Jun 17, 12:50 UTC | Jun 18, 07:05 UTC | 18h 15m |
| 2026-06-17 | KZR215 | NQZ → AYT | Jun 17, 10:50 UTC | Jun 18, 07:05 UTC | 20h 15m |
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 EI-KDD page for operator, model, and routing details .