sensors Mode-S transponder
700007
ICAO 24-bit transponder address · allocated to Afghanistan
Currently assigned to YA-CAV · AIRBUS A-310
- Hex
- 700007
- Octal
- 34000007
- Decimal
- 7,340,039
- Country
- AF
- Tail
- YA-CAV
- Type
- A310
- Flights observed
- 127
- Distinct callsigns
- 20
- Country
- AF
- Last broadcast
- 4d ago
Last known position
Country allocation
The ICAO 24-bit address 700007 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 |
|---|---|---|---|
| AFG719 | - | 8 | 2026-06-30 |
| AFG311 | - | 7 | 2026-07-10 |
| AFG312 | - | 6 | 2026-07-10 |
| AFG713 | Ariana Afghan Airlines | 4 | 2026-07-01 |
| FG2035 | - | 3 | 2026-06-20 |
| AFG720 | - | 3 | 2026-07-01 |
| AFG714 | Ariana Afghan Airlines | 3 | 2026-07-02 |
| AFG416 | - | 3 | 2026-07-05 |
| AFG2452 | - | 3 | 2026-06-29 |
| AFG2450 | - | 3 | 2026-06-28 |
| AFG2445 | - | 3 | 2026-06-25 |
| AFG2441 | - | 3 | 2026-06-22 |
| AFG2438 | - | 3 | 2026-06-22 |
| AFG2127 | - | 3 | 2026-05-01 |
| AFG2118 | - | 3 | 2026-04-26 |
| AFG2108 | - | 3 | 2026-04-21 |
| AFG2102 | - | 3 | 2026-04-19 |
| AFG415 | - | 2 | 2026-07-02 |
| AFG414 | Ariana Afghan Airlines | 2 | 2026-04-15 |
| AFG2454 | - | 2 | 2026-06-29 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-10 | AFG312 | - | Jul 10, 08:50 UTC | Jul 10, 09:25 UTC | 35m |
| 2026-07-10 | AFG311 | - | Jul 10, 06:25 UTC | Jul 10, 07:10 UTC | 45m |
| 2026-07-05 | AFG416 | - | Jul 5, 16:40 UTC | Jul 6, 00:45 UTC | 8h 5m |
| 2026-07-04 | AFG312 | - | Jul 4, 14:10 UTC | Jul 4, 14:50 UTC | 40m |
| 2026-07-04 | AFG311 | - | Jul 4, 11:55 UTC | Jul 4, 12:35 UTC | 40m |
| 2026-07-02 | AFG415 | - | Jul 2, 16:50 UTC | Jul 3, 00:40 UTC | 7h 50m |
| 2026-07-02 | AFG415 | - | Jul 2, 01:50 UTC | Jul 3, 00:40 UTC | 22h 50m |
| 2026-07-02 | AFG714 | ESB → KBL | Jul 2, 01:20 UTC | Jul 2, 23:45 UTC | 22h 25m |
| 2026-07-01 | AFG714 | ESB → KBL | Jul 1, 21:50 UTC | Jul 2, 17:50 UTC | 20h 0m |
| 2026-07-01 | AFG713 | ESB → KBL | Jul 1, 20:50 UTC | Jul 2, 17:50 UTC | 21h 0m |
| 2026-07-01 | AFG720 | - | Jul 1, 01:50 UTC | Jul 2, 01:40 UTC | 23h 50m |
| 2026-06-30 | AFG719 | - | Jun 30, 23:10 UTC | Jun 30, 23:25 UTC | 15m |
| 2026-06-30 | AFG719 | - | Jun 30, 21:00 UTC | Jun 30, 22:30 UTC | 1h 30m |
| 2026-06-29 | AFG2454 | - | Jun 29, 22:44 UTC | Jun 30, 21:45 UTC | 23h 1m |
| 2026-06-29 | AFG2454 | - | Jun 29, 16:19 UTC | Jun 29, 23:39 UTC | 7h 20m |
| 2026-06-29 | AFG2452 | - | Jun 29, 00:20 UTC | Jun 29, 23:39 UTC | 23h 20m |
| 2026-06-28 | AFG2452 | - | Jun 28, 17:50 UTC | Jun 29, 17:19 UTC | 23h 30m |
| 2026-06-28 | AFG2452 | - | Jun 28, 17:34 UTC | Jun 29, 01:29 UTC | 7h 55m |
| 2026-06-28 | AFG2450 | - | Jun 28, 00:30 UTC | Jun 28, 18:29 UTC | 18h 0m |
| 2026-06-27 | AFG2450 | - | Jun 27, 17:49 UTC | Jun 28, 17:44 UTC | 23h 55m |
| 2026-06-27 | AFG2450 | - | Jun 27, 01:49 UTC | Jun 28, 01:29 UTC | 23h 40m |
| 2026-06-27 | AFG2448 | - | Jun 27, 00:55 UTC | Jun 27, 18:45 UTC | 17h 50m |
| 2026-06-26 | AFG2448 | - | Jun 26, 17:40 UTC | Jun 27, 01:49 UTC | 8h 10m |
| 2026-06-25 | AFG2445 | - | Jun 25, 16:24 UTC | Jun 25, 23:49 UTC | 7h 25m |
| 2026-06-24 | AFG2445 | - | Jun 24, 23:50 UTC | Jun 25, 23:44 UTC | 23h 55m |
| 2026-06-24 | AFG2445 | - | Jun 24, 23:04 UTC | Jun 25, 17:25 UTC | 18h 20m |
| 2026-06-24 | AFG2443 | - | Jun 24, 16:14 UTC | Jun 24, 23:59 UTC | 7h 45m |
| 2026-06-23 | AFG2442 | - | Jun 23, 18:39 UTC | Jun 24, 17:10 UTC | 22h 30m |
| 2026-06-22 | AFG2441 | - | Jun 22, 23:50 UTC | Jun 23, 19:44 UTC | 19h 55m |
| 2026-06-22 | AFG2441 | - | Jun 22, 22:44 UTC | Jun 23, 19:44 UTC | 21h 0m |
| 2026-06-22 | AFG2441 | - | Jun 22, 16:20 UTC | Jun 23, 13:45 UTC | 21h 25m |
| 2026-06-22 | AFG2438 | - | Jun 22, 00:29 UTC | Jun 22, 23:45 UTC | 23h 15m |
| 2026-06-21 | AFG2438 | - | Jun 21, 18:04 UTC | Jun 22, 17:20 UTC | 23h 15m |
| 2026-06-21 | AFG2438 | - | Jun 21, 17:29 UTC | Jun 22, 01:29 UTC | 8h 0m |
| 2026-06-20 | AFG2437 | - | Jun 20, 21:49 UTC | Jun 21, 18:25 UTC | 20h 35m |
| 2026-06-20 | AFG2436 | - | Jun 20, 20:55 UTC | Jun 21, 18:25 UTC | 21h 30m |
| 2026-06-20 | FG2035 | - | Jun 20, 14:05 UTC | Jun 20, 21:49 UTC | 7h 45m |
| 2026-06-19 | FG2035 | - | Jun 19, 23:49 UTC | Jun 20, 21:49 UTC | 22h 0m |
| 2026-06-19 | FG2035 | - | Jun 19, 23:14 UTC | Jun 20, 21:44 UTC | 22h 30m |
| 2026-06-19 | AFG2433 | - | Jun 19, 17:34 UTC | Jun 20, 00:19 UTC | 6h 45m |
| 2026-06-18 | AFG2433 | - | Jun 18, 21:50 UTC | Jun 19, 18:30 UTC | 20h 39m |
| 2026-06-18 | AFG2432 | - | Jun 18, 21:10 UTC | Jun 19, 18:30 UTC | 21h 19m |
| 2026-06-18 | AFG2432 | - | Jun 18, 15:05 UTC | Jun 18, 22:15 UTC | 7h 10m |
| 2026-06-17 | AFG2431 | - | Jun 17, 15:50 UTC | Jun 18, 15:45 UTC | 23h 55m |
| 2026-06-17 | AFG2429 | - | Jun 17, 08:35 UTC | Jun 17, 16:20 UTC | 7h 45m |
| 2026-06-14 | AFG2427 | - | Jun 14, 16:30 UTC | Jun 15, 01:15 UTC | 8h 45m |
| 2026-06-14 | AFG2427 | - | Jun 14, 00:50 UTC | Jun 14, 17:35 UTC | 16h 45m |
| 2026-06-13 | AFG2425 | - | Jun 13, 15:55 UTC | Jun 14, 01:45 UTC | 9h 50m |
| 2026-06-13 | AFG2425 | - | Jun 13, 02:00 UTC | Jun 14, 01:45 UTC | 23h 44m |
| 2026-06-13 | AFG2424 | - | Jun 13, 01:05 UTC | Jun 13, 16:50 UTC | 15h 44m |
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-CAV page for operator, model, and routing details .