sensors Mode-S transponder
700011
ICAO 24-bit transponder address · allocated to Afghanistan
Currently assigned to YA-KME · AIRBUS A-340-300
- Hex
- 700011
- Octal
- 34000021
- Decimal
- 7,340,049
- Country
- AF
- Tail
- YA-KME
- Type
- A343
- Flights observed
- 81
- Distinct callsigns
- 19
- Country
- AF
- Last broadcast
- 8h ago
Last known position
Country allocation
The ICAO 24-bit address 700011 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 19 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| KMF9919 | Kam Air | 20 | 2026-05-28 |
| KMF994 | Kam Air | 9 | 2026-05-06 |
| KMF9909 | Kam Air | 7 | 2026-05-23 |
| KMF901 | Kam Air | 6 | 2026-05-04 |
| KMF9920 | Kam Air | 5 | 2026-05-29 |
| KMF4401 | Kam Air | 5 | 2026-05-25 |
| KMF4402 | Kam Air | 4 | 2026-05-24 |
| KMF2023 | Kam Air | 4 | 2026-04-21 |
| KMF2016 | Kam Air | 4 | 2026-04-20 |
| KMF2007 | Kam Air | 3 | 2026-04-19 |
| KMF9910 | Kam Air | 2 | 2026-05-08 |
| KMF902 | Kam Air | 2 | 2026-05-04 |
| KMF2031 | Kam Air | 2 | 2026-04-22 |
| KMF2011 | Kam Air | 2 | 2026-04-19 |
| KMF2008 | Kam Air | 2 | 2026-04-19 |
| KMF995 | Kam Air | 1 | 2026-05-13 |
| KMF993 | Kam Air | 1 | 2026-04-16 |
| KMF2024 | Kam Air | 1 | 2026-04-21 |
| KMF2004 | Kam Air | 1 | 2026-06-02 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | KMF2004 | MED → MZR | Jun 2, 11:25 UTC | Jun 2, 12:30 UTC | 1h 5m |
| 2026-05-29 | KMF9920 | SAW → KBL | May 29, 01:35 UTC | May 29, 03:30 UTC | 1h 55m |
| 2026-05-28 | KMF9919 | KBL → SAW | May 28, 21:15 UTC | May 28, 23:35 UTC | 2h 20m |
| 2026-05-26 | KMF9919 | KBL → SAW | May 26, 21:04 UTC | May 27, 03:04 UTC | 6h 0m |
| 2026-05-26 | KMF9919 | KBL → SAW | May 26, 02:19 UTC | May 26, 22:29 UTC | 20h 10m |
| 2026-05-26 | KMF9919 | KBL → SAW | May 26, 01:40 UTC | May 26, 22:29 UTC | 20h 50m |
| 2026-05-25 | KMF9919 | KBL → SAW | May 25, 10:20 UTC | May 25, 22:19 UTC | 11h 59m |
| 2026-05-25 | KMF4401 | KBL → DEL | May 25, 06:55 UTC | May 25, 07:40 UTC | 45m |
| 2026-05-24 | KMF4402 | DEL → KBL | May 24, 10:20 UTC | May 25, 07:40 UTC | 21h 20m |
| 2026-05-23 | KMF4401 | KBL → DEL | May 23, 21:55 UTC | May 24, 07:40 UTC | 9h 45m |
| 2026-05-23 | KMF9909 | KBL → IST | May 23, 17:30 UTC | May 23, 17:40 UTC | 10m |
| 2026-05-22 | KMF9909 | KBL → IST | May 22, 22:20 UTC | May 23, 16:50 UTC | 18h 30m |
| 2026-05-22 | KMF9909 | KBL → IST | May 22, 21:50 UTC | May 23, 16:50 UTC | 18h 59m |
| 2026-05-22 | KMF9909 | KBL → IST | May 22, 17:55 UTC | May 22, 18:05 UTC | 10m |
| 2026-05-17 | KMF9920 | SAW → KBL | May 17, 01:50 UTC | May 17, 02:55 UTC | 1h 5m |
| 2026-05-16 | KMF9919 | KBL → SAW | May 16, 20:45 UTC | May 16, 22:05 UTC | 1h 20m |
| 2026-05-15 | KMF9919 | KBL → SAW | May 15, 22:20 UTC | May 16, 22:05 UTC | 23h 45m |
| 2026-05-15 | KMF9909 | KBL → IST | May 15, 15:40 UTC | May 15, 22:30 UTC | 6h 50m |
| 2026-05-14 | KMF9919 | KBL → SAW | May 14, 20:45 UTC | May 15, 17:00 UTC | 20h 14m |
| 2026-05-13 | KMF995 | KBL → RUH | May 13, 07:30 UTC | May 13, 11:45 UTC | 4h 15m |
| 2026-05-11 | KMF9919 | KBL → SAW | May 11, 20:55 UTC | May 12, 03:00 UTC | 6h 5m |
| 2026-05-10 | KMF9920 | SAW → KBL | May 10, 01:55 UTC | May 10, 03:14 UTC | 1h 20m |
| 2026-05-09 | KMF9919 | KBL → SAW | May 9, 21:00 UTC | May 9, 22:20 UTC | 1h 20m |
| 2026-05-08 | KMF9919 | KBL → SAW | May 8, 22:20 UTC | May 9, 22:15 UTC | 23h 55m |
| 2026-05-08 | KMF9910 | IST → KBL | May 8, 21:45 UTC | May 8, 22:35 UTC | 50m |
| 2026-05-08 | KMF9909 | KBL → IST | May 8, 01:59 UTC | May 8, 17:00 UTC | 15h 0m |
| 2026-05-07 | KMF9919 | KBL → SAW | May 7, 21:05 UTC | May 7, 22:25 UTC | 1h 20m |
| 2026-05-07 | KMF9919 | KBL → SAW | May 7, 02:20 UTC | May 7, 22:25 UTC | 20h 5m |
| 2026-05-07 | KMF9919 | KBL → SAW | May 7, 02:00 UTC | May 7, 22:25 UTC | 20h 25m |
| 2026-05-06 | KMF994 | JED → KBL | May 6, 11:15 UTC | May 7, 02:20 UTC | 15h 4m |
| 2026-05-06 | KMF994 | JED → KBL | May 6, 07:40 UTC | May 7, 02:20 UTC | 18h 39m |
| 2026-05-04 | KMF902 | DXB → KBL | May 4, 23:50 UTC | May 5, 00:00 UTC | 10m |
| 2026-05-04 | KMF901 | KBL → DXB | May 4, 20:10 UTC | May 4, 20:40 UTC | 30m |
| 2026-05-03 | KMF901 | KBL → DXB | May 3, 23:15 UTC | May 4, 16:00 UTC | 16h 45m |
| 2026-05-03 | KMF901 | KBL → DXB | May 3, 15:25 UTC | May 3, 15:55 UTC | 30m |
| 2026-05-02 | KMF901 | KBL → DXB | May 2, 15:40 UTC | May 2, 16:05 UTC | 25m |
| 2026-05-01 | KMF9910 | IST → KBL | May 1, 21:30 UTC | May 1, 22:40 UTC | 1h 10m |
| 2026-05-01 | KMF9909 | KBL → IST | May 1, 02:10 UTC | May 1, 17:30 UTC | 15h 20m |
| 2026-04-30 | KMF9919 | KBL → SAW | Apr 30, 21:10 UTC | Apr 30, 22:35 UTC | 1h 25m |
| 2026-04-30 | KMF9919 | KBL → SAW | Apr 30, 00:55 UTC | Apr 30, 22:35 UTC | 21h 40m |
| 2026-04-29 | KMF994 | JED → KBL | Apr 29, 09:55 UTC | Apr 30, 01:50 UTC | 15h 54m |
| 2026-04-29 | KMF4401 | KBL → DEL | Apr 29, 06:55 UTC | Apr 29, 07:35 UTC | 40m |
| 2026-04-28 | KMF902 | DXB → KBL | Apr 28, 23:25 UTC | Apr 28, 23:50 UTC | 25m |
| 2026-04-28 | KMF901 | KBL → DXB | Apr 28, 15:25 UTC | Apr 28, 15:45 UTC | 20m |
| 2026-04-27 | KMF4402 | DEL → KBL | Apr 27, 10:00 UTC | Apr 27, 10:35 UTC | 35m |
| 2026-04-26 | KMF4401 | KBL → DEL | Apr 26, 23:25 UTC | Apr 27, 08:00 UTC | 8h 35m |
| 2026-04-26 | KMF901 | KBL → DXB | Apr 26, 15:25 UTC | Apr 26, 15:45 UTC | 20m |
| 2026-04-26 | KMF9920 | SAW → KBL | Apr 26, 02:00 UTC | Apr 26, 03:05 UTC | 1h 5m |
| 2026-04-25 | KMF9919 | KBL → SAW | Apr 25, 21:00 UTC | Apr 25, 22:30 UTC | 1h 30m |
| 2026-04-24 | KMF4402 | DEL → KBL | Apr 24, 11:45 UTC | Apr 24, 12:20 UTC | 35m |
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-KME page for operator, model, and routing details .