sensors Mode-S transponder
68326F
ICAO 24-bit transponder address · allocated to Kazakhstan
- Hex
- 68326F
- Octal
- 32031157
- Decimal
- 6,828,655
- Country
- KZ
- Flights observed
- 24
- Distinct callsigns
- 3
- Country
- KZ
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address 68326F 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 3 distinct
Recent flights last 24
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-04 | FJK1265 | - | Jun 4, 07:05 UTC | Jun 4, 09:30 UTC | 2h 25m |
| 2026-06-03 | FJK1265 | - | Jun 3, 08:30 UTC | Jun 3, 08:45 UTC | 15m |
| 2026-05-11 | FJK1267 | - | May 11, 15:45 UTC | May 11, 18:10 UTC | 2h 25m |
| 2026-05-11 | FJK1266 | - | May 11, 12:10 UTC | May 11, 13:55 UTC | 1h 45m |
| 2026-05-11 | FJK1265 | - | May 11, 10:15 UTC | May 11, 10:45 UTC | 30m |
| 2026-05-08 | FJK1265 | - | May 8, 09:39 UTC | May 8, 11:55 UTC | 2h 15m |
| 2026-05-05 | FJK1265 | - | May 5, 13:10 UTC | May 5, 13:30 UTC | 20m |
| 2026-05-01 | FJK1266 | - | May 1, 04:30 UTC | May 1, 09:00 UTC | 4h 30m |
| 2026-04-29 | FJK1267 | - | Apr 29, 04:10 UTC | Apr 29, 23:05 UTC | 18h 55m |
| 2026-04-28 | FJK1266 | - | Apr 28, 12:20 UTC | Apr 28, 14:35 UTC | 2h 15m |
| 2026-04-28 | FJK1265 | - | Apr 28, 10:55 UTC | Apr 28, 11:05 UTC | 10m |
| 2026-04-28 | FJK1265 | - | Apr 28, 09:25 UTC | Apr 28, 10:10 UTC | 45m |
| 2026-04-27 | FJK1266 | SVO → SVO | Apr 27, 09:15 UTC | Apr 27, 09:30 UTC | 15m |
| 2026-04-25 | FJK1267 | - | Apr 25, 15:50 UTC | Apr 26, 11:05 UTC | 19h 15m |
| 2026-04-25 | FJK1267 | - | Apr 25, 15:15 UTC | Apr 26, 11:05 UTC | 19h 50m |
| 2026-04-25 | FJK1266 | - | Apr 25, 10:05 UTC | Apr 25, 12:50 UTC | 2h 45m |
| 2026-04-25 | FJK1265 | - | Apr 25, 08:30 UTC | Apr 25, 08:40 UTC | 10m |
| 2026-04-25 | FJK1265 | - | Apr 25, 06:10 UTC | Apr 25, 06:20 UTC | 10m |
| 2026-04-24 | FJK1266 | - | Apr 24, 15:25 UTC | Apr 24, 15:40 UTC | 15m |
| 2026-04-22 | FJK1266 | - | Apr 22, 05:45 UTC | Apr 22, 11:30 UTC | 5h 45m |
| 2026-04-17 | FJK1265 | - | Apr 17, 14:00 UTC | Apr 17, 14:40 UTC | 40m |
| 2026-04-13 | FJK1267 | - | Apr 13, 22:35 UTC | Apr 13, 23:15 UTC | 40m |
| 2026-04-13 | FJK1266 | - | Apr 13, 16:50 UTC | Apr 13, 17:20 UTC | 30m |
| 2026-04-13 | FJK1266 | - | Apr 13, 15:35 UTC | Apr 13, 15:45 UTC | 10m |
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.