sensors Mode-S transponder
68332A
ICAO 24-bit transponder address · allocated to Kazakhstan
Currently assigned to UP-B3738 · BOEING 737 MAX 9
- Hex
- 68332A
- Octal
- 32031452
- Decimal
- 6,828,842
- Country
- KZ
- Tail
- UP-B3738
- Type
- B39M
- Flights observed
- 217
- Distinct callsigns
- 20
- Country
- KZ
- Last broadcast
- Jul 26, 22:20 UTC
Current position
Country allocation
The ICAO 24-bit address 68332A 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 |
|---|---|---|---|
| VSV5273 | - | 34 | 2026-07-25 |
| VSV5240 | - | 15 | 2026-07-02 |
| VSV5275 | - | 14 | 2026-07-23 |
| VSV5282 | - | 12 | 2026-07-24 |
| VSV5276 | - | 12 | 2026-07-10 |
| VSV5266 | - | 11 | 2026-07-04 |
| VSV5268 | - | 10 | 2026-07-25 |
| VSV5274 | - | 9 | 2026-07-26 |
| VSV5212 | Scat Air | 7 | 2026-05-13 |
| VSV5241 | - | 6 | 2026-05-07 |
| VSV482 | - | 6 | 2026-07-05 |
| VSV481 | - | 6 | 2026-07-04 |
| VSV5380 | - | 5 | 2026-06-29 |
| VSV5291 | Scat Air | 5 | 2026-05-04 |
| VSV5281 | - | 5 | 2026-06-26 |
| VSV5269 | - | 5 | 2026-07-16 |
| VSV5265 | - | 5 | 2026-05-08 |
| VSV5267 | Scat Air | 4 | 2026-06-23 |
| VSV5263 | - | 4 | 2026-06-30 |
| VSV5201 | - | 4 | 2026-07-01 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | VSV5274 | - | Jul 26, 09:15 UTC | Jul 26, 22:20 UTC | 13h 5m |
| 2026-07-25 | VSV5268 | - | Jul 25, 18:35 UTC | Jul 26, 05:30 UTC | 10h 55m |
| 2026-07-25 | VSV5273 | - | Jul 25, 08:30 UTC | Jul 25, 11:05 UTC | 2h 35m |
| 2026-07-24 | VSV5273 | - | Jul 24, 12:40 UTC | Jul 25, 11:05 UTC | 22h 25m |
| 2026-07-24 | VSV5282 | - | Jul 24, 01:25 UTC | Jul 24, 11:20 UTC | 9h 55m |
| 2026-07-23 | VSV5275 | - | Jul 23, 11:15 UTC | Jul 23, 23:10 UTC | 11h 55m |
| 2026-07-22 | VSV5273 | - | Jul 22, 15:20 UTC | Jul 23, 09:30 UTC | 18h 10m |
| 2026-07-22 | VSV5287 | - | Jul 22, 03:30 UTC | Jul 22, 12:30 UTC | 9h 0m |
| 2026-07-21 | VSV5369 | - | Jul 21, 22:15 UTC | Jul 22, 00:40 UTC | 2h 25m |
| 2026-07-20 | VSV5272 | - | Jul 20, 10:10 UTC | Jul 20, 12:00 UTC | 1h 50m |
| 2026-07-20 | VSV5271 | - | Jul 20, 06:05 UTC | Jul 20, 08:30 UTC | 2h 25m |
| 2026-07-19 | VSV844 | - | Jul 19, 07:10 UTC | Jul 20, 06:30 UTC | 23h 20m |
| 2026-07-18 | VSV843 | CIT → TBS | Jul 18, 16:35 UTC | Jul 19, 05:50 UTC | 13h 15m |
| 2026-07-18 | VSV725 | - | Jul 18, 14:45 UTC | Jul 18, 15:10 UTC | 25m |
| 2026-07-16 | VSV5270 | - | Jul 16, 09:25 UTC | Jul 17, 01:15 UTC | 15h 50m |
| 2026-07-16 | VSV5269 | - | Jul 16, 03:55 UTC | Jul 16, 06:55 UTC | 3h 0m |
| 2026-07-15 | VSV5269 | - | Jul 15, 10:35 UTC | Jul 16, 06:55 UTC | 20h 20m |
| 2026-07-15 | VSV5269 | - | Jul 15, 09:25 UTC | Jul 16, 06:55 UTC | 21h 30m |
| 2026-07-14 | VSV5268 | AYT → AYT | Jul 14, 18:20 UTC | Jul 15, 05:50 UTC | 11h 29m |
| 2026-07-14 | VSV5273 | - | Jul 14, 08:40 UTC | Jul 14, 11:15 UTC | 2h 35m |
| 2026-07-13 | VSV5273 | - | Jul 13, 14:35 UTC | Jul 14, 11:15 UTC | 20h 40m |
| 2026-07-13 | VSV5273 | AYT → AYT | Jul 13, 13:10 UTC | Jul 14, 11:15 UTC | 22h 5m |
| 2026-07-13 | VSV5282 | - | Jul 13, 02:01 UTC | Jul 13, 11:35 UTC | 9h 35m |
| 2026-07-12 | VSV5275 | - | Jul 12, 09:10 UTC | Jul 13, 00:15 UTC | 15h 5m |
| 2026-07-11 | VSV5268 | - | Jul 11, 18:25 UTC | Jul 12, 05:20 UTC | 10h 55m |
| 2026-07-11 | VSV5273 | - | Jul 11, 08:45 UTC | Jul 11, 11:00 UTC | 2h 15m |
| 2026-07-10 | VSV5276 | - | Jul 10, 12:40 UTC | Jul 11, 11:00 UTC | 22h 20m |
| 2026-07-10 | VSV5282 | - | Jul 10, 01:25 UTC | Jul 10, 11:10 UTC | 9h 45m |
| 2026-07-09 | VSV5275 | - | Jul 9, 11:30 UTC | Jul 9, 23:30 UTC | 12h 0m |
| 2026-07-09 | VSV5273 | - | Jul 9, 07:45 UTC | Jul 9, 10:15 UTC | 2h 30m |
| 2026-07-08 | VSV5273 | - | Jul 8, 10:35 UTC | Jul 9, 10:15 UTC | 23h 40m |
| 2026-07-08 | VSV5276 | - | Jul 8, 09:15 UTC | Jul 9, 08:30 UTC | 23h 15m |
| 2026-07-07 | VSV5268 | - | Jul 7, 18:25 UTC | Jul 8, 05:45 UTC | 11h 20m |
| 2026-07-07 | VSV5273 | - | Jul 7, 08:35 UTC | Jul 7, 11:00 UTC | 2h 25m |
| 2026-07-06 | VSV5273 | - | Jul 6, 10:35 UTC | Jul 7, 10:30 UTC | 23h 55m |
| 2026-07-06 | VSV476 | - | Jul 6, 10:20 UTC | Jul 6, 10:35 UTC | 15m |
| 2026-07-05 | VSV482 | - | Jul 5, 15:55 UTC | Jul 5, 17:20 UTC | 1h 25m |
| 2026-07-04 | VSV481 | - | Jul 4, 21:50 UTC | Jul 5, 14:20 UTC | 16h 30m |
| 2026-07-04 | VSV481 | - | Jul 4, 17:00 UTC | Jul 5, 14:20 UTC | 21h 20m |
| 2026-07-04 | VSV5266 | - | Jul 4, 02:40 UTC | Jul 4, 21:50 UTC | 19h 10m |
| 2026-07-03 | VSV5266 | - | Jul 3, 19:00 UTC | Jul 4, 17:20 UTC | 22h 20m |
| 2026-07-03 | VSV5266 | - | Jul 3, 17:25 UTC | Jul 4, 11:35 UTC | 18h 10m |
| 2026-07-02 | VSV5240 | - | Jul 2, 14:00 UTC | Jul 3, 03:40 UTC | 13h 40m |
| 2026-07-02 | VSV5240 | - | Jul 2, 06:35 UTC | Jul 3, 03:40 UTC | 21h 5m |
| 2026-07-02 | VSV5240 | - | Jul 2, 04:55 UTC | Jul 3, 03:40 UTC | 22h 45m |
| 2026-07-01 | VSV5201 | - | Jul 1, 16:20 UTC | Jul 2, 02:40 UTC | 10h 20m |
| 2026-06-30 | VSV5263 | - | Jun 30, 18:40 UTC | Jul 1, 04:45 UTC | 10h 5m |
| 2026-06-29 | VSV5380 | - | Jun 29, 13:14 UTC | Jun 30, 06:10 UTC | 16h 56m |
| 2026-06-29 | VSV5282 | - | Jun 29, 01:55 UTC | Jun 29, 11:25 UTC | 9h 30m |
| 2026-06-28 | VSV5275 | - | Jun 28, 22:10 UTC | Jun 29, 00:34 UTC | 2h 25m |
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-B3738 page for operator, model, and routing details .