Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

700017

ICAO 24-bit transponder address · allocated to Afghanistan

Currently assigned to YA-FGA · BOEING 737-500

Hex
700017
Octal
34000027
Decimal
7,340,055
Country
AF
Tail
YA-FGA
Type
B735
No current signal · last broadcast 2d ago
Flights observed
134
Distinct callsigns
16
Country
AF
Last broadcast
2d ago

Last known position

Most recent position reported by Mode-S 700017.

Country allocation

The ICAO 24-bit address 700017 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
AFG715 - 19 2026-06-18
AFG719 - 18 2026-06-24
AFG707 - 15 2026-07-06
AFG713 - 13 2026-07-15
AFG416 - 13 2026-06-28
AFG720 - 10 2026-06-24
AFG711 - 8 2026-06-20
AFG402 - 6 2026-06-26
AFG716 - 5 2026-06-18
AFG712 - 5 2026-06-20
AFG708 - 5 2026-07-06
AFG415 Ariana Afghan Airlines 5 2026-06-14
AFG401 - 5 2026-06-27
AFG714 Ariana Afghan Airlines 4 2026-06-25
AFG418 Ariana Afghan Airlines 2 2026-04-18
AFG417 Ariana Afghan Airlines 1 2026-05-25

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-15 AFG713 - Jul 15, 18:05 UTCJul 15, 23:20 UTC5h 15m
2026-07-08 AFG713 - Jul 8, 17:50 UTCJul 8, 23:30 UTC5h 40m
2026-07-06 AFG708 - Jul 6, 23:00 UTCJul 7, 00:35 UTC1h 35m
2026-07-06 AFG707 - Jul 6, 20:40 UTCJul 6, 20:55 UTC15m
2026-07-06 AFG707 - Jul 6, 19:05 UTCJul 6, 19:55 UTC50m
2026-06-29 AFG708 - Jun 29, 22:49 UTCJun 30, 00:09 UTC1h 20m
2026-06-29 AFG707 - Jun 29, 18:39 UTCJun 29, 20:15 UTC1h 35m
2026-06-29 AFG707 - Jun 29, 00:39 UTCJun 29, 20:15 UTC19h 35m
2026-06-28 AFG416 - Jun 28, 18:40 UTCJun 29, 01:44 UTC7h 5m
2026-06-28 AFG416 - Jun 28, 01:50 UTCJun 29, 01:44 UTC23h 55m
2026-06-27 AFG401 - Jun 27, 19:19 UTCJun 27, 19:49 UTC30m
2026-06-26 AFG401 - Jun 26, 23:49 UTCJun 27, 19:49 UTC20h 0m
2026-06-26 AFG402 - Jun 26, 23:30 UTCJun 27, 19:49 UTC20h 20m
2026-06-26 AFG416 - Jun 26, 00:10 UTCJun 26, 18:24 UTC18h 15m
2026-06-25 AFG416 - Jun 25, 18:15 UTCJun 26, 01:20 UTC7h 5m
2026-06-25 AFG416 - Jun 25, 03:50 UTCJun 26, 01:20 UTC21h 30m
2026-06-25 AFG714 ESB → KBL Jun 25, 03:04 UTCJun 26, 01:20 UTC22h 15m
2026-06-24 AFG714 ESB → KBL Jun 24, 23:50 UTCJun 25, 19:15 UTC19h 25m
2026-06-24 AFG713 ESB → KBL Jun 24, 23:20 UTCJun 25, 19:15 UTC19h 55m
2026-06-24 AFG713 ESB → KBL Jun 24, 03:55 UTCJun 25, 03:44 UTC23h 50m
2026-06-24 AFG720 - Jun 24, 03:04 UTCJun 25, 00:44 UTC21h 40m
2026-06-24 AFG719 - Jun 24, 00:34 UTCJun 24, 00:59 UTC25m
2026-06-23 AFG719 - Jun 23, 10:44 UTCJun 23, 23:55 UTC13h 10m
2026-06-22 AFG707 KBL → SVO Jun 22, 20:55 UTCJun 22, 22:19 UTC1h 25m
2026-06-21 AFG707 KBL → SVO Jun 21, 23:50 UTCJun 22, 22:19 UTC22h 30m
2026-06-21 AFG416 - Jun 21, 23:30 UTCJun 22, 21:45 UTC22h 15m
2026-06-21 AFG416 - Jun 21, 17:10 UTCJun 22, 00:29 UTC7h 20m
2026-06-20 AFG712 - Jun 20, 20:55 UTCJun 21, 17:29 UTC20h 35m
2026-06-20 AFG711 - Jun 20, 18:34 UTCJun 20, 19:15 UTC40m
2026-06-19 AFG711 - Jun 19, 23:19 UTCJun 20, 19:15 UTC19h 55m
2026-06-18 AFG716 - Jun 18, 23:50 UTCJun 19, 18:30 UTC18h 39m
2026-06-18 AFG716 - Jun 18, 22:35 UTCJun 19, 18:30 UTC19h 54m
2026-06-18 AFG715 - Jun 18, 18:15 UTCJun 18, 20:50 UTC2h 35m
2026-06-18 AFG715 - Jun 18, 00:05 UTCJun 18, 20:50 UTC20h 45m
2026-06-17 AFG715 - Jun 17, 20:10 UTCJun 18, 19:45 UTC23h 35m
2026-06-16 AFG713 ESB → KBL Jun 16, 23:50 UTCJun 17, 21:45 UTC21h 55m
2026-06-16 AFG720 IST → KBL Jun 16, 21:55 UTCJun 17, 21:45 UTC23h 50m
2026-06-16 AFG719 KBL → IST Jun 16, 17:45 UTCJun 16, 20:25 UTC2h 41m
2026-06-15 AFG719 KBL → IST Jun 15, 23:50 UTCJun 16, 20:25 UTC20h 36m
2026-06-15 AFG719 KBL → IST Jun 15, 22:30 UTCJun 16, 20:25 UTC21h 56m
2026-06-15 AFG707 KBL → SVO Jun 15, 17:04 UTCJun 15, 18:45 UTC1h 40m
2026-06-14 AFG415 KBL → JED Jun 14, 18:00 UTCJun 15, 17:45 UTC23h 45m
2026-06-13 AFG716 - Jun 13, 23:50 UTCJun 14, 19:05 UTC19h 15m
2026-06-13 AFG715 - Jun 13, 19:35 UTCJun 13, 22:10 UTC2h 35m
2026-06-12 AFG715 - Jun 12, 23:50 UTCJun 13, 22:10 UTC22h 19m
2026-06-12 AFG715 - Jun 12, 21:50 UTCJun 13, 21:45 UTC23h 54m
2026-06-12 AFG719 KBL → IST Jun 12, 00:05 UTCJun 12, 19:45 UTC19h 41m
2026-06-11 AFG719 KBL → IST Jun 11, 23:10 UTCJun 12, 19:45 UTC20h 36m
2026-06-11 AFG715 MZR → IST Jun 11, 18:30 UTCJun 11, 20:05 UTC1h 35m
2026-06-10 AFG715 MZR → IST Jun 10, 23:50 UTCJun 11, 20:05 UTC20h 15m

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

Mode-S 700017 frequently asked

What is Mode-S code 700017?
700017 is an ICAO 24-bit transponder address. Allocated to Afghanistan. Assigned to YA-FGA.
Where is Mode-S 700017 registered?
Mode-S code 700017 is allocated to Afghanistan (AF). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 700017 broadcasting right now?
No active broadcast right now. Last signal was 2d ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 700017, octal 34000027, decimal 7,340,055.
What flights does 700017 operate?
Mode-S 700017 has broadcast 16 distinct callsigns, including AFG715, AFG719, AFG707, AFG713, AFG416.