sensors Mode-S transponder

700025

ICAO 24-bit transponder address · allocated to Afghanistan

Currently assigned to YA-KMJ · BOEING 737-300

Hex
700025
Octal
34000045
Decimal
7,340,069
Country
AF
Tail
YA-KMJ
Type
B733
No current signal · last broadcast 13h ago
Flights observed
80
Distinct callsigns
16
Country
AF
Last broadcast
13h ago

Last known position

Most recent position reported by Mode-S 700025.

Country allocation

The ICAO 24-bit address 700025 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 16 distinct

Callsign Airline Flights Last seen
KMF978 - 15 2026-07-10
KMF977 - 15 2026-07-13
KMF9011 - 13 2026-07-05
KMF9921 Kam Air 9 2026-07-01
KMF9012 - 8 2026-07-05
KMF965 - 3 2026-07-12
KMF9922 Kam Air 2 2026-07-02
KMF9919 - 2 2026-06-14
KMF9909 Kam Air 2 2026-06-03
KMF924 - 2 2026-07-12
KMF902 Kam Air 2 2026-04-24
KMF901 Kam Air 2 2026-04-24
KMF4402 Kam Air 2 2026-05-31
KMF9920 Kam Air 1 2026-06-15
KMF923 - 1 2026-07-11
KMF4401 Kam Air 1 2026-05-29

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-13 KMF977 - Jul 13, 17:55 UTCJul 13, 18:50 UTC55m
2026-07-12 KMF924 - Jul 12, 08:15 UTCJul 12, 08:45 UTC30m
2026-07-12 KMF965 - Jul 12, 05:50 UTCJul 12, 06:20 UTC30m
2026-07-11 KMF965 - Jul 11, 08:45 UTCJul 12, 06:20 UTC21h 35m
2026-07-11 KMF923 - Jul 11, 06:40 UTCJul 11, 07:05 UTC25m
2026-07-10 KMF978 - Jul 10, 20:35 UTCJul 10, 21:30 UTC55m
2026-07-10 KMF977 - Jul 10, 17:55 UTCJul 10, 18:50 UTC55m
2026-07-09 KMF924 - Jul 9, 07:55 UTCJul 9, 08:25 UTC30m
2026-07-09 KMF965 - Jul 9, 05:50 UTCJul 9, 06:15 UTC25m
2026-07-07 KMF978 - Jul 7, 20:25 UTCJul 8, 07:15 UTC10h 50m
2026-07-07 KMF977 - Jul 7, 18:30 UTCJul 7, 18:50 UTC20m
2026-07-05 KMF9012 - Jul 5, 21:15 UTCJul 5, 23:20 UTC2h 5m
2026-07-05 KMF9011 - Jul 5, 16:40 UTCJul 5, 18:10 UTC1h 30m
2026-07-04 KMF9011 - Jul 4, 21:20 UTCJul 5, 18:10 UTC20h 50m
2026-07-04 KMF9011 - Jul 4, 20:25 UTCJul 5, 18:10 UTC21h 45m
2026-07-04 KMF977 - Jul 4, 17:50 UTCJul 4, 18:45 UTC55m
2026-07-02 KMF978 - Jul 2, 20:15 UTCJul 2, 21:15 UTC1h 0m
2026-07-02 KMF9922 SAW → MZR Jul 2, 01:05 UTCJul 2, 19:00 UTC17h 55m
2026-07-01 KMF9921 MZR → SAW Jul 1, 21:05 UTCJul 1, 23:35 UTC2h 30m
2026-06-30 KMF9012 - Jun 30, 21:20 UTCJul 1, 21:15 UTC23h 55m
2026-06-30 KMF9011 - Jun 30, 16:40 UTCJun 30, 19:25 UTC2h 45m
2026-06-28 KMF978 - Jun 28, 20:04 UTCJun 28, 21:04 UTC1h 0m
2026-06-28 KMF977 KBL → DOH Jun 28, 17:19 UTCJun 28, 18:19 UTC1h 0m
2026-06-27 KMF977 KBL → DOH Jun 27, 21:19 UTCJun 28, 18:19 UTC21h 0m
2026-06-27 KMF978 - Jun 27, 20:24 UTCJun 28, 18:19 UTC21h 55m
2026-06-27 KMF977 KBL → DOH Jun 27, 18:04 UTCJun 27, 19:00 UTC55m
2026-06-26 KMF978 - Jun 26, 20:15 UTCJun 27, 19:00 UTC22h 45m
2026-06-26 KMF977 KBL → DOH Jun 26, 17:40 UTCJun 26, 18:34 UTC55m
2026-06-25 KMF977 KBL → DOH Jun 25, 21:20 UTCJun 26, 18:34 UTC21h 15m
2026-06-25 KMF977 KBL → DOH Jun 25, 20:34 UTCJun 26, 18:34 UTC22h 0m
2026-06-24 KMF977 KBL → DOH Jun 24, 21:19 UTCJun 25, 18:34 UTC21h 15m
2026-06-24 KMF9921 MZR → SAW Jun 24, 20:35 UTCJun 25, 18:34 UTC22h 0m
2026-06-23 KMF9921 MZR → SAW Jun 23, 23:19 UTCJun 24, 22:10 UTC22h 50m
2026-06-23 KMF9012 - Jun 23, 21:20 UTCJun 24, 21:14 UTC23h 55m
2026-06-23 KMF9012 - Jun 23, 21:14 UTCJun 23, 23:29 UTC2h 15m
2026-06-23 KMF9011 - Jun 23, 18:34 UTCJun 23, 18:55 UTC20m
2026-06-23 KMF9011 - Jun 23, 16:24 UTCJun 23, 17:54 UTC1h 30m
2026-06-21 KMF978 DOH → KBL Jun 21, 20:24 UTCJun 21, 21:14 UTC50m
2026-06-21 KMF977 KBL → DOH Jun 21, 17:54 UTCJun 21, 18:25 UTC30m
2026-06-20 KMF978 DOH → KBL Jun 20, 20:29 UTCJun 21, 18:25 UTC21h 55m
2026-06-20 KMF977 KBL → DOH Jun 20, 17:59 UTCJun 20, 18:34 UTC35m
2026-06-18 KMF9922 SAW → MZR Jun 18, 00:50 UTCJun 18, 02:50 UTC2h 0m
2026-06-17 KMF9921 MZR → SAW Jun 17, 21:05 UTCJun 17, 23:35 UTC2h 30m
2026-06-16 KMF9921 MZR → SAW Jun 16, 23:20 UTCJun 17, 23:15 UTC23h 55m
2026-06-16 KMF9012 - Jun 16, 22:30 UTCJun 17, 21:15 UTC22h 45m
2026-06-16 KMF9011 - Jun 16, 19:25 UTCJun 16, 19:35 UTC10m
2026-06-16 KMF9011 - Jun 16, 16:55 UTCJun 16, 18:35 UTC1h 40m
2026-06-15 KMF9920 SAW → KBL Jun 15, 01:40 UTCJun 15, 03:45 UTC2h 5m
2026-06-14 KMF9919 - Jun 14, 23:10 UTCJun 14, 23:25 UTC15m
2026-06-14 KMF9919 - Jun 14, 21:25 UTCJun 14, 22:35 UTC1h 10m

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-KMJ page for operator, model, and routing details .

Mode-S 700025 frequently asked

What is Mode-S code 700025?
700025 is an ICAO 24-bit transponder address. Allocated to Afghanistan. Assigned to YA-KMJ.
Where is Mode-S 700025 registered?
Mode-S code 700025 is allocated to Afghanistan (AF). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 700025 broadcasting right now?
No active broadcast right now. Last signal was 13h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 700025, octal 34000045, decimal 7,340,069.
What flights does 700025 operate?
Mode-S 700025 has broadcast 16 distinct callsigns, including KMF978, KMF977, KMF9011, KMF9921, KMF9012.