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
- Flights observed
- 63
- Distinct callsigns
- 16
- Country
- AF
- Last broadcast
- 8m ago
Current position
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 | Ariana Afghan Airlines | 7 | 2026-05-23 |
| AFG707 | Ariana Afghan Airlines | 7 | 2026-06-01 |
| AFG711 | - | 6 | 2026-05-16 |
| AFG416 | Ariana Afghan Airlines | 6 | 2026-05-17 |
| AFG402 | Ariana Afghan Airlines | 5 | 2026-05-30 |
| AFG720 | Ariana Afghan Airlines | 4 | 2026-05-12 |
| AFG719 | Ariana Afghan Airlines | 4 | 2026-05-12 |
| AFG713 | Ariana Afghan Airlines | 4 | 2026-05-06 |
| AFG712 | - | 4 | 2026-05-19 |
| AFG708 | Ariana Afghan Airlines | 4 | 2026-06-01 |
| AFG415 | Ariana Afghan Airlines | 3 | 2026-04-30 |
| AFG401 | Ariana Afghan Airlines | 3 | 2026-05-30 |
| AFG716 | Ariana Afghan Airlines | 2 | 2026-05-21 |
| AFG418 | Ariana Afghan Airlines | 2 | 2026-04-18 |
| AFG714 | Ariana Afghan Airlines | 1 | 2026-05-12 |
| AFG417 | Ariana Afghan Airlines | 1 | 2026-05-25 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-01 | AFG708 | SVO → KBL | Jun 1, 22:25 UTC | Jun 2, 19:45 UTC | 21h 20m |
| 2026-06-01 | AFG707 | KBL → SVO | Jun 1, 17:45 UTC | Jun 1, 19:15 UTC | 1h 30m |
| 2026-05-30 | AFG402 | DXB → KBL | May 30, 23:10 UTC | May 30, 23:30 UTC | 20m |
| 2026-05-30 | AFG401 | KBL → DXB | May 30, 19:10 UTC | May 30, 19:25 UTC | 15m |
| 2026-05-30 | AFG402 | DXB → KBL | May 30, 00:00 UTC | May 30, 00:25 UTC | 25m |
| 2026-05-29 | AFG401 | KBL → DXB | May 29, 17:55 UTC | May 29, 18:20 UTC | 25m |
| 2026-05-25 | AFG417 | KDH → JED | May 25, 16:05 UTC | May 25, 23:49 UTC | 7h 44m |
| 2026-05-23 | AFG715 | MZR → IST | May 23, 14:05 UTC | May 23, 16:55 UTC | 2h 50m |
| 2026-05-21 | AFG716 | IST → KBL | May 21, 21:55 UTC | May 22, 12:50 UTC | 14h 55m |
| 2026-05-21 | AFG715 | MZR → IST | May 21, 18:30 UTC | May 21, 18:40 UTC | 10m |
| 2026-05-21 | AFG715 | MZR → IST | May 21, 16:25 UTC | May 21, 17:45 UTC | 1h 20m |
| 2026-05-19 | AFG712 | - | May 19, 11:00 UTC | May 19, 14:15 UTC | 3h 15m |
| 2026-05-17 | AFG416 | JED → KBL | May 17, 18:30 UTC | May 18, 01:05 UTC | 6h 35m |
| 2026-05-16 | AFG711 | - | May 16, 12:05 UTC | May 16, 15:10 UTC | 3h 5m |
| 2026-05-14 | AFG716 | IST → KBL | May 14, 22:55 UTC | May 15, 13:40 UTC | 14h 45m |
| 2026-05-14 | AFG715 | MZR → IST | May 14, 16:25 UTC | May 14, 18:00 UTC | 1h 35m |
| 2026-05-13 | AFG715 | MZR → IST | May 13, 22:15 UTC | May 14, 18:00 UTC | 19h 45m |
| 2026-05-13 | AFG715 | MZR → IST | May 13, 17:55 UTC | May 14, 17:45 UTC | 23h 50m |
| 2026-05-12 | AFG714 | ESB → KBL | May 12, 23:50 UTC | May 13, 23:35 UTC | 23h 45m |
| 2026-05-12 | AFG720 | IST → KBL | May 12, 22:45 UTC | May 13, 19:10 UTC | 20h 25m |
| 2026-05-12 | AFG719 | KBL → IST | May 12, 16:25 UTC | May 12, 18:10 UTC | 1h 45m |
| 2026-05-11 | AFG707 | KBL → SVO | May 11, 20:15 UTC | May 11, 21:45 UTC | 1h 30m |
| 2026-05-08 | AFG720 | IST → KBL | May 8, 23:10 UTC | May 9, 16:15 UTC | 17h 5m |
| 2026-05-08 | AFG720 | IST → KBL | May 8, 17:50 UTC | May 9, 16:15 UTC | 22h 25m |
| 2026-05-08 | AFG719 | KBL → IST | May 8, 16:45 UTC | May 9, 15:45 UTC | 23h 0m |
| 2026-05-06 | AFG713 | ESB → KBL | May 6, 19:40 UTC | May 7, 01:35 UTC | 5h 55m |
| 2026-05-05 | AFG713 | ESB → KBL | May 5, 23:50 UTC | May 6, 21:05 UTC | 21h 14m |
| 2026-05-05 | AFG713 | ESB → KBL | May 5, 22:30 UTC | May 6, 21:05 UTC | 22h 34m |
| 2026-05-04 | AFG719 | KBL → IST | May 4, 22:30 UTC | May 5, 17:30 UTC | 19h 0m |
| 2026-05-03 | AFG707 | KBL → SVO | May 3, 23:50 UTC | May 4, 19:00 UTC | 19h 11m |
| 2026-05-03 | AFG416 | JED → KBL | May 3, 22:54 UTC | May 4, 19:00 UTC | 20h 6m |
| 2026-05-03 | AFG416 | JED → KBL | May 3, 16:34 UTC | May 4, 00:00 UTC | 7h 25m |
| 2026-05-01 | AFG402 | DXB → KBL | May 1, 23:05 UTC | May 1, 23:35 UTC | 30m |
| 2026-05-01 | AFG416 | JED → KBL | May 1, 01:00 UTC | May 1, 18:25 UTC | 17h 25m |
| 2026-04-30 | AFG416 | JED → KBL | Apr 30, 19:50 UTC | May 1, 18:25 UTC | 22h 35m |
| 2026-04-30 | AFG415 | KBL → JED | Apr 30, 19:00 UTC | May 1, 02:00 UTC | 7h 0m |
| 2026-04-30 | AFG415 | KBL → JED | Apr 30, 16:15 UTC | Apr 30, 16:45 UTC | 30m |
| 2026-04-29 | AFG713 | ESB → KBL | Apr 29, 18:00 UTC | Apr 30, 09:00 UTC | 14h 59m |
| 2026-04-27 | AFG708 | SVO → KBL | Apr 27, 23:00 UTC | Apr 28, 11:20 UTC | 12h 20m |
| 2026-04-27 | AFG707 | KBL → SVO | Apr 27, 18:25 UTC | Apr 27, 19:15 UTC | 50m |
| 2026-04-24 | AFG720 | IST → KBL | Apr 24, 23:10 UTC | Apr 25, 00:05 UTC | 55m |
| 2026-04-23 | AFG719 | KBL → IST | Apr 23, 22:30 UTC | Apr 24, 17:35 UTC | 19h 5m |
| 2026-04-23 | AFG715 | - | Apr 23, 04:15 UTC | Apr 23, 18:10 UTC | 13h 55m |
| 2026-04-22 | AFG712 | - | Apr 22, 09:50 UTC | Apr 23, 07:30 UTC | 21h 40m |
| 2026-04-22 | AFG712 | - | Apr 22, 07:50 UTC | Apr 23, 07:30 UTC | 23h 40m |
| 2026-04-22 | AFG711 | - | Apr 22, 07:35 UTC | Apr 23, 04:55 UTC | 21h 20m |
| 2026-04-21 | AFG402 | DXB → KBL | Apr 21, 23:45 UTC | Apr 22, 00:10 UTC | 25m |
| 2026-04-20 | AFG708 | SVO → KBL | Apr 20, 23:50 UTC | Apr 21, 18:45 UTC | 18h 55m |
| 2026-04-20 | AFG707 | KBL → SVO | Apr 20, 20:10 UTC | Apr 20, 21:45 UTC | 1h 35m |
| 2026-04-19 | AFG707 | KBL → SVO | Apr 19, 23:00 UTC | Apr 20, 21:45 UTC | 22h 45m |
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 .