Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

6831E4

ICAO 24-bit transponder address · allocated to Kazakhstan

Currently assigned to UP-B5703 · BOEING 757-200

Hex
6831E4
Octal
32030744
Decimal
6,828,516
Country
KZ
Tail
UP-B5703
Type
B752
No current signal · last broadcast 2h ago
Flights observed
106
Distinct callsigns
20
Country
KZ
Last broadcast
2h ago

Last known position

Most recent position reported by Mode-S 6831E4.

Country allocation

The ICAO 24-bit address 6831E4 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
VSV5212 - 24 2026-07-10
VSV5210 - 15 2026-07-05
VSV5291 - 9 2026-07-08
VSV5211 - 9 2026-07-06
VSV5292 - 7 2026-07-09
VSV5213 - 5 2026-06-28
VSV3413 - 5 2026-07-07
VSV3412 - 5 2026-07-07
VSV5351 Scat Air 3 2026-05-24
VSV5278 - 3 2026-07-13
VSV5217 - 3 2026-07-08
VSV5335 - 2 2026-04-24
VSV5271 - 2 2026-05-25
VSV3410 - 2 2026-05-18
VSV5343 - 1 2026-05-15
VSV5342 - 1 2026-05-21
VSV5334 Scat Air 1 2026-04-30
VSV5298 - 1 2026-07-13
VSV5297 - 1 2026-07-13
VSV5295 - 1 2026-07-03

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-13 VSV5298 - Jul 13, 22:35 UTCJul 14, 04:30 UTC5h 55m
2026-07-13 VSV5297 - Jul 13, 15:55 UTCJul 13, 20:40 UTC4h 45m
2026-07-13 VSV5278 - Jul 13, 05:50 UTCJul 13, 08:10 UTC2h 20m
2026-07-12 VSV5278 - Jul 12, 11:30 UTCJul 13, 08:10 UTC20h 40m
2026-07-12 VSV5278 - Jul 12, 10:20 UTCJul 13, 08:10 UTC21h 50m
2026-07-11 VSV5273 - Jul 11, 20:15 UTCJul 12, 08:10 UTC11h 55m
2026-07-11 VSV5283 - Jul 11, 07:45 UTCJul 11, 16:00 UTC8h 15m
2026-07-10 VSV5287 - Jul 10, 20:55 UTCJul 11, 04:01 UTC7h 5m
2026-07-10 VSV5212 - Jul 10, 05:35 UTCJul 10, 08:15 UTC2h 40m
2026-07-09 VSV5212 - Jul 9, 11:05 UTCJul 10, 08:15 UTC21h 10m
2026-07-09 VSV5212 - Jul 9, 09:05 UTCJul 10, 08:15 UTC23h 10m
2026-07-09 VSV5292 - Jul 9, 08:50 UTCJul 10, 06:55 UTC22h 5m
2026-07-08 VSV5291 - Jul 8, 17:50 UTCJul 9, 06:10 UTC12h 20m
2026-07-08 VSV5217 - Jul 8, 13:35 UTCJul 8, 16:00 UTC2h 25m
2026-07-07 VSV3413 - Jul 7, 15:05 UTCJul 8, 14:15 UTC23h 10m
2026-07-07 VSV3413 - Jul 7, 13:30 UTCJul 7, 15:50 UTC2h 20m
2026-07-07 VSV3412 - Jul 7, 07:45 UTCJul 7, 10:20 UTC2h 35m
2026-07-06 VSV5211 - Jul 6, 06:10 UTCJul 6, 08:00 UTC1h 50m
2026-07-05 VSV5210 - Jul 5, 11:25 UTCJul 6, 04:20 UTC16h 55m
2026-07-05 VSV5212 - Jul 5, 06:25 UTCJul 5, 08:50 UTC2h 25m
2026-07-04 VSV5212 - Jul 4, 11:05 UTCJul 5, 08:50 UTC21h 45m
2026-07-04 VSV5292 - Jul 4, 10:05 UTCJul 5, 08:50 UTC22h 45m
2026-07-04 VSV5291 - Jul 4, 04:10 UTCJul 4, 07:05 UTC2h 55m
2026-07-03 VSV5291 - Jul 3, 06:25 UTCJul 4, 04:50 UTC22h 25m
2026-07-03 VSV5295 - Jul 3, 00:55 UTCJul 3, 06:35 UTC5h 40m
2026-07-02 VSV5292 - Jul 2, 09:05 UTCJul 3, 06:35 UTC21h 30m
2026-07-02 VSV5292 - Jul 2, 08:45 UTCJul 3, 06:35 UTC21h 50m
2026-07-02 VSV5292 - Jul 2, 05:05 UTCJul 3, 01:40 UTC20h 35m
2026-07-02 VSV5291 - Jul 2, 03:15 UTCJul 3, 01:40 UTC22h 25m
2026-07-01 VSV5291 - Jul 1, 13:15 UTCJul 2, 11:00 UTC21h 45m
2026-07-01 VSV5291 - Jul 1, 12:25 UTCJul 2, 11:00 UTC22h 35m
2026-07-01 VSV5217 - Jul 1, 07:55 UTCJul 1, 10:05 UTC2h 10m
2026-06-28 VSV5213 - Jun 28, 11:04 UTCJun 28, 12:50 UTC1h 45m
2026-06-28 VSV5212 - Jun 28, 06:34 UTCJun 28, 08:50 UTC2h 15m
2026-06-27 VSV5212 - Jun 27, 11:04 UTCJun 28, 08:50 UTC21h 45m
2026-06-27 VSV5212 - Jun 27, 10:50 UTCJun 28, 08:50 UTC22h 0m
2026-06-27 VSV5210 - Jun 27, 06:19 UTCJun 27, 08:39 UTC2h 20m
2026-06-26 VSV5210 - Jun 26, 11:09 UTCJun 27, 08:39 UTC21h 30m
2026-06-26 VSV5210 - Jun 26, 10:15 UTCJun 27, 08:39 UTC22h 25m
2026-06-26 VSV5212 ALA → GOI Jun 26, 05:24 UTCJun 26, 07:24 UTC2h 0m
2026-06-25 VSV5212 ALA → GOI Jun 25, 11:04 UTCJun 26, 07:24 UTC20h 20m
2026-06-25 VSV5211 - Jun 25, 10:09 UTCJun 26, 07:24 UTC21h 15m
2026-06-24 VSV5210 - Jun 24, 18:50 UTCJun 25, 08:09 UTC13h 20m
2026-06-24 VSV5217 - Jun 24, 14:15 UTCJun 24, 16:34 UTC2h 20m
2026-06-22 VSV5211 - Jun 22, 06:25 UTCJun 22, 08:10 UTC1h 45m
2026-06-21 VSV5210 - Jun 21, 10:54 UTCJun 22, 04:09 UTC17h 15m
2026-06-21 VSV5212 ALA → GOI Jun 21, 06:24 UTCJun 21, 08:49 UTC2h 25m
2026-06-20 VSV5212 ALA → GOI Jun 20, 11:05 UTCJun 21, 08:49 UTC21h 45m
2026-06-20 VSV5292 - Jun 20, 10:15 UTCJun 21, 08:49 UTC22h 35m
2026-06-20 VSV5292 - Jun 20, 07:04 UTCJun 21, 07:00 UTC23h 55m

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

Mode-S 6831E4 frequently asked

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