sensors Mode-S transponder
6832DC
ICAO 24-bit transponder address · allocated to Kazakhstan
Currently assigned to UP-EM005 · EMBRAER EMB-135 Legacy
- Hex
- 6832DC
- Octal
- 32031334
- Decimal
- 6,828,764
- Country
- KZ
- Tail
- UP-EM005
- Type
- E35L
- Flights observed
- 25
- Distinct callsigns
- 1
- Country
- KZ
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 6832DC 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 1 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| UPEM005 | - | 25 | 2026-06-18 |
Recent flights last 25
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-18 | UPEM005 | - | Jun 18, 23:15 UTC | Jun 18, 23:25 UTC | 10m |
| 2026-06-14 | UPEM005 | - | Jun 14, 17:15 UTC | Jun 14, 17:40 UTC | 25m |
| 2026-06-14 | UPEM005 | - | Jun 14, 10:25 UTC | Jun 14, 16:05 UTC | 5h 40m |
| 2026-06-12 | UPEM005 | - | Jun 12, 04:15 UTC | Jun 12, 04:50 UTC | 35m |
| 2026-06-09 | UPEM005 | - | Jun 9, 06:05 UTC | Jun 9, 06:35 UTC | 30m |
| 2026-06-09 | UPEM005 | - | Jun 9, 03:10 UTC | Jun 9, 03:50 UTC | 40m |
| 2026-06-08 | UPEM005 | - | Jun 8, 07:25 UTC | Jun 9, 03:50 UTC | 20h 25m |
| 2026-06-08 | UPEM005 | - | Jun 8, 06:15 UTC | Jun 9, 03:50 UTC | 21h 35m |
| 2026-06-08 | UPEM005 | - | Jun 8, 04:05 UTC | Jun 8, 04:50 UTC | 45m |
| 2026-06-05 | UPEM005 | - | Jun 5, 16:50 UTC | Jun 5, 17:40 UTC | 50m |
| 2026-06-05 | UPEM005 | - | Jun 5, 11:35 UTC | Jun 5, 16:00 UTC | 4h 25m |
| 2026-06-05 | UPEM005 | - | Jun 5, 10:30 UTC | Jun 5, 10:50 UTC | 20m |
| 2026-05-29 | UPEM005 | - | May 29, 16:40 UTC | May 29, 17:00 UTC | 20m |
| 2026-05-28 | UPEM005 | - | May 28, 14:25 UTC | May 28, 16:40 UTC | 2h 15m |
| 2026-05-28 | UPEM005 | - | May 28, 11:15 UTC | May 28, 13:35 UTC | 2h 20m |
| 2026-05-26 | UPEM005 | - | May 26, 12:40 UTC | May 26, 13:19 UTC | 40m |
| 2026-05-26 | UPEM005 | - | May 26, 08:59 UTC | May 26, 11:15 UTC | 2h 15m |
| 2026-05-21 | UPEM005 | - | May 21, 03:40 UTC | May 21, 10:25 UTC | 6h 45m |
| 2026-05-20 | UPEM005 | - | May 20, 07:45 UTC | May 20, 08:50 UTC | 1h 5m |
| 2026-05-18 | UPEM005 | - | May 18, 04:05 UTC | May 18, 04:25 UTC | 20m |
| 2026-05-05 | UPEM005 | - | May 5, 04:00 UTC | May 6, 00:25 UTC | 20h 25m |
| 2026-05-04 | UPEM005 | - | May 4, 23:00 UTC | May 5, 04:25 UTC | 5h 25m |
| 2026-05-04 | UPEM005 | - | May 4, 20:45 UTC | May 4, 21:05 UTC | 20m |
| 2026-05-02 | UPEM005 | - | May 2, 17:00 UTC | May 2, 17:45 UTC | 45m |
| 2026-05-01 | UPEM005 | - | May 1, 18:15 UTC | May 1, 22:20 UTC | 4h 5m |
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-EM005 page for operator, model, and routing details .