sensors Mode-S transponder
6832C4
ICAO 24-bit transponder address · allocated to Kazakhstan
Currently assigned to UP-C6004 · BOMBARDIER CL-600 Challenger
- Hex
- 6832C4
- Octal
- 32031304
- Decimal
- 6,828,740
- Country
- KZ
- Tail
- UP-C6004
- Type
- CL60
- Flights observed
- 22
- Distinct callsigns
- 6
- Country
- KZ
- Last broadcast
- 3d ago
Last known position
Country allocation
The ICAO 24-bit address 6832C4 falls within the block assigned to Kazakhstan (KZ) by ICAO Annex 10, Volume III. Every aircraft registered in Kazakhstan 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 6 distinct
Recent flights last 22
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-17 | KEJ6480 | - | Jun 17, 01:15 UTC | Jun 17, 06:40 UTC | 5h 25m |
| 2026-06-16 | KEJ6482 | - | Jun 16, 11:00 UTC | Jun 16, 11:20 UTC | 20m |
| 2026-06-15 | UPC6004 | - | Jun 15, 15:04 UTC | Jun 16, 11:20 UTC | 20h 15m |
| 2026-06-15 | UPC6004 | - | Jun 15, 14:05 UTC | Jun 16, 11:20 UTC | 21h 15m |
| 2026-06-15 | UPC6004 | - | Jun 15, 11:00 UTC | Jun 15, 13:00 UTC | 2h 0m |
| 2026-06-10 | UPC6004 | - | Jun 10, 13:30 UTC | Jun 10, 15:20 UTC | 1h 50m |
| 2026-06-10 | UPC6004 | - | Jun 10, 08:30 UTC | Jun 10, 12:20 UTC | 3h 50m |
| 2026-06-02 | UPC6004 | - | Jun 2, 17:20 UTC | Jun 2, 19:10 UTC | 1h 50m |
| 2026-06-02 | UPC6004 | - | Jun 2, 15:00 UTC | Jun 2, 15:50 UTC | 50m |
| 2026-05-23 | UPC6004 | - | May 23, 12:00 UTC | May 23, 13:45 UTC | 1h 45m |
| 2026-05-23 | UPC6004 | - | May 23, 10:00 UTC | May 23, 11:05 UTC | 1h 5m |
| 2026-05-23 | UPC6004 | - | May 23, 07:10 UTC | May 23, 07:25 UTC | 15m |
| 2026-05-23 | UPC6004 | - | May 23, 05:25 UTC | May 23, 06:30 UTC | 1h 5m |
| 2026-05-16 | KEJ6485 | - | May 16, 15:50 UTC | May 16, 16:35 UTC | 45m |
| 2026-05-13 | KEJ6485 | - | May 13, 12:30 UTC | May 13, 13:45 UTC | 1h 15m |
| 2026-05-10 | KEJ6485 | - | May 10, 06:50 UTC | May 10, 07:45 UTC | 55m |
| 2026-05-07 | KEJ6485 | - | May 7, 10:15 UTC | May 7, 10:50 UTC | 35m |
| 2026-05-06 | KEJ6485 | - | May 6, 12:25 UTC | May 6, 13:05 UTC | 40m |
| 2026-05-01 | KEJ6481 | - | May 1, 14:50 UTC | May 1, 15:20 UTC | 30m |
| 2026-05-01 | KEJ6480 | - | May 1, 09:40 UTC | May 1, 13:45 UTC | 4h 5m |
| 2026-04-17 | KEJ6486 | - | Apr 17, 12:40 UTC | Apr 17, 13:05 UTC | 25m |
| 2026-04-17 | KEJ6485 | - | Apr 17, 10:00 UTC | Apr 17, 10:15 UTC | 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 UP-C6004 page for operator, model, and routing details .