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
No current signal · last broadcast 2d ago
Flights observed
100
Distinct callsigns
4
Country
KZ
Last broadcast
2d ago

Last known position

Most recent position reported by Mode-S 6832BF.

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

Callsign Airline Flights Last seen
TGI1826 - 58 2026-07-26
TGI1827 - 33 2026-07-26
TGI1828 - 7 2026-07-22
TGI1829 - 2 2026-07-11

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-26 TGI1827 - Jul 26, 17:00 UTCJul 26, 17:15 UTC15m
2026-07-26 TGI1827 GSV → GSV Jul 26, 13:30 UTCJul 26, 13:45 UTC15m
2026-07-26 TGI1826 - Jul 26, 11:05 UTCJul 26, 11:30 UTC25m
2026-07-25 TGI1827 - Jul 25, 16:30 UTCJul 25, 17:30 UTC1h 0m
2026-07-25 TGI1826 - Jul 25, 09:55 UTCJul 25, 10:10 UTC15m
2026-07-22 TGI1828 - Jul 22, 15:55 UTCJul 22, 18:00 UTC2h 5m
2026-07-20 TGI1826 - Jul 20, 10:10 UTCJul 20, 12:10 UTC2h 0m
2026-07-19 TGI1827 - Jul 19, 13:15 UTCJul 19, 15:10 UTC1h 55m
2026-07-18 TGI1826 - Jul 18, 11:00 UTCJul 18, 12:40 UTC1h 40m
2026-07-17 TGI1826 - Jul 17, 10:10 UTCJul 17, 10:30 UTC20m
2026-07-17 TGI1826 - Jul 17, 08:40 UTCJul 17, 09:35 UTC55m
2026-07-15 TGI1828 - Jul 15, 07:50 UTCJul 15, 15:00 UTC7h 10m
2026-07-14 TGI1827 - Jul 14, 05:45 UTCJul 14, 22:55 UTC17h 9m
2026-07-12 TGI1826 - Jul 12, 08:55 UTCJul 12, 13:01 UTC4h 5m
2026-07-11 TGI1829 - Jul 11, 11:15 UTCJul 12, 09:00 UTC21h 45m
2026-07-09 TGI1828 - Jul 9, 17:30 UTCJul 9, 18:15 UTC45m
2026-07-09 TGI1827 - Jul 9, 15:15 UTCJul 9, 16:00 UTC45m
2026-07-08 TGI1827 - Jul 8, 17:50 UTCJul 9, 13:00 UTC19h 10m
2026-07-08 TGI1827 - Jul 8, 17:20 UTCJul 9, 13:00 UTC19h 40m
2026-07-08 TGI1826 - Jul 8, 14:00 UTCJul 8, 15:55 UTC1h 55m
2026-07-08 TGI1826 - Jul 8, 11:10 UTCJul 8, 11:25 UTC15m
2026-07-06 TGI1826 - Jul 6, 12:45 UTCJul 6, 14:40 UTC1h 55m
2026-07-05 TGI1826 - Jul 5, 09:00 UTCJul 5, 13:55 UTC4h 55m
2026-07-03 TGI1826 - Jul 3, 12:30 UTCJul 3, 12:40 UTC10m
2026-07-02 TGI1827 - Jul 2, 13:50 UTCJul 2, 14:20 UTC30m
2026-07-02 TGI1826 - Jul 2, 12:15 UTCJul 2, 12:30 UTC15m
2026-07-02 TGI1826 - Jul 2, 08:05 UTCJul 2, 08:25 UTC20m
2026-07-01 TGI1827 - Jul 1, 17:30 UTCJul 1, 17:55 UTC25m
2026-06-30 TGI1827 - Jun 30, 19:50 UTCJul 1, 17:55 UTC22h 5m
2026-06-30 TGI1827 - Jun 30, 19:35 UTCJul 1, 17:45 UTC22h 10m
2026-06-30 TGI1826 - Jun 30, 11:25 UTCJun 30, 11:50 UTC25m
2026-06-26 TGI1826 - Jun 26, 10:55 UTCJun 26, 13:04 UTC2h 10m
2026-06-24 TGI1828 - Jun 24, 15:44 UTCJun 24, 16:19 UTC35m
2026-06-24 TGI1827 - Jun 24, 11:50 UTCJun 24, 12:40 UTC50m
2026-06-24 TGI1826 - Jun 24, 09:05 UTCJun 24, 10:30 UTC1h 25m
2026-06-20 TGI1826 - Jun 20, 08:55 UTCJun 20, 13:09 UTC4h 15m
2026-06-19 TGI1827 - Jun 19, 16:25 UTCJun 19, 17:04 UTC40m
2026-06-19 TGI1826 - Jun 19, 14:24 UTCJun 19, 15:24 UTC1h 0m
2026-06-18 TGI1826 - Jun 18, 12:45 UTCJun 18, 13:05 UTC20m
2026-06-17 TGI1827 - Jun 17, 15:05 UTCJun 17, 19:00 UTC3h 55m
2026-06-17 TGI1826 - Jun 17, 01:10 UTCJun 17, 11:00 UTC9h 50m
2026-06-15 TGI1828 - Jun 15, 17:50 UTCJun 15, 20:40 UTC2h 50m
2026-06-15 TGI1827 ISL → TBS Jun 15, 14:10 UTCJun 15, 15:59 UTC1h 50m
2026-06-15 TGI1826 - Jun 15, 12:39 UTCJun 15, 13:00 UTC20m
2026-06-15 TGI1826 - Jun 15, 07:55 UTCJun 15, 08:25 UTC30m
2026-06-14 TGI1826 - Jun 14, 11:20 UTCJun 14, 11:35 UTC15m
2026-06-13 TGI1827 - Jun 13, 13:50 UTCJun 13, 14:05 UTC15m
2026-06-13 TGI1826 - Jun 13, 11:45 UTCJun 13, 12:30 UTC45m
2026-06-13 TGI1826 - Jun 13, 07:10 UTCJun 13, 07:20 UTC10m
2026-06-12 TGI1826 - Jun 12, 15:00 UTCJun 12, 15:15 UTC15m

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 .

Mode-S 6832BF frequently asked

What is Mode-S code 6832BF?
6832BF is an ICAO 24-bit transponder address. Allocated to Kazakhstan. Assigned to UP-EM028.
Where is Mode-S 6832BF registered?
Mode-S code 6832BF is allocated to Kazakhstan (KZ). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 6832BF broadcasting right now?
No active broadcast right now. Last signal was 2d ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 6832BF, octal 32031277, decimal 6,828,735.
What flights does 6832BF operate?
Mode-S 6832BF has broadcast 4 distinct callsigns, including TGI1826, TGI1827, TGI1828, TGI1829.