sensors Mode-S transponder
700015
ICAO 24-bit transponder address · allocated to Afghanistan
Currently assigned to YA-KMH · AIRBUS A-340-300
- Hex
- 700015
- Octal
- 34000025
- Decimal
- 7,340,053
- Country
- AF
- Tail
- YA-KMH
- Type
- A343
- Flights observed
- 88
- Distinct callsigns
- 20
- Country
- AF
- Last broadcast
- 5h ago
Last known position
Country allocation
The ICAO 24-bit address 700015 falls within the block assigned to Afghanistan (AF) by ICAO Annex 10, Volume III. Every aircraft registered in Afghanistan 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 |
|---|---|---|---|
| KMF2018 | Kam Air | 6 | 2026-04-20 |
| KMF2120 | Kam Air | 5 | 2026-05-13 |
| KMF2100 | - | 4 | 2026-05-09 |
| KMF2088 | Kam Air | 4 | 2026-05-07 |
| KMF2072 | Kam Air | 4 | 2026-05-05 |
| KMF2056 | Kam Air | 4 | 2026-04-30 |
| KMF2006 | Kam Air | 4 | 2026-04-18 |
| KMF9919 | Kam Air | 3 | 2026-06-01 |
| KMF2038 | Kam Air | 3 | 2026-04-24 |
| KMF2030 | Kam Air | 3 | 2026-04-22 |
| KMF2026 | Kam Air | 3 | 2026-04-22 |
| KMF2010 | Kam Air | 3 | 2026-04-19 |
| KMF9920 | Kam Air | 2 | 2026-06-02 |
| KMF9909 | Kam Air | 2 | 2026-04-15 |
| KMF901 | Kam Air | 2 | 2026-06-02 |
| KMF2116 | Kam Air | 2 | 2026-05-11 |
| KMF2108 | Kam Air | 2 | 2026-05-11 |
| KMF2064 | Kam Air | 2 | 2026-05-03 |
| KMF2059 | Kam Air | 2 | 2026-05-02 |
| KMF2058 | Kam Air | 2 | 2026-05-01 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | KMF901 | KBL → DXB | Jun 2, 16:35 UTC | Jun 2, 16:55 UTC | 20m |
| 2026-06-02 | KMF9920 | SAW → KBL | Jun 2, 01:40 UTC | Jun 2, 03:30 UTC | 1h 50m |
| 2026-06-01 | KMF9919 | KBL → SAW | Jun 1, 21:10 UTC | Jun 1, 23:30 UTC | 2h 20m |
| 2026-05-30 | KMF5502 | - | May 30, 09:40 UTC | May 30, 10:05 UTC | 25m |
| 2026-05-21 | KMF5501 | - | May 21, 07:10 UTC | May 21, 07:35 UTC | 25m |
| 2026-05-20 | KMF902 | DXB → KBL | May 20, 23:25 UTC | May 20, 23:50 UTC | 25m |
| 2026-05-20 | KMF901 | KBL → DXB | May 20, 15:35 UTC | May 20, 16:00 UTC | 25m |
| 2026-05-17 | KMF2136 | JED → KBL | May 17, 00:45 UTC | May 17, 01:40 UTC | 55m |
| 2026-05-15 | KMF2132 | JED → KBL | May 15, 20:00 UTC | May 15, 21:00 UTC | 1h 0m |
| 2026-05-14 | KMF2128 | JED → MZR | May 14, 21:25 UTC | May 15, 21:00 UTC | 23h 34m |
| 2026-05-13 | KMF2124 | JED → KBL | May 13, 23:35 UTC | May 14, 22:20 UTC | 22h 45m |
| 2026-05-13 | KMF2120 | JED → KDH | May 13, 09:25 UTC | May 14, 00:35 UTC | 15h 10m |
| 2026-05-13 | KMF2120 | JED → KDH | May 13, 03:30 UTC | May 14, 00:35 UTC | 21h 5m |
| 2026-05-13 | KMF2120 | JED → KDH | May 13, 02:55 UTC | May 14, 00:35 UTC | 21h 40m |
| 2026-05-12 | KMF2120 | JED → KDH | May 12, 13:35 UTC | May 13, 10:20 UTC | 20h 45m |
| 2026-05-12 | KMF2120 | JED → KDH | May 12, 12:50 UTC | May 13, 10:20 UTC | 21h 30m |
| 2026-05-11 | KMF2116 | JED → KBL | May 11, 22:35 UTC | May 12, 13:40 UTC | 15h 6m |
| 2026-05-11 | KMF2116 | JED → KBL | May 11, 16:15 UTC | May 12, 13:40 UTC | 21h 26m |
| 2026-05-11 | KMF2108 | JED → KDH | May 11, 08:25 UTC | May 11, 22:35 UTC | 14h 10m |
| 2026-05-10 | KMF2108 | JED → KDH | May 10, 13:19 UTC | May 11, 09:20 UTC | 20h 0m |
| 2026-05-10 | KMF2104 | JED → KBL | May 10, 12:30 UTC | May 11, 09:20 UTC | 20h 50m |
| 2026-05-09 | KMF2100 | - | May 9, 22:30 UTC | May 10, 13:25 UTC | 14h 55m |
| 2026-05-09 | KMF2100 | - | May 9, 15:50 UTC | May 10, 13:25 UTC | 21h 35m |
| 2026-05-09 | KMF2100 | - | May 9, 09:20 UTC | May 10, 06:10 UTC | 20h 50m |
| 2026-05-09 | KMF2100 | - | May 9, 08:30 UTC | May 10, 06:10 UTC | 21h 40m |
| 2026-05-08 | KMF2096 | JED → KDH | May 8, 13:20 UTC | May 9, 09:30 UTC | 20h 10m |
| 2026-05-08 | KMF2092 | JED → KDH | May 8, 12:30 UTC | May 9, 09:30 UTC | 21h 0m |
| 2026-05-07 | KMF2088 | JED → KDH | May 7, 21:25 UTC | May 8, 13:30 UTC | 16h 5m |
| 2026-05-07 | KMF2088 | JED → KDH | May 7, 15:00 UTC | May 8, 13:15 UTC | 22h 15m |
| 2026-05-07 | KMF2088 | JED → KDH | May 7, 06:00 UTC | May 7, 22:30 UTC | 16h 30m |
| 2026-05-06 | KMF2088 | JED → KDH | May 6, 23:50 UTC | May 7, 22:30 UTC | 22h 40m |
| 2026-05-06 | KMF2084 | JED → KDH | May 6, 15:30 UTC | May 7, 15:05 UTC | 23h 35m |
| 2026-05-05 | KMF2076 | JED → KBL | May 5, 22:45 UTC | May 6, 16:30 UTC | 17h 45m |
| 2026-05-05 | KMF2072 | JED → MZR | May 5, 07:40 UTC | May 5, 23:45 UTC | 16h 5m |
| 2026-05-05 | KMF2072 | JED → MZR | May 5, 02:01 UTC | May 5, 23:45 UTC | 21h 45m |
| 2026-05-04 | KMF2072 | JED → MZR | May 4, 13:35 UTC | May 5, 08:35 UTC | 19h 1m |
| 2026-05-04 | KMF2072 | JED → MZR | May 4, 12:45 UTC | May 5, 08:35 UTC | 19h 51m |
| 2026-05-04 | KMF2068 | JED → MZR | May 4, 07:00 UTC | May 5, 02:01 UTC | 19h 1m |
| 2026-05-03 | KMF2064 | MED → KBL | May 3, 20:00 UTC | May 4, 13:50 UTC | 17h 50m |
| 2026-05-03 | KMF2064 | MED → KBL | May 3, 15:20 UTC | May 4, 13:50 UTC | 22h 30m |
| 2026-05-03 | KMF2063 | HEA → MED | May 3, 14:15 UTC | May 4, 13:00 UTC | 22h 45m |
| 2026-05-02 | KMF2059 | HEA → MED | May 2, 03:25 UTC | May 2, 10:30 UTC | 7h 5m |
| 2026-05-01 | KMF2059 | HEA → MED | May 1, 07:25 UTC | May 2, 04:35 UTC | 21h 10m |
| 2026-05-01 | KMF2058 | MED → HEA | May 1, 06:40 UTC | May 2, 04:35 UTC | 21h 55m |
| 2026-05-01 | KMF2058 | MED → HEA | May 1, 01:00 UTC | May 1, 07:40 UTC | 6h 40m |
| 2026-04-30 | KMF2057 | HEA → MED | Apr 30, 07:20 UTC | May 1, 07:00 UTC | 23h 41m |
| 2026-04-30 | KMF2056 | MED → HEA | Apr 30, 06:20 UTC | May 1, 02:05 UTC | 19h 45m |
| 2026-04-30 | KMF2056 | MED → HEA | Apr 30, 01:30 UTC | May 1, 01:10 UTC | 23h 40m |
| 2026-04-30 | KMF2056 | MED → HEA | Apr 30, 00:50 UTC | Apr 30, 07:20 UTC | 6h 30m |
| 2026-04-29 | KMF2056 | MED → HEA | Apr 29, 07:20 UTC | Apr 30, 07:15 UTC | 23h 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 YA-KMH page for operator, model, and routing details .