sensors Mode-S transponder

683268

ICAO 24-bit transponder address · allocated to Kazakhstan

Currently assigned to UP-B5705 · BOEING 757-200

Hex
683268
Octal
32031150
Decimal
6,828,648
Country
KZ
Tail
UP-B5705
Type
B752
No current signal · last broadcast Jul 26, 12:40 UTC
Flights observed
173
Distinct callsigns
20
Country
KZ
Last broadcast
Jul 26, 12:40 UTC

Last known position

Most recent position reported by Mode-S 683268.

Country allocation

The ICAO 24-bit address 683268 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 20 distinct

Callsign Airline Flights Last seen
VSV5278 - 45 2026-07-23
VSV5280 - 15 2026-07-20
VSV5298 - 9 2026-07-23
VSV5277 Scat Air 9 2026-07-22
VSV5279 - 8 2026-06-18
VSV5334 Scat Air 7 2026-04-15
VSV5297 Scat Air 7 2026-07-23
VSV5287 - 6 2026-06-26
VSV5283 - 6 2026-07-18
VSV5275 - 6 2026-07-07
VSV5273 - 6 2026-07-18
VSV5212 Scat Air 6 2026-07-26
VSV5272 - 5 2026-06-27
VSV5268 - 4 2026-05-20
VSV5210 - 4 2026-07-25
VSV5351 - 3 2026-04-25
VSV5335 - 3 2026-04-17
VSV5274 - 3 2026-07-21
VSV5267 Scat Air 3 2026-05-19
VSV5317 - 2 2026-05-08

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-26 VSV5213 GOI → ALA Jul 26, 10:55 UTCJul 26, 12:40 UTC1h 45m
2026-07-26 VSV5212 ALA → GOI Jul 26, 06:40 UTCJul 26, 09:05 UTC2h 25m
2026-07-25 VSV5212 ALA → GOI Jul 25, 12:25 UTCJul 26, 09:05 UTC20h 41m
2026-07-25 VSV5212 ALA → GOI Jul 25, 11:20 UTCJul 26, 09:05 UTC21h 46m
2026-07-25 VSV5210 - Jul 25, 06:35 UTCJul 25, 09:00 UTC2h 25m
2026-07-24 VSV5210 - Jul 24, 10:05 UTCJul 25, 09:00 UTC22h 55m
2026-07-24 VSV5213 GOI → ALA Jul 24, 09:50 UTCJul 25, 07:55 UTC22h 5m
2026-07-23 VSV5298 - Jul 23, 22:30 UTCJul 24, 04:15 UTC5h 45m
2026-07-23 VSV5297 AYT → UKK Jul 23, 15:40 UTCJul 23, 20:40 UTC5h 0m
2026-07-23 VSV5278 - Jul 23, 08:20 UTCJul 23, 08:45 UTC25m
2026-07-22 VSV5277 AYT → CIT Jul 22, 12:20 UTCJul 23, 07:40 UTC19h 20m
2026-07-21 VSV5274 - Jul 21, 19:40 UTCJul 22, 10:25 UTC14h 45m
2026-07-20 VSV5280 - Jul 20, 20:30 UTCJul 21, 06:35 UTC10h 4m
2026-07-20 VSV5278 - Jul 20, 06:10 UTCJul 20, 08:35 UTC2h 25m
2026-07-19 VSV5278 - Jul 19, 10:05 UTCJul 20, 08:35 UTC22h 30m
2026-07-19 VSV5277 AYT → CIT Jul 19, 09:55 UTCJul 20, 08:00 UTC22h 5m
2026-07-18 VSV5273 - Jul 18, 19:45 UTCJul 19, 08:10 UTC12h 25m
2026-07-18 VSV5283 - Jul 18, 14:45 UTCJul 18, 15:15 UTC30m
2026-07-18 VSV5284 - Jul 18, 07:25 UTCJul 18, 14:00 UTC6h 35m
2026-07-17 VSV5288 - Jul 17, 21:15 UTCJul 18, 06:00 UTC8h 46m
2026-07-16 VSV5280 - Jul 16, 20:09 UTCJul 17, 06:50 UTC10h 40m
2026-07-15 VSV5278 - Jul 15, 14:05 UTCJul 16, 08:35 UTC18h 30m
2026-07-15 VSV5278 AYT → AYT Jul 15, 12:15 UTCJul 16, 08:35 UTC20h 20m
2026-07-15 VSV5217 - Jul 15, 08:05 UTCJul 15, 10:35 UTC2h 30m
2026-07-13 VSV5292 - Jul 13, 07:15 UTCJul 13, 09:40 UTC2h 25m
2026-07-12 VSV5291 - Jul 12, 10:55 UTCJul 13, 04:30 UTC17h 35m
2026-07-12 VSV5212 - Jul 12, 06:15 UTCJul 12, 08:35 UTC2h 20m
2026-07-11 VSV5212 - Jul 11, 12:15 UTCJul 12, 08:35 UTC20h 20m
2026-07-11 VSV5212 - Jul 11, 11:05 UTCJul 12, 08:35 UTC21h 30m
2026-07-11 VSV5210 - Jul 11, 06:15 UTCJul 11, 08:50 UTC2h 35m
2026-07-10 VSV5296 - Jul 10, 00:50 UTCJul 10, 07:00 UTC6h 10m
2026-07-09 VSV5211 - Jul 9, 10:05 UTCJul 10, 07:00 UTC20h 55m
2026-07-09 VSV5278 - Jul 9, 06:00 UTCJul 9, 08:30 UTC2h 30m
2026-07-08 VSV5278 - Jul 8, 10:15 UTCJul 9, 08:30 UTC22h 15m
2026-07-07 VSV5275 - Jul 7, 19:35 UTCJul 8, 07:55 UTC12h 20m
2026-07-06 VSV5280 - Jul 6, 20:25 UTCJul 7, 07:40 UTC11h 15m
2026-07-06 VSV5278 - Jul 6, 05:55 UTCJul 6, 08:15 UTC2h 20m
2026-07-05 VSV5278 - Jul 5, 10:15 UTCJul 6, 08:15 UTC22h 0m
2026-07-04 VSV5273 - Jul 4, 19:50 UTCJul 5, 07:40 UTC11h 50m
2026-07-03 VSV5283 - Jul 3, 21:00 UTCJul 4, 16:00 UTC19h 0m
2026-07-02 VSV5298 - Jul 2, 22:25 UTCJul 3, 04:20 UTC5h 55m
2026-07-02 VSV5297 - Jul 2, 15:35 UTCJul 2, 20:35 UTC5h 0m
2026-07-02 VSV5278 - Jul 2, 06:20 UTCJul 2, 08:40 UTC2h 20m
2026-07-01 VSV5278 - Jul 1, 10:05 UTCJul 2, 08:40 UTC22h 35m
2026-06-30 VSV5275 - Jun 30, 19:30 UTCJul 1, 07:55 UTC12h 25m
2026-06-29 VSV5280 - Jun 29, 20:15 UTCJun 30, 06:30 UTC10h 16m
2026-06-29 VSV5278 - Jun 29, 06:09 UTCJun 29, 08:35 UTC2h 25m
2026-06-28 VSV5278 - Jun 28, 12:05 UTCJun 29, 08:35 UTC20h 30m
2026-06-28 VSV5278 - Jun 28, 10:15 UTCJun 29, 08:35 UTC22h 20m
2026-06-28 VSV5273 - Jun 28, 08:14 UTCJun 28, 08:39 UTC25m

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

Mode-S 683268 frequently asked

What is Mode-S code 683268?
683268 is an ICAO 24-bit transponder address. Allocated to Kazakhstan. Assigned to UP-B5705.
Where is Mode-S 683268 registered?
Mode-S code 683268 is allocated to Kazakhstan (KZ). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 683268 broadcasting right now?
No active broadcast right now. Last signal was Jul 26, 12:40 UTC.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 683268, octal 32031150, decimal 6,828,648.
What flights does 683268 operate?
Mode-S 683268 has broadcast 20 distinct callsigns, including VSV5278, VSV5280, VSV5298, VSV5277, VSV5279.