Paropamisadae
alexandrian satrapy in Afghanistan and Pakistan

Paropamisadae or Parapamisadae (Ancient Greek: Παροπαμισάδαι or Παροπανισάδαι) was a satrapy of the Alexandrian Empire in modern Afghanistan and Pakistan, which largely coincided with the Achaemenid province of Parupraesanna. It consisted of the districts of Sattagydia (Bannu basin), Gandhara (Kabul, Peshawar, and Taxila), and Oddiyana (Swat Valley). Paruparaesanna is mentioned in the Akkadian language and Elamite language versions of the Behistun Inscription of Darius the Great, whereas in the Old Persian version it is called Gandāra. The entire satrapy was subsequently ceded by Seleucus I Nicator to Chandragupta Maurya after Mauryan Victory in Selucid-Mauryan war following a treaty.
Name
Paropamisadae is the Latinized form of the Greek name Paropamisádai (Παροπαμισάδαι), which is in turn derived from Old Persian Para-uparisaina, meaning "Beyond the Hindu Kush", where the Hindu Kush is referred to as Uparisaina ("higher than the eagle").
In the Greek language and Latin, "Paropamisus" (Παροπαμισός, Paropamisós) came to mean the Hindu Kush. In many Greek and Latin sources, particularly editions of Ptolemy's Geography where their realm is included on the 9th Map of Asia, the names of the people and region are given as Paropanisadae and Paropanisus. They also appeared less frequently as Parapamisadae and Parapamīsus (Παραπάμισος, Parapámisos), Paropamīsii, etc.
The name was also applied to a nearby river, probably the Obi river. The mountain range Selseleh-ye Safīd Kūh is also called Paropamisus or Paropamisus Mountains.
Begin with the source’s own compact description: “Paropamisadae” is alexandrian satrapy in Afghanistan and Pakistan. The dossier treats that line as a proposition to test through Paropamisadae, alexandrian and satrapy, not as a finished interpretation.
Why this record matters
The phrase “alexandrian satrapy in Afghanistan and Pakistan” supplies a clear boundary for inquiry. It also exposes the unanswered questions: who defined that boundary, when it became stable and which sources sit outside it.
Named sources, stable identifiers and responsible institutions provide the strongest route from overview to verifiable evidence. The source revision retrieved here is dated Sep 12, 2026. The linked authority identifier is Q1327635. None of the 0 selected statements returned an explicit reference.
Overview language is designed for orientation and should not be treated as a substitute for the evidence cited beneath it. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “Paropamisadae”, its source revision and the description used here.
- Expand the search: follow Paropamisadae primary sources, Paropamisadae archive and Paropamisadae research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Paropamisadae”?
- Which cited source is closest to the event, object or claim?
- What terminology or title could unlock a more precise catalogue search?
Search terms from this dossier
This entry incorporates text from “Paropamisadae” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.