sensors Mode-S transponder
507C95
ICAO 24-bit transponder address · allocated to Uzbekistan
Currently assigned to UK67014 · BOEING 767-300
- Hex
- 507C95
- Octal
- 24076225
- Decimal
- 5,274,773
- Country
- UZ
- Tail
- UK67014
- Type
- B763
- Flights observed
- 92
- Distinct callsigns
- 20
- Country
- UZ
- Last broadcast
- 14h ago
Last known position
Country allocation
The ICAO 24-bit address 507C95 falls within the block assigned to Uzbekistan (UZ) by ICAO Annex 10, Volume III. Every aircraft registered in Uzbekistan 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 |
|---|---|---|---|
| FKH8011 | - | 12 | 2026-05-27 |
| FKH8062 | - | 10 | 2026-05-11 |
| FKH8021 | - | 9 | 2026-05-28 |
| FKH8874 | - | 5 | 2026-05-04 |
| FKH8541 | - | 5 | 2026-05-09 |
| FKH8443 | - | 5 | 2026-05-11 |
| FKH8051 | - | 5 | 2026-05-29 |
| FKH8023 | - | 5 | 2026-05-29 |
| FKH8441 | - | 4 | 2026-05-02 |
| FKH8063 | - | 4 | 2026-05-05 |
| FKH8022 | - | 4 | 2026-05-28 |
| FKH8875 | - | 3 | 2026-05-04 |
| FKH8064 | - | 3 | 2026-05-26 |
| FKH8061 | - | 3 | 2026-05-04 |
| FKH8052 | - | 3 | 2026-04-25 |
| FKH8013 | - | 3 | 2026-05-27 |
| FKH8542 | - | 2 | 2026-04-15 |
| FKH9983 | - | 1 | 2026-05-25 |
| FKH9982 | - | 1 | 2026-05-13 |
| FKH8873 | - | 1 | 2026-04-19 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | FKH8051 | - | May 29, 12:25 UTC | May 29, 12:45 UTC | 20m |
| 2026-05-29 | FKH8023 | - | May 29, 08:50 UTC | May 29, 09:30 UTC | 40m |
| 2026-05-28 | FKH8022 | - | May 28, 20:00 UTC | May 29, 03:55 UTC | 7h 55m |
| 2026-05-28 | FKH8021 | - | May 28, 03:40 UTC | May 28, 12:40 UTC | 9h 0m |
| 2026-05-27 | FKH8013 | - | May 27, 08:40 UTC | May 27, 22:45 UTC | 14h 5m |
| 2026-05-27 | FKH8011 | - | May 27, 05:55 UTC | May 27, 06:04 UTC | 10m |
| 2026-05-26 | FKH8011 | - | May 26, 22:35 UTC | May 27, 02:54 UTC | 4h 20m |
| 2026-05-26 | FKH8011 | - | May 26, 17:04 UTC | May 26, 17:25 UTC | 20m |
| 2026-05-26 | FKH8064 | - | May 26, 01:40 UTC | May 26, 15:05 UTC | 13h 25m |
| 2026-05-25 | FKH9983 | - | May 25, 19:10 UTC | May 25, 20:15 UTC | 1h 5m |
| 2026-05-13 | FKH9982 | - | May 13, 07:00 UTC | May 13, 08:05 UTC | 1h 5m |
| 2026-05-13 | FKH8011 | - | May 13, 02:10 UTC | May 13, 02:35 UTC | 25m |
| 2026-05-12 | FKH8011 | - | May 12, 19:35 UTC | May 12, 19:50 UTC | 15m |
| 2026-05-12 | FKH8011 | - | May 12, 14:00 UTC | May 12, 14:15 UTC | 15m |
| 2026-05-11 | FKH8064 | - | May 11, 17:25 UTC | May 12, 11:20 UTC | 17h 55m |
| 2026-05-11 | FKH8064 | - | May 11, 13:45 UTC | May 12, 11:20 UTC | 21h 36m |
| 2026-05-11 | FKH8062 | - | May 11, 08:30 UTC | May 11, 08:45 UTC | 15m |
| 2026-05-11 | FKH8443 | - | May 11, 05:30 UTC | May 11, 06:00 UTC | 30m |
| 2026-05-09 | FKH8541 | - | May 9, 23:09 UTC | May 10, 14:49 UTC | 15h 40m |
| 2026-05-09 | FKH8541 | - | May 9, 14:20 UTC | May 10, 09:40 UTC | 19h 20m |
| 2026-05-09 | FKH8250 | - | May 9, 11:30 UTC | May 9, 12:00 UTC | 30m |
| 2026-05-08 | FKH8652 | - | May 8, 23:05 UTC | May 8, 23:40 UTC | 35m |
| 2026-05-08 | FKH8022 | - | May 8, 04:19 UTC | May 8, 06:30 UTC | 2h 10m |
| 2026-05-07 | FKH8021 | - | May 7, 18:55 UTC | May 8, 01:59 UTC | 7h 4m |
| 2026-05-07 | FKH8021 | - | May 7, 13:25 UTC | May 7, 13:40 UTC | 15m |
| 2026-05-06 | FKH8013 | - | May 6, 16:30 UTC | May 7, 10:00 UTC | 17h 30m |
| 2026-05-06 | FKH8011 | - | May 6, 12:40 UTC | May 7, 10:00 UTC | 21h 20m |
| 2026-05-06 | FKH8011 | - | May 6, 07:05 UTC | May 6, 07:20 UTC | 15m |
| 2026-05-06 | FKH8010 | - | May 6, 03:20 UTC | May 6, 03:45 UTC | 25m |
| 2026-05-05 | FKH8063 | - | May 5, 15:45 UTC | May 5, 16:20 UTC | 35m |
| 2026-05-05 | FKH8062 | - | May 5, 07:10 UTC | May 5, 11:50 UTC | 4h 40m |
| 2026-05-05 | FKH8062 | - | May 5, 01:20 UTC | May 5, 01:35 UTC | 15m |
| 2026-05-04 | FKH8061 | - | May 4, 20:35 UTC | May 4, 21:00 UTC | 25m |
| 2026-05-04 | FKH8875 | - | May 4, 09:20 UTC | May 4, 15:55 UTC | 6h 35m |
| 2026-05-04 | FKH8874 | - | May 4, 06:55 UTC | May 4, 07:10 UTC | 15m |
| 2026-05-03 | FKH8874 | - | May 3, 18:50 UTC | May 4, 03:45 UTC | 8h 55m |
| 2026-05-03 | FKH8443 | - | May 3, 14:35 UTC | May 3, 15:05 UTC | 30m |
| 2026-05-02 | FKH8441 | - | May 2, 16:25 UTC | May 2, 18:55 UTC | 2h 30m |
| 2026-05-02 | FKH8051 | - | May 2, 09:40 UTC | May 2, 09:50 UTC | 10m |
| 2026-05-02 | FKH8051 | - | May 2, 00:20 UTC | May 2, 00:35 UTC | 15m |
| 2026-05-01 | FKH8023 | - | May 1, 21:15 UTC | May 1, 21:35 UTC | 20m |
| 2026-05-01 | FKH8023 | - | May 1, 16:00 UTC | May 1, 16:20 UTC | 20m |
| 2026-05-01 | FKH8021 | - | May 1, 06:10 UTC | May 1, 06:20 UTC | 10m |
| 2026-04-30 | FKH8021 | - | Apr 30, 21:10 UTC | May 1, 03:20 UTC | 6h 10m |
| 2026-04-30 | FKH8021 | - | Apr 30, 15:40 UTC | Apr 30, 15:55 UTC | 15m |
| 2026-04-30 | FKH8013 | - | Apr 30, 10:50 UTC | Apr 30, 11:15 UTC | 25m |
| 2026-04-29 | FKH8011 | - | Apr 29, 15:00 UTC | Apr 29, 21:15 UTC | 6h 15m |
| 2026-04-29 | FKH8011 | - | Apr 29, 09:10 UTC | Apr 29, 09:25 UTC | 15m |
| 2026-04-29 | FKH8443 | - | Apr 29, 03:00 UTC | Apr 29, 03:34 UTC | 35m |
| 2026-04-28 | FKH8441 | - | Apr 28, 03:20 UTC | Apr 29, 03:10 UTC | 23h 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 UK67014 page for operator, model, and routing details .