{
    "@context": {
        "schema": "https://schema.org/",
        "dct": "http://purl.org/dc/terms/",
        "hg": "https://hormuz.group/data/ns#"
    },
    "id": "hg:infrastructure:fereydunkenar-port",
    "identifier": "hg:infrastructure:fereydunkenar-port",
    "dataset_type": "entity_dataset",
    "entity_type": "infrastructure",
    "data_version": "2.0",
    "generated_by": "Hormuz Data Layer 0.2.1",
    "generated_at": "2026-07-04T02:51:18+00:00",
    "name": "Fereydunkenar Port",
    "slug": "fereydunkenar-port",
    "status": "publish",
    "url": "https://hormuz.group/infrastructure/fereydunkenar-port/",
    "json_url": "https://hormuz.group/wp-content/uploads/hormuz-data/cpt/infrastructure/fereydunkenar-port.json",
    "rest_url": "https://hormuz.group/wp-json/hormuz-data/v1/cpt/infrastructure/fereydunkenar-port",
    "summary": "",
    "machine_summary": "Fereydunkenar Port Fereydunkenar Port matters in the Hormuz Graph as a smaller Caspian port on Mazandaran’s central coast, positioned between the province’s agricultural, food, and consumer markets and northern maritime routes. Its role is different from Amirabad’s larger corridor profile: Fereydunkenar is more relevant for localized port activity, coastal trade, warehousing, and short-sea logistics serving nearby districts. It connects provincial goods movement, Caspian shipping options, and regional distribution needs without carrying the same national-gateway weight as Iran’s larger northern ports. Fereydunkenar Port Fereydunkenar, Mazandaran Province, Iran province: Mazandaran industry: Logistics &amp; Transport, Maritime Logistics, Ports &amp; Shipping market: Exports, Imports, Ports, Trade &amp; Transit challenges: Compliance, Data Gaps, Logistics Gap infrastructure_type: Port",
    "published_at": "2026-06-24T12:44:46+00:00",
    "modified_at": "2026-06-24T12:44:46+00:00",
    "taxonomies": {
        "province": [
            {
                "id": 193,
                "name": "Mazandaran",
                "slug": "mazandaran",
                "url": "https://hormuz.group/provinces/mazandaran/"
            }
        ],
        "industry": [
            {
                "id": 19,
                "name": "Logistics &amp; Transport",
                "slug": "logistics-transport",
                "url": "https://hormuz.group/industry/logistics-transport/"
            },
            {
                "id": 319,
                "name": "Maritime Logistics",
                "slug": "maritime-logistics",
                "url": "https://hormuz.group/industry/logistics-transport/maritime-logistics/"
            },
            {
                "id": 117,
                "name": "Ports &amp; Shipping",
                "slug": "ports-shipping",
                "url": "https://hormuz.group/industry/logistics-transport/ports-shipping/"
            }
        ],
        "market": [
            {
                "id": 56,
                "name": "Exports",
                "slug": "exports",
                "url": "https://hormuz.group/market/trade-transit/exports/"
            },
            {
                "id": 57,
                "name": "Imports",
                "slug": "imports",
                "url": "https://hormuz.group/market/trade-transit/imports/"
            },
            {
                "id": 61,
                "name": "Ports",
                "slug": "ports",
                "url": "https://hormuz.group/market/trade-transit/ports/"
            },
            {
                "id": 39,
                "name": "Trade &amp; Transit",
                "slug": "trade-transit",
                "url": "https://hormuz.group/market/trade-transit/"
            }
        ],
        "challenges": [
            {
                "id": 164,
                "name": "Compliance",
                "slug": "compliance",
                "url": "https://hormuz.group/challenges/regulatory-barriers/compliance/"
            },
            {
                "id": 187,
                "name": "Data Gaps",
                "slug": "data-gaps",
                "url": "https://hormuz.group/challenges/operational-risks/data-gaps/"
            },
            {
                "id": 170,
                "name": "Logistics Gap",
                "slug": "logistics-gap",
                "url": "https://hormuz.group/challenges/infrastructure-gaps/logistics-gap/"
            }
        ],
        "infrastructure_type": [
            {
                "id": 309,
                "name": "Port",
                "slug": "port",
                "url": "https://hormuz.group/infrastructure-type/port/"
            }
        ]
    },
    "taxonomy_labels": {
        "province": "Mazandaran",
        "industry": "Logistics &amp; Transport, Maritime Logistics, Ports &amp; Shipping",
        "market": "Exports, Imports, Ports, Trade &amp; Transit",
        "challenges": "Compliance, Data Gaps, Logistics Gap",
        "infrastructure_type": "Port"
    },
    "fields_summary": {
        "official_name": "Fereydunkenar Port",
        "city_location": "Fereydunkenar, Mazandaran Province, Iran",
        "strategic_role": "Fereydunkenar Port matters in the Hormuz Graph as a smaller Caspian port on Mazandaran’s central coast, positioned between the province’s agricultural, food, and consumer markets and northern maritime routes. Its role is different from Amirabad’s larger corridor profile: Fereydunkenar is more relevant for localized port activity, coastal trade, warehousing, and short-sea logistics serving nearby districts. It connects provincial goods movement, Caspian shipping options, and regional distribution needs without carrying the same national-gateway weight as Iran’s larger northern ports.",
        "operational_status": "active",
        "related_use_cases": "Useful for regional port comparison, Caspian cargo routing, local warehouse planning, import-export feasibility screening, and partner search in central Mazandaran. Analysts can use it to assess whether smaller cargo flows should use Fereydunkenar, Amirabad, or Anzali depending on destination, cargo type, inland access, and service availability. Practical decisions should verify active routes, storage capacity, customs processes, and port service reliability."
    },
    "fields": {
        "rank_math_internal_links_processed": "1",
        "wp_statistics_words_count": "0",
        "official_name": "Fereydunkenar Port",
        "city_location": "Fereydunkenar, Mazandaran Province, Iran",
        "operational_status": "active",
        "verification_status": "basic",
        "data_confidence": "medium",
        "last_updated": "24/06/2026",
        "strategic_role": "Fereydunkenar Port matters in the Hormuz Graph as a smaller Caspian port on Mazandaran’s central coast, positioned between the province’s agricultural, food, and consumer markets and northern maritime routes. Its role is different from Amirabad’s larger corridor profile: Fereydunkenar is more relevant for localized port activity, coastal trade, warehousing, and short-sea logistics serving nearby districts. It connects provincial goods movement, Caspian shipping options, and regional distribution needs without carrying the same national-gateway weight as Iran’s larger northern ports.",
        "related_use_cases": "Useful for regional port comparison, Caspian cargo routing, local warehouse planning, import-export feasibility screening, and partner search in central Mazandaran. Analysts can use it to assess whether smaller cargo flows should use Fereydunkenar, Amirabad, or Anzali depending on destination, cargo type, inland access, and service availability. Practical decisions should verify active routes, storage capacity, customs processes, and port service reliability.",
        "source_note": "Based on public infrastructure, provincial, industrial, and market-context information. Further verification is required before treating this profile as verified investment intelligence.",
        "rank_math_analytic_object_id": "118"
    },
    "field_profile": {
        "rank_math_internal_links_processed": {
            "type": "string",
            "present": true,
            "length": 1
        },
        "wp_statistics_words_count": {
            "type": "string",
            "present": true,
            "length": 1
        },
        "official_name": {
            "type": "string",
            "present": true,
            "length": 18
        },
        "city_location": {
            "type": "string",
            "present": true,
            "length": 40
        },
        "operational_status": {
            "type": "string",
            "present": true,
            "length": 6
        },
        "verification_status": {
            "type": "string",
            "present": true,
            "length": 5
        },
        "data_confidence": {
            "type": "string",
            "present": true,
            "length": 6
        },
        "last_updated": {
            "type": "string",
            "present": true,
            "length": 10
        },
        "strategic_role": {
            "type": "string",
            "present": true,
            "length": 597
        },
        "related_use_cases": {
            "type": "string",
            "present": true,
            "length": 463
        },
        "source_note": {
            "type": "string",
            "present": true,
            "length": 186
        },
        "rank_math_analytic_object_id": {
            "type": "string",
            "present": true,
            "length": 3
        }
    },
    "sources": [
        {
            "type": "note",
            "value": "Based on public infrastructure, provincial, industrial, and market-context information. Further verification is required before treating this profile as verified investment intelligence."
        }
    ],
    "quality": {
        "required_fields": [
            "official_name",
            "city_location",
            "strategic_role",
            "operational_status",
            "related_use_cases",
            "verification_status",
            "data_confidence",
            "source_note",
            "last_updated"
        ],
        "missing_required_fields": [],
        "missing_required_count": 0,
        "verification_status": "basic",
        "data_confidence": "medium",
        "last_updated": "24/06/2026",
        "stale_over_180_days": false,
        "quality_score": 100
    },
    "verification": {
        "verification_status": "basic",
        "data_confidence": "medium",
        "last_updated": "24/06/2026"
    }
}