sensors Mode-S transponder
7000A4
ICAO 24-bit transponder address · allocated to Afghanistan
Currently assigned to YA-KAB · AIRBUS A-340-300
- Hex
- 7000A4
- Octal
- 34000244
- Decimal
- 7,340,196
- Country
- AF
- Tail
- YA-KAB
- Type
- A343
- Flights observed
- 169
- Distinct callsigns
- 20
- Country
- AF
- Last broadcast
- Jul 26, 01:35 UTC
Last known position
Country allocation
The ICAO 24-bit address 7000A4 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 |
|---|---|---|---|
| KMF9919 | Kam Air | 35 | 2026-07-25 |
| KMF9910 | Kam Air | 12 | 2026-07-24 |
| KMF994 | Kam Air | 8 | 2026-07-01 |
| KMF9920 | Kam Air | 7 | 2026-07-26 |
| KMF9909 | Kam Air | 7 | 2026-07-24 |
| KMF4401 | - | 7 | 2026-07-19 |
| KMF4402 | Kam Air | 5 | 2026-07-18 |
| KMF9011 | Kam Air | 4 | 2026-05-24 |
| KMF2104 | Kam Air | 4 | 2026-06-27 |
| KMF2092 | Kam Air | 4 | 2026-06-25 |
| KMF2088 | Kam Air | 4 | 2026-06-24 |
| KMF5501 | - | 3 | 2026-04-16 |
| KMF2064 | Kam Air | 3 | 2026-06-20 |
| KMF2060 | Kam Air | 3 | 2026-06-19 |
| KMF2050 | Kam Air | 3 | 2026-04-28 |
| KMF2040 | Kam Air | 3 | 2026-04-25 |
| KMF2130 | Kam Air | 2 | 2026-05-15 |
| KMF2112 | - | 2 | 2026-06-28 |
| KMF2108 | - | 2 | 2026-06-28 |
| KMF2106 | Kam Air | 2 | 2026-05-10 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | KMF9920 | SAW → KBL | Jul 26, 01:10 UTC | Jul 26, 01:35 UTC | 25m |
| 2026-07-25 | KMF9919 | KBL → SAW | Jul 25, 20:55 UTC | Jul 25, 22:15 UTC | 1h 20m |
| 2026-07-24 | KMF9910 | IST → KBL | Jul 24, 21:05 UTC | Jul 25, 21:00 UTC | 23h 55m |
| 2026-07-24 | KMF9910 | IST → KBL | Jul 24, 20:35 UTC | Jul 24, 22:30 UTC | 1h 55m |
| 2026-07-24 | KMF9909 | KBL → IST | Jul 24, 01:30 UTC | Jul 24, 18:20 UTC | 16h 50m |
| 2026-07-23 | KMF9919 | KBL → SAW | Jul 23, 23:10 UTC | Jul 23, 23:20 UTC | 10m |
| 2026-07-23 | KMF9919 | KBL → SAW | Jul 23, 20:50 UTC | Jul 23, 22:15 UTC | 1h 25m |
| 2026-07-22 | KMF9910 | - | Jul 22, 21:05 UTC | Jul 23, 21:00 UTC | 23h 55m |
| 2026-07-22 | KMF9910 | - | Jul 22, 20:45 UTC | Jul 22, 22:35 UTC | 1h 50m |
| 2026-07-22 | KMF9909 | KBL → IST | Jul 22, 01:20 UTC | Jul 22, 18:20 UTC | 17h 0m |
| 2026-07-21 | KMF9919 | - | Jul 21, 20:55 UTC | Jul 21, 23:15 UTC | 2h 20m |
| 2026-07-21 | KMF9919 | - | Jul 21, 01:10 UTC | Jul 21, 23:15 UTC | 22h 5m |
| 2026-07-20 | KMF9919 | - | Jul 20, 03:05 UTC | Jul 20, 22:10 UTC | 19h 5m |
| 2026-07-20 | KMF9919 | - | Jul 20, 01:20 UTC | Jul 20, 22:10 UTC | 20h 50m |
| 2026-07-19 | KMF9919 | - | Jul 19, 09:45 UTC | Jul 19, 23:05 UTC | 13h 20m |
| 2026-07-19 | KMF4401 | - | Jul 19, 06:50 UTC | Jul 19, 07:30 UTC | 40m |
| 2026-07-18 | KMF4402 | DEL → KBL | Jul 18, 09:35 UTC | Jul 19, 07:30 UTC | 21h 55m |
| 2026-07-18 | KMF4401 | - | Jul 18, 06:35 UTC | Jul 18, 07:25 UTC | 50m |
| 2026-07-17 | KMF9910 | - | Jul 17, 20:29 UTC | Jul 17, 21:00 UTC | 30m |
| 2026-07-17 | KMF9920 | - | Jul 17, 01:29 UTC | Jul 17, 16:55 UTC | 15h 25m |
| 2026-07-16 | KMF9919 | - | Jul 16, 20:49 UTC | Jul 16, 23:15 UTC | 2h 25m |
| 2026-07-15 | KMF9910 | - | Jul 15, 21:15 UTC | Jul 16, 21:00 UTC | 23h 45m |
| 2026-07-15 | KMF9910 | - | Jul 15, 20:25 UTC | Jul 15, 22:20 UTC | 1h 55m |
| 2026-07-15 | KMF9920 | - | Jul 15, 01:25 UTC | Jul 15, 17:05 UTC | 15h 40m |
| 2026-07-14 | KMF9919 | - | Jul 14, 03:05 UTC | Jul 14, 22:10 UTC | 19h 5m |
| 2026-07-14 | KMF9920 | - | Jul 14, 01:25 UTC | Jul 14, 22:10 UTC | 20h 45m |
| 2026-07-13 | KMF9919 | - | Jul 13, 20:50 UTC | Jul 13, 23:10 UTC | 2h 20m |
| 2026-07-13 | KMF9919 | - | Jul 13, 03:05 UTC | Jul 13, 23:10 UTC | 20h 5m |
| 2026-07-13 | KMF9919 | - | Jul 13, 01:30 UTC | Jul 13, 23:10 UTC | 21h 40m |
| 2026-07-12 | KMF9919 | - | Jul 12, 22:50 UTC | Jul 12, 23:15 UTC | 25m |
| 2026-07-12 | KMF9919 | - | Jul 12, 03:05 UTC | Jul 12, 22:15 UTC | 19h 10m |
| 2026-07-12 | KMF9920 | - | Jul 12, 01:30 UTC | Jul 12, 22:15 UTC | 20h 45m |
| 2026-07-11 | KMF9919 | - | Jul 11, 23:00 UTC | Jul 11, 23:10 UTC | 10m |
| 2026-07-11 | KMF9919 | - | Jul 11, 09:50 UTC | Jul 11, 22:05 UTC | 12h 15m |
| 2026-07-10 | KMF4401 | - | Jul 10, 20:35 UTC | Jul 11, 08:05 UTC | 11h 30m |
| 2026-07-10 | KMF9909 | - | Jul 10, 01:25 UTC | Jul 10, 17:10 UTC | 15h 45m |
| 2026-07-09 | KMF9919 | - | Jul 9, 20:50 UTC | Jul 9, 23:20 UTC | 2h 30m |
| 2026-07-08 | KMF9910 | - | Jul 8, 21:05 UTC | Jul 9, 21:00 UTC | 23h 55m |
| 2026-07-08 | KMF9910 | - | Jul 8, 20:50 UTC | Jul 8, 22:45 UTC | 1h 55m |
| 2026-07-08 | KMF9909 | - | Jul 8, 01:35 UTC | Jul 8, 18:05 UTC | 16h 30m |
| 2026-07-07 | KMF9919 | - | Jul 7, 03:05 UTC | Jul 7, 22:20 UTC | 19h 15m |
| 2026-07-07 | KMF9919 | - | Jul 7, 01:50 UTC | Jul 7, 22:20 UTC | 20h 30m |
| 2026-07-06 | KMF9919 | - | Jul 6, 23:00 UTC | Jul 6, 23:20 UTC | 20m |
| 2026-07-06 | KMF9919 | - | Jul 6, 03:05 UTC | Jul 6, 22:20 UTC | 19h 15m |
| 2026-07-06 | KMF9920 | - | Jul 6, 01:45 UTC | Jul 6, 22:20 UTC | 20h 35m |
| 2026-07-05 | KMF9919 | - | Jul 5, 20:55 UTC | Jul 5, 23:20 UTC | 2h 25m |
| 2026-07-05 | KMF9919 | - | Jul 5, 01:50 UTC | Jul 5, 23:20 UTC | 21h 30m |
| 2026-07-04 | KMF9919 | - | Jul 4, 23:00 UTC | Jul 4, 23:15 UTC | 15m |
| 2026-07-04 | KMF9919 | - | Jul 4, 20:50 UTC | Jul 4, 22:15 UTC | 1h 25m |
| 2026-07-03 | KMF9910 | - | Jul 3, 20:40 UTC | Jul 3, 22:30 UTC | 1h 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 YA-KAB page for operator, model, and routing details .