sensors Mode-S transponder
68327B
ICAO 24-bit transponder address · allocated to Kazakhstan
Currently assigned to UP-EM019 · EMBRAER EMB-135 Legacy
- Hex
- 68327B
- Octal
- 32031173
- Decimal
- 6,828,667
- Country
- KZ
- Tail
- UP-EM019
- Type
- E35L
- Flights observed
- 52
- Distinct callsigns
- 6
- Country
- KZ
- Last broadcast
- Jul 25, 11:20 UTC
Last known position
Country allocation
The ICAO 24-bit address 68327B 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 6 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-25 | FJK1261 | - | Jul 25, 11:05 UTC | Jul 25, 11:20 UTC | 15m |
| 2026-07-24 | FJK1262 | - | Jul 24, 13:10 UTC | Jul 24, 17:10 UTC | 4h 0m |
| 2026-07-24 | FJK1261 | - | Jul 24, 11:10 UTC | Jul 24, 11:25 UTC | 15m |
| 2026-07-11 | FJK1262 | - | Jul 11, 20:15 UTC | Jul 11, 20:50 UTC | 35m |
| 2026-07-10 | FJK1261 | - | Jul 10, 14:25 UTC | Jul 10, 15:00 UTC | 35m |
| 2026-07-09 | FJK1262 | - | Jul 9, 10:10 UTC | Jul 9, 10:35 UTC | 25m |
| 2026-07-08 | FJK1263 | - | Jul 8, 21:55 UTC | Jul 9, 09:25 UTC | 11h 30m |
| 2026-07-08 | FJK1262 | - | Jul 8, 18:40 UTC | Jul 8, 20:45 UTC | 2h 5m |
| 2026-07-07 | FJK1261 | - | Jul 7, 09:45 UTC | Jul 7, 12:35 UTC | 2h 50m |
| 2026-07-04 | FJK1263 | - | Jul 4, 19:00 UTC | Jul 4, 20:00 UTC | 1h 0m |
| 2026-07-04 | FJK1262 | - | Jul 4, 14:25 UTC | Jul 4, 17:35 UTC | 3h 10m |
| 2026-07-03 | FJK1263 | SVO → SVO | Jul 3, 14:40 UTC | Jul 3, 15:00 UTC | 20m |
| 2026-06-28 | FJK1263 | - | Jun 28, 12:55 UTC | Jun 28, 15:34 UTC | 2h 40m |
| 2026-06-28 | FJK1262 | - | Jun 28, 10:24 UTC | Jun 28, 12:09 UTC | 1h 45m |
| 2026-06-28 | FJK1263 | - | Jun 28, 05:24 UTC | Jun 28, 07:50 UTC | 2h 25m |
| 2026-06-28 | FJK1262 | - | Jun 28, 00:45 UTC | Jun 28, 04:05 UTC | 3h 20m |
| 2026-06-27 | FJK1261 | - | Jun 27, 23:10 UTC | Jun 27, 23:45 UTC | 35m |
| 2026-06-12 | FJK1261 | - | Jun 12, 10:15 UTC | Jun 12, 10:40 UTC | 25m |
| 2026-06-07 | FJK1261 | - | Jun 7, 09:20 UTC | Jun 7, 09:35 UTC | 15m |
| 2026-06-07 | FJK1261 | - | Jun 7, 08:30 UTC | Jun 7, 08:45 UTC | 15m |
| 2026-06-05 | FJK1262 | - | Jun 5, 12:40 UTC | Jun 5, 13:40 UTC | 1h 0m |
| 2026-06-04 | FJK1261 | - | Jun 4, 10:15 UTC | Jun 4, 14:40 UTC | 4h 25m |
| 2026-06-03 | FJK1262 | - | Jun 3, 02:50 UTC | Jun 3, 06:15 UTC | 3h 25m |
| 2026-06-03 | FJK1261 | - | Jun 3, 01:35 UTC | Jun 3, 01:55 UTC | 20m |
| 2026-05-30 | FJK1266 | - | May 30, 22:00 UTC | May 30, 23:35 UTC | 1h 35m |
| 2026-05-30 | FJK1265 | NCE → BUD | May 30, 18:55 UTC | May 30, 20:30 UTC | 1h 35m |
| 2026-05-28 | FJK1266 | BUD → NCE | May 28, 11:45 UTC | May 28, 13:30 UTC | 1h 45m |
| 2026-05-28 | FJK1265 | LEJ → BUD | May 28, 09:25 UTC | May 28, 10:30 UTC | 1h 5m |
| 2026-05-27 | FJK1267 | GVA → LEJ | May 27, 06:04 UTC | May 27, 07:20 UTC | 1h 16m |
| 2026-05-27 | FJK1266 | - | May 27, 02:39 UTC | May 27, 05:14 UTC | 2h 35m |
| 2026-05-26 | FJK1265 | - | May 26, 23:25 UTC | May 27, 00:34 UTC | 1h 10m |
| 2026-05-23 | FJK1261 | - | May 23, 12:10 UTC | May 23, 12:45 UTC | 35m |
| 2026-05-18 | FJK1263 | - | May 18, 13:05 UTC | May 18, 13:15 UTC | 10m |
| 2026-05-17 | FJK1262 | - | May 17, 15:25 UTC | May 18, 13:15 UTC | 21h 50m |
| 2026-05-17 | FJK1261 | - | May 17, 11:40 UTC | May 17, 14:40 UTC | 3h 0m |
| 2026-05-17 | FJK1263 | - | May 17, 06:00 UTC | May 17, 07:55 UTC | 1h 55m |
| 2026-05-14 | FJK1261 | - | May 14, 09:00 UTC | May 14, 09:40 UTC | 40m |
| 2026-05-13 | FJK1262 | - | May 13, 12:25 UTC | May 13, 14:20 UTC | 1h 55m |
| 2026-05-13 | FJK1261 | - | May 13, 08:30 UTC | May 13, 10:15 UTC | 1h 45m |
| 2026-05-12 | FJK1262 | - | May 12, 14:50 UTC | May 12, 17:00 UTC | 2h 10m |
| 2026-05-12 | FJK1261 | - | May 12, 09:05 UTC | May 12, 12:35 UTC | 3h 30m |
| 2026-05-11 | FJK1263 | - | May 11, 14:25 UTC | May 11, 15:30 UTC | 1h 5m |
| 2026-05-11 | FJK1262 | ZRH → TBS | May 11, 09:35 UTC | May 11, 13:25 UTC | 3h 50m |
| 2026-05-10 | FJK1261 | TBS → ZRH | May 10, 09:40 UTC | May 10, 14:00 UTC | 4h 20m |
| 2026-05-09 | FJK1263 | - | May 9, 20:05 UTC | May 9, 21:30 UTC | 1h 25m |
| 2026-05-01 | FJK1261 | - | May 1, 13:45 UTC | May 1, 14:00 UTC | 15m |
| 2026-04-19 | FJK1261 | - | Apr 19, 23:20 UTC | Apr 19, 23:40 UTC | 20m |
| 2026-04-17 | FJK1262 | - | Apr 17, 08:35 UTC | Apr 17, 08:45 UTC | 10m |
| 2026-04-15 | FJK1262 | - | Apr 15, 07:30 UTC | Apr 15, 08:45 UTC | 1h 15m |
| 2026-04-14 | FJK1262 | - | Apr 14, 16:50 UTC | Apr 14, 17:40 UTC | 50m |
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-EM019 page for operator, model, and routing details .