Denmark–Iran relations
diplomatic relations between the Kingdom of Denmark and the Islamic Republic of Iran
The first Persian envoy to Denmark arrived in 1691 in order to negotiate the release of the Iranian-owned cargo of a Bengali ship seized by the Danish fleet. The Iranian diplomat had been issued with diplomatic credentials by Suleiman I of Persia (Shah 1666–1694) and opened negotiations with King Christian V of Denmark. He was unable to secure the release of the cargo.
History
In 1933, a Danish consulate was established in Tehran which was later upgraded to an embassy. Also in 1933, with the arrival of Danish engineers in Iran, technical cooperation commenced. In the same year a contract was signed with the Danish engineering firm of Kampsax A/S to construct the Trans-Iranian Railway line. Five years later, on 25 August 1938, with the opening of the North- South railway line the Iranian desire of connecting the North to the South by rail came true. Following a state visit in 1958, Iran established an embassy in Copenhagen. More specifically, the mission in Copenhagen was launched on 19 February 1959 and Ali Asghar Nase was appointed Iranian ambassador. The 2006 Muhammad cartoons controversy saw the Danish embassy to Iran attacked by protesters and the Iranian Ambassador to Denmark called to Tehran; thus straining political and economic interaction between the two countries.
Begin with the source’s own compact description: “Denmark–Iran relations” is diplomatic relations between the Kingdom of Denmark and the Islamic Republic of Iran. The dossier treats that line as a proposition to test through Denmark, Iran and relations, not as a finished interpretation.
Why this record matters
The phrase “diplomatic relations between the Kingdom of Denmark and the Islamic Republic of Iran” 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.
Vocabulary and entity names are the principal evidence signals here, because they determine the precision of every later search. The source revision retrieved here is dated Sep 17, 2026. The linked authority identifier is Q5258018. None of the 0 selected statements returned an explicit reference. The first chronological checks are 1691, 1666, 1694 and 1933.
A concise general-reference account can conceal disagreements about scope, terminology or the weight assigned to individual sources. 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 “Denmark–Iran relations”, its source revision and the description used here.
- Expand the search: follow Denmark–Iran relations primary sources, Denmark–Iran relations archive and Denmark 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 “Denmark–Iran relations”?
- Which institution is responsible for the underlying evidence?
- Which cited source is closest to the event, object or claim?
Search terms from this dossier
This entry incorporates text from “Denmark–Iran relations” 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.