sensors Mode-S transponder
C828EF
ICAO 24-bit transponder address · allocated to New Zealand
Currently assigned to ZK-JCJ · BOMBARDIER CL-600 Challenger
- Hex
- C828EF
- Octal
- 62024357
- Decimal
- 13,117,679
- Country
- NZ
- Tail
- ZK-JCJ
- Type
- CL60
- Flights observed
- 46
- Distinct callsigns
- 1
- Country
- NZ
- Last broadcast
- 5h ago
Last known position
Country allocation
The ICAO 24-bit address C828EF falls within the block assigned to New Zealand (NZ) by ICAO Annex 10, Volume III. Every aircraft registered in New Zealand 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 |
|---|---|---|---|
| ZKJCJ | - | 46 | 2026-06-23 |
Recent flights last 46
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-23 | ZKJCJ | - | Jun 23, 00:30 UTC | Jun 23, 00:50 UTC | 20m |
| 2026-06-13 | ZKJCJ | - | Jun 13, 23:40 UTC | Jun 14, 00:35 UTC | 55m |
| 2026-06-13 | ZKJCJ | - | Jun 13, 19:10 UTC | Jun 13, 22:05 UTC | 2h 55m |
| 2026-06-12 | ZKJCJ | - | Jun 12, 04:55 UTC | Jun 12, 06:00 UTC | 1h 5m |
| 2026-06-12 | ZKJCJ | - | Jun 12, 03:55 UTC | Jun 12, 04:20 UTC | 25m |
| 2026-06-12 | ZKJCJ | - | Jun 12, 02:30 UTC | Jun 12, 03:25 UTC | 55m |
| 2026-06-10 | ZKJCJ | - | Jun 10, 04:10 UTC | Jun 10, 05:15 UTC | 1h 5m |
| 2026-06-09 | ZKJCJ | - | Jun 9, 21:15 UTC | Jun 9, 21:25 UTC | 10m |
| 2026-06-07 | ZKJCJ | IVC → CHC | Jun 7, 04:25 UTC | Jun 7, 05:05 UTC | 40m |
| 2026-06-07 | ZKJCJ | - | Jun 7, 00:49 UTC | Jun 7, 03:55 UTC | 3h 5m |
| 2026-06-03 | ZKJCJ | - | Jun 3, 00:00 UTC | Jun 3, 00:30 UTC | 30m |
| 2026-06-02 | ZKJCJ | - | Jun 2, 22:45 UTC | Jun 2, 23:25 UTC | 40m |
| 2026-05-28 | ZKJCJ | - | May 28, 22:50 UTC | May 28, 23:30 UTC | 40m |
| 2026-05-28 | ZKJCJ | - | May 28, 21:10 UTC | May 28, 22:25 UTC | 1h 15m |
| 2026-05-28 | ZKJCJ | SYD → AKL | May 28, 04:45 UTC | May 28, 07:30 UTC | 2h 45m |
| 2026-05-27 | ZKJCJ | - | May 27, 22:15 UTC | May 28, 00:55 UTC | 2h 40m |
| 2026-05-27 | ZKJCJ | - | May 27, 19:20 UTC | May 27, 20:55 UTC | 1h 35m |
| 2026-05-27 | ZKJCJ | - | May 27, 01:14 UTC | May 27, 01:49 UTC | 35m |
| 2026-05-26 | ZKJCJ | - | May 26, 22:15 UTC | May 26, 22:29 UTC | 15m |
| 2026-05-25 | ZKJCJ | - | May 25, 23:40 UTC | May 26, 00:09 UTC | 30m |
| 2026-05-25 | ZKJCJ | - | May 25, 22:19 UTC | May 25, 23:00 UTC | 40m |
| 2026-05-25 | ZKJCJ | - | May 25, 20:45 UTC | May 25, 21:24 UTC | 40m |
| 2026-05-21 | ZKJCJ | - | May 21, 05:10 UTC | May 21, 05:50 UTC | 40m |
| 2026-05-21 | ZKJCJ | - | May 21, 01:00 UTC | May 21, 01:20 UTC | 20m |
| 2026-05-20 | ZKJCJ | - | May 20, 22:20 UTC | May 20, 23:50 UTC | 1h 30m |
| 2026-05-20 | ZKJCJ | - | May 20, 06:40 UTC | May 20, 07:20 UTC | 40m |
| 2026-05-19 | ZKJCJ | - | May 19, 20:15 UTC | May 20, 05:45 UTC | 9h 31m |
| 2026-05-14 | ZKJCJ | MEL → CHC | May 14, 23:20 UTC | May 15, 02:25 UTC | 3h 5m |
| 2026-05-10 | ZKJCJ | - | May 10, 23:44 UTC | May 11, 03:00 UTC | 3h 15m |
| 2026-05-10 | ZKJCJ | ADL → CHC | May 10, 08:40 UTC | May 10, 12:30 UTC | 3h 50m |
| 2026-05-07 | ZKJCJ | MEB → ADL | May 7, 08:40 UTC | May 7, 09:55 UTC | 1h 15m |
| 2026-05-05 | ZKJCJ | CHC → MEB | May 5, 20:20 UTC | May 5, 23:40 UTC | 3h 20m |
| 2026-05-03 | ZKJCJ | IVC → CHC | May 3, 04:40 UTC | May 3, 05:20 UTC | 40m |
| 2026-05-03 | ZKJCJ | CHC → IVC | May 3, 02:30 UTC | May 3, 03:10 UTC | 40m |
| 2026-04-29 | ZKJCJ | IVC → CHC | Apr 29, 22:45 UTC | Apr 29, 23:25 UTC | 39m |
| 2026-04-29 | ZKJCJ | - | Apr 29, 21:00 UTC | Apr 29, 21:45 UTC | 45m |
| 2026-04-29 | ZKJCJ | - | Apr 29, 04:55 UTC | Apr 29, 05:55 UTC | 1h 0m |
| 2026-04-29 | ZKJCJ | - | Apr 29, 02:20 UTC | Apr 29, 03:24 UTC | 1h 5m |
| 2026-04-28 | ZKJCJ | - | Apr 28, 05:20 UTC | Apr 28, 06:25 UTC | 1h 5m |
| 2026-04-27 | ZKJCJ | - | Apr 27, 19:50 UTC | Apr 27, 20:45 UTC | 55m |
| 2026-04-23 | ZKJCJ | - | Apr 23, 21:35 UTC | Apr 23, 23:10 UTC | 1h 35m |
| 2026-04-19 | ZKJCJ | - | Apr 19, 00:00 UTC | Apr 19, 00:50 UTC | 50m |
| 2026-04-18 | ZKJCJ | - | Apr 18, 22:15 UTC | Apr 18, 23:10 UTC | 55m |
| 2026-04-15 | ZKJCJ | - | Apr 15, 02:55 UTC | Apr 15, 03:25 UTC | 30m |
| 2026-04-15 | ZKJCJ | - | Apr 15, 02:25 UTC | Apr 15, 02:50 UTC | 25m |
| 2026-04-15 | ZKJCJ | - | Apr 15, 01:00 UTC | Apr 15, 01:50 UTC | 50m |
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 ZK-JCJ page for operator, model, and routing details .