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