Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

683266

ICAO 24-bit transponder address · allocated to Kazakhstan

Currently assigned to UP-B3720 · BOEING 737 MAX 8

Hex
683266
Octal
32031146
Decimal
6,828,646
Country
KZ
Tail
UP-B3720
Type
B38M
No current signal · last broadcast 5h ago
Flights observed
67
Distinct callsigns
20
Country
KZ
Last broadcast
5h ago

Last known position

Most recent position reported by Mode-S 683266.

Country allocation

The ICAO 24-bit address 683266 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
VSV485 - 14 2026-07-07
VSV486 - 10 2026-07-07
VSV844 - 8 2026-07-16
VSV843 - 7 2026-07-16
VSV470 - 4 2026-07-03
VSV490 - 3 2026-07-18
VSV489 Scat Air 3 2026-07-18
VSV469 - 3 2026-07-02
VSV724 - 2 2026-07-08
VSV723 Scat Air 2 2026-06-17
VSV483 Scat Air 2 2026-07-02
VSV826 Scat Air 1 2026-07-17
VSV824 Scat Air 1 2026-06-13
VSV823 Scat Air 1 2026-06-12
VSV818 Scat Air 1 2026-05-13
VSV817 Scat Air 1 2026-05-13
VSV801 - 1 2026-07-15
VSV484 - 1 2026-06-30
VSV468 - 1 2026-06-29
VSV467 - 1 2026-06-29

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-18 VSV490 - Jul 18, 13:35 UTCJul 18, 16:30 UTC2h 55m
2026-07-18 VSV489 CIT → BUD Jul 18, 09:00 UTCJul 18, 12:25 UTC3h 25m
2026-07-17 VSV489 CIT → BUD Jul 17, 16:24 UTCJul 18, 12:25 UTC20h 1m
2026-07-17 VSV826 LED → CIT Jul 17, 15:00 UTCJul 17, 15:15 UTC15m
2026-07-16 VSV844 - Jul 16, 07:10 UTCJul 16, 07:35 UTC25m
2026-07-16 VSV843 - Jul 16, 04:50 UTCJul 16, 05:25 UTC35m
2026-07-15 VSV843 - Jul 15, 09:05 UTCJul 16, 05:25 UTC20h 20m
2026-07-15 VSV801 - Jul 15, 06:50 UTCJul 15, 07:15 UTC25m
2026-07-14 VSV490 - Jul 14, 17:10 UTCJul 15, 06:10 UTC12h 59m
2026-07-13 VSV844 - Jul 13, 10:10 UTCJul 13, 10:40 UTC30m
2026-07-13 VSV843 - Jul 13, 07:25 UTCJul 13, 07:55 UTC30m
2026-07-10 VSV844 - Jul 10, 12:35 UTCJul 10, 13:05 UTC30m
2026-07-10 VSV843 - Jul 10, 10:10 UTCJul 10, 10:45 UTC35m
2026-07-09 VSV490 - Jul 9, 07:15 UTCJul 9, 10:10 UTC2h 55m
2026-07-09 VSV489 - Jul 9, 05:15 UTCJul 9, 05:40 UTC25m
2026-07-08 VSV724 - Jul 8, 04:00 UTCJul 8, 04:25 UTC25m
2026-07-07 VSV486 - Jul 7, 15:35 UTCJul 8, 02:35 UTC11h 0m
2026-07-07 VSV485 - Jul 7, 13:40 UTCJul 7, 14:00 UTC20m
2026-07-07 VSV485 - Jul 7, 11:30 UTCJul 7, 12:15 UTC45m
2026-07-06 VSV844 - Jul 6, 10:20 UTCJul 6, 10:45 UTC25m
2026-07-06 VSV843 - Jul 6, 07:35 UTCJul 6, 08:05 UTC30m
2026-07-03 VSV844 - Jul 3, 11:55 UTCJul 3, 12:25 UTC30m
2026-07-03 VSV470 - Jul 3, 00:15 UTCJul 3, 10:20 UTC10h 5m
2026-07-02 VSV469 - Jul 2, 07:45 UTCJul 2, 21:55 UTC14h 10m
2026-07-02 VSV483 CIT → MUC Jul 2, 05:55 UTCJul 2, 06:15 UTC20m
2026-06-30 VSV484 - Jun 30, 15:50 UTCJun 30, 17:35 UTC1h 45m
2026-06-29 VSV468 - Jun 29, 22:05 UTCJun 30, 14:35 UTC16h 31m
2026-06-29 VSV467 - Jun 29, 20:09 UTCJun 29, 20:35 UTC25m
2026-06-29 VSV844 - Jun 29, 10:24 UTCJun 29, 19:24 UTC9h 0m
2026-06-29 VSV843 - Jun 29, 07:44 UTCJun 29, 08:14 UTC30m
2026-06-25 VSV486 - Jun 25, 07:15 UTCJun 25, 19:15 UTC12h 0m
2026-06-25 VSV485 - Jun 25, 03:10 UTCJun 25, 05:50 UTC2h 40m
2026-06-17 VSV724 UKK → CIT Jun 17, 04:00 UTCJun 17, 04:21 UTC20m
2026-06-17 VSV723 CIT → UKK Jun 17, 02:00 UTCJun 17, 02:25 UTC25m
2026-06-16 VSV723 CIT → UKK Jun 16, 03:39 UTCJun 17, 02:25 UTC22h 46m
2026-06-15 VSV470 - Jun 15, 23:25 UTCJun 16, 03:39 UTC4h 15m
2026-06-15 VSV469 - Jun 15, 17:25 UTCJun 15, 21:35 UTC4h 10m
2026-06-14 VSV844 TBS → CIT Jun 14, 07:15 UTCJun 14, 07:50 UTC35m
2026-06-13 VSV824 BUS → NQZ Jun 13, 13:10 UTCJun 14, 05:25 UTC16h 15m
2026-06-12 VSV823 NQZ → BUS Jun 12, 18:10 UTCJun 13, 12:05 UTC17h 54m
2026-06-10 VSV486 IST → CIT Jun 10, 07:45 UTCJun 10, 09:50 UTC2h 5m
2026-06-10 VSV485 CIT → IST Jun 10, 05:40 UTCJun 10, 06:00 UTC20m
2026-06-10 VSV485 CIT → IST Jun 10, 03:20 UTCJun 10, 05:00 UTC1h 40m
2026-06-05 VSV486 IST → CIT Jun 5, 21:10 UTCJun 5, 23:15 UTC2h 5m
2026-06-04 VSV470 BKK → CIT Jun 4, 23:35 UTCJun 5, 19:30 UTC19h 55m
2026-06-04 VSV470 BKK → CIT Jun 4, 23:15 UTCJun 5, 19:30 UTC20h 15m
2026-06-04 VSV469 CIT → BKK Jun 4, 07:05 UTCJun 4, 21:50 UTC14h 45m
2026-06-04 VSV483 CIT → MUC Jun 4, 05:00 UTCJun 4, 05:40 UTC40m
2026-05-26 VSV486 IST → CIT May 26, 16:50 UTCMay 26, 17:50 UTC1h 0m
2026-05-26 VSV486 IST → CIT May 26, 15:45 UTCMay 26, 15:54 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-B3720 page for operator, model, and routing details .

Mode-S 683266 frequently asked

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