Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

683320

ICAO 24-bit transponder address · allocated to Kazakhstan

Currently assigned to UP-EM014 · EMBRAER EMB-135 Legacy

Hex
683320
Octal
32031440
Decimal
6,828,832
Country
KZ
Tail
UP-EM014
Type
E35L
No current signal · last broadcast Jul 26, 07:40 UTC
Flights observed
99
Distinct callsigns
1
Country
KZ
Last broadcast
Jul 26, 07:40 UTC

Last known position

Most recent position reported by Mode-S 683320.

Country allocation

The ICAO 24-bit address 683320 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
UPEM014 - 99 2026-07-26

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-26 UPEM014 - Jul 26, 07:15 UTCJul 26, 07:40 UTC25m
2026-07-20 UPEM014 - Jul 20, 14:50 UTCJul 20, 15:05 UTC15m
2026-07-20 UPEM014 - Jul 20, 12:35 UTCJul 20, 12:55 UTC20m
2026-07-20 UPEM014 - Jul 20, 07:30 UTCJul 20, 07:45 UTC15m
2026-07-19 UPEM014 - Jul 19, 16:30 UTCJul 20, 06:25 UTC13h 55m
2026-07-19 UPEM014 - Jul 19, 09:10 UTCJul 19, 15:20 UTC6h 10m
2026-07-19 UPEM014 SVO → SVO Jul 19, 08:05 UTCJul 19, 08:20 UTC15m
2026-07-18 UPEM014 - Jul 18, 19:15 UTCJul 18, 19:50 UTC35m
2026-07-18 UPEM014 - Jul 18, 12:20 UTCJul 18, 18:35 UTC6h 15m
2026-07-18 UPEM014 - Jul 18, 10:30 UTCJul 18, 11:05 UTC35m
2026-07-17 UPEM014 - Jul 17, 17:40 UTCJul 17, 20:04 UTC2h 25m
2026-07-17 UPEM014 - Jul 17, 15:20 UTCJul 17, 16:29 UTC1h 10m
2026-07-15 UPEM014 - Jul 15, 00:55 UTCJul 15, 04:30 UTC3h 35m
2026-07-13 UPEM014 - Jul 13, 08:45 UTCJul 13, 11:25 UTC2h 40m
2026-07-11 UPEM014 - Jul 11, 17:50 UTCJul 11, 18:20 UTC30m
2026-07-11 UPEM014 - Jul 11, 12:50 UTCJul 11, 13:50 UTC1h 0m
2026-07-10 UPEM014 - Jul 10, 08:50 UTCJul 10, 14:10 UTC5h 20m
2026-07-09 UPEM014 PMO → BER Jul 9, 15:15 UTCJul 9, 17:35 UTC2h 20m
2026-07-09 UPEM014 - Jul 9, 09:30 UTCJul 9, 14:10 UTC4h 40m
2026-07-09 UPEM014 - Jul 9, 06:25 UTCJul 9, 07:55 UTC1h 30m
2026-07-08 UPEM014 - Jul 8, 05:20 UTCJul 8, 12:20 UTC7h 0m
2026-07-07 UPEM014 FRL → LIN Jul 7, 15:05 UTCJul 7, 15:45 UTC40m
2026-07-05 UPEM014 - Jul 5, 14:00 UTCJul 5, 14:20 UTC20m
2026-07-05 UPEM014 - Jul 5, 12:20 UTCJul 5, 13:20 UTC1h 0m
2026-07-04 UPEM014 - Jul 4, 14:55 UTCJul 4, 16:40 UTC1h 45m
2026-07-04 UPEM014 - Jul 4, 09:15 UTCJul 4, 13:40 UTC4h 25m
2026-07-01 UPEM014 - Jul 1, 14:20 UTCJul 1, 14:45 UTC25m
2026-07-01 UPEM014 - Jul 1, 07:20 UTCJul 1, 13:40 UTC6h 20m
2026-06-30 UPEM014 - Jun 30, 12:40 UTCJun 30, 14:40 UTC2h 0m
2026-06-30 UPEM014 - Jun 30, 09:15 UTCJun 30, 11:55 UTC2h 40m
2026-06-26 UPEM014 - Jun 26, 04:30 UTCJun 26, 04:55 UTC25m
2026-06-24 UPEM014 - Jun 24, 14:29 UTCJun 24, 14:39 UTC10m
2026-06-24 UPEM014 - Jun 24, 12:54 UTCJun 24, 13:20 UTC25m
2026-06-24 UPEM014 - Jun 24, 06:59 UTCJun 24, 10:49 UTC3h 50m
2026-06-24 UPEM014 - Jun 24, 04:30 UTCJun 24, 05:54 UTC1h 25m
2026-06-22 UPEM014 - Jun 22, 13:29 UTCJun 22, 14:05 UTC35m
2026-06-22 UPEM014 - Jun 22, 07:45 UTCJun 22, 12:25 UTC4h 40m
2026-06-22 UPEM014 - Jun 22, 04:34 UTCJun 22, 06:05 UTC1h 30m
2026-06-20 UPEM014 - Jun 20, 05:59 UTCJun 20, 09:29 UTC3h 30m
2026-06-19 UPEM014 - Jun 19, 14:15 UTCJun 19, 17:49 UTC3h 35m
2026-06-18 UPEM014 - Jun 18, 11:35 UTCJun 18, 11:55 UTC20m
2026-06-18 UPEM014 LED → LED Jun 18, 08:15 UTCJun 18, 08:40 UTC25m
2026-06-15 UPEM014 - Jun 15, 15:19 UTCJun 15, 15:45 UTC25m
2026-06-15 UPEM014 - Jun 15, 08:45 UTCJun 15, 14:45 UTC6h 0m
2026-06-12 UPEM014 BLQ → LBG Jun 12, 18:10 UTCJun 12, 19:40 UTC1h 30m
2026-06-12 UPEM014 - Jun 12, 13:05 UTCJun 12, 17:15 UTC4h 10m
2026-06-12 UPEM014 - Jun 12, 11:30 UTCJun 12, 11:40 UTC10m
2026-06-11 UPEM014 - Jun 11, 07:10 UTCJun 11, 07:40 UTC30m
2026-06-11 UPEM014 - Jun 11, 06:05 UTCJun 11, 06:30 UTC25m
2026-06-11 UPEM014 - Jun 11, 01:40 UTCJun 11, 01:50 UTC10m

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-EM014 page for operator, model, and routing details .

Mode-S 683320 frequently asked

What is Mode-S code 683320?
683320 is an ICAO 24-bit transponder address. Allocated to Kazakhstan. Assigned to UP-EM014.
Where is Mode-S 683320 registered?
Mode-S code 683320 is allocated to Kazakhstan (KZ). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 683320 broadcasting right now?
No active broadcast right now. Last signal was Jul 26, 07:40 UTC.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 683320, octal 32031440, decimal 6,828,832.
What flights does 683320 operate?
Mode-S 683320 has broadcast 1 distinct callsign, including UPEM014.