sensors Mode-S transponder

683273

ICAO 24-bit transponder address · allocated to Kazakhstan

Currently assigned to UP-B3726 · BOEING 737 MAX 9

Hex
683273
Octal
32031163
Decimal
6,828,659
Country
KZ
Tail
UP-B3726
Type
B39M
No current signal · last broadcast 6h ago
Flights observed
152
Distinct callsigns
20
Country
KZ
Last broadcast
6h ago

Last known position

Most recent position reported by Mode-S 683273.

Country allocation

The ICAO 24-bit address 683273 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
VSV5240 - 37 2026-05-28
VSV5241 - 19 2026-05-28
VSV5266 - 17 2026-05-30
VSV5291 Scat Air 9 2026-05-24
VSV5265 - 9 2026-05-29
VSV5264 - 8 2026-05-26
VSV5262 - 8 2026-05-23
VSV5263 - 7 2026-05-19
VSV5321 Scat Air 6 2026-04-19
VSV5304 - 5 2026-04-18
VSV5261 - 4 2026-05-23
VSV5200 Scat Air 4 2026-05-20
VSV5292 - 3 2026-05-03
VSV5212 Scat Air 3 2026-05-09
VSV5275 - 2 2026-05-10
VSV5272 - 2 2026-05-04
VSV726 Scat Air 1 2026-04-13
VSV725 Scat Air 1 2026-04-13
VSV5320 - 1 2026-04-17
VSV5274 - 1 2026-05-06

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-05-30 VSV5266 - May 30, 03:20 UTCMay 30, 06:00 UTC2h 40m
2026-05-30 VSV5266 - May 30, 00:35 UTCMay 30, 00:45 UTC10m
2026-05-29 VSV5265 - May 29, 22:10 UTCMay 29, 22:20 UTC10m
2026-05-29 VSV5265 - May 29, 17:55 UTCMay 29, 20:25 UTC2h 30m
2026-05-28 VSV5240 - May 28, 19:05 UTCMay 29, 09:15 UTC14h 10m
2026-05-28 VSV5240 - May 28, 12:50 UTCMay 29, 09:15 UTC20h 25m
2026-05-28 VSV5240 - May 28, 10:50 UTCMay 29, 09:15 UTC22h 25m
2026-05-28 VSV5241 - May 28, 10:30 UTCMay 29, 08:45 UTC22h 15m
2026-05-28 VSV5241 - May 28, 05:35 UTCMay 29, 00:20 UTC18h 45m
2026-05-28 VSV5241 - May 28, 02:55 UTCMay 29, 00:20 UTC21h 25m
2026-05-28 VSV5266 - May 28, 00:25 UTCMay 28, 00:35 UTC10m
2026-05-27 VSV5265 - May 27, 22:25 UTCMay 27, 22:35 UTC10m
2026-05-27 VSV5265 - May 27, 18:00 UTCMay 27, 20:25 UTC2h 25m
2026-05-26 VSV5264 - May 26, 18:55 UTCMay 27, 06:40 UTC11h 45m
2026-05-26 VSV5264 - May 26, 08:50 UTCMay 27, 06:40 UTC21h 50m
2026-05-26 VSV5240 - May 26, 06:14 UTCMay 26, 21:29 UTC15h 15m
2026-05-25 VSV5240 - May 25, 23:00 UTCMay 26, 21:29 UTC22h 30m
2026-05-25 VSV5240 - May 25, 19:15 UTCMay 26, 09:09 UTC13h 55m
2026-05-25 VSV5240 - May 25, 12:55 UTCMay 26, 09:09 UTC20h 14m
2026-05-25 VSV5240 - May 25, 11:00 UTCMay 26, 09:09 UTC22h 9m
2026-05-24 VSV5291 ALA → ALA May 24, 14:50 UTCMay 25, 08:55 UTC18h 5m
2026-05-24 VSV5291 ALA → ALA May 24, 14:30 UTCMay 25, 08:55 UTC18h 25m
2026-05-23 VSV5262 - May 23, 21:20 UTCMay 24, 10:15 UTC12h 55m
2026-05-23 VSV5261 - May 23, 04:50 UTCMay 24, 01:55 UTC21h 5m
2026-05-23 VSV5266 - May 23, 02:55 UTCMay 24, 01:55 UTC23h 0m
2026-05-22 VSV5265 - May 22, 17:40 UTCMay 22, 20:10 UTC2h 30m
2026-05-22 VSV5240 - May 22, 06:05 UTCMay 22, 09:00 UTC2h 55m
2026-05-21 VSV5240 - May 21, 12:50 UTCMay 22, 09:00 UTC20h 10m
2026-05-21 VSV5240 - May 21, 10:50 UTCMay 22, 09:00 UTC22h 10m
2026-05-21 VSV5240 - May 21, 10:30 UTCMay 22, 08:45 UTC22h 15m
2026-05-20 VSV5200 SSH → SSH May 20, 21:25 UTCMay 21, 07:20 UTC9h 55m
2026-05-19 VSV5263 - May 19, 19:10 UTCMay 20, 05:45 UTC10h 36m
2026-05-19 VSV5263 - May 19, 08:50 UTCMay 20, 05:45 UTC20h 56m
2026-05-19 VSV5263 - May 19, 06:50 UTCMay 20, 05:45 UTC22h 56m
2026-05-19 VSV5263 - May 19, 06:15 UTCMay 20, 04:45 UTC22h 31m
2026-05-18 VSV5263 - May 18, 23:30 UTCMay 19, 22:35 UTC23h 5m
2026-05-18 VSV5240 - May 18, 18:50 UTCMay 19, 08:55 UTC14h 5m
2026-05-18 VSV5240 - May 18, 12:55 UTCMay 19, 08:55 UTC19h 59m
2026-05-18 VSV5240 - May 18, 11:55 UTCMay 19, 08:55 UTC20h 59m
2026-05-18 VSV5240 - May 18, 08:50 UTCMay 19, 08:45 UTC23h 54m
2026-05-18 VSV5291 ALA → ALA May 18, 06:55 UTCMay 19, 06:45 UTC23h 49m
2026-05-18 VSV5291 ALA → ALA May 18, 06:05 UTCMay 19, 00:45 UTC18h 39m
2026-05-17 VSV5291 ALA → ALA May 17, 16:50 UTCMay 18, 13:50 UTC21h 0m
2026-05-17 VSV5291 ALA → ALA May 17, 14:50 UTCMay 18, 13:50 UTC23h 0m
2026-05-17 VSV5291 ALA → ALA May 17, 14:25 UTCMay 18, 12:20 UTC21h 55m
2026-05-17 VSV5266 - May 17, 02:00 UTCMay 17, 05:25 UTC3h 25m
2026-05-16 VSV5265 - May 16, 17:50 UTCMay 16, 21:25 UTC3h 35m
2026-05-16 VSV5266 - May 16, 01:45 UTCMay 16, 05:25 UTC3h 40m
2026-05-15 VSV5265 - May 15, 17:30 UTCMay 15, 21:05 UTC3h 35m
2026-05-14 VSV5240 - May 14, 12:50 UTCMay 15, 09:05 UTC20h 15m

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

Mode-S 683273 frequently asked

What is Mode-S code 683273?
683273 is an ICAO 24-bit transponder address. Allocated to Kazakhstan. Assigned to UP-B3726.
Where is Mode-S 683273 registered?
Mode-S code 683273 is allocated to Kazakhstan (KZ). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 683273 broadcasting right now?
No active broadcast right now. Last signal was 6h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 683273, octal 32031163, decimal 6,828,659.
What flights does 683273 operate?
Mode-S 683273 has broadcast 20 distinct callsigns, including VSV5240, VSV5241, VSV5266, VSV5291, VSV5265.