Open Company Data in Iceland: Official Sources, APIs and Reuse Rights
Iceland has a serious official company-data ecosystem, but it should not be reduced to a simple list of companies. The right way to evaluate Iceland is to start with the official register, then add open-data, statistics, procurement, intellectual-property and regulator layers.
The strongest route is Skatturinn's company-registration services and public API portal, supported by Icelandic statistics, procurement, IP and regulator sources. That makes Iceland a small market with a clear official API signal, but it does not remove the usual reuse checks: dataset terms, attribution, no-endorsement language, privacy, marketing-law boundaries and source freshness.
This guide maps the main official sources for company data in Iceland, explains what each source can and cannot do, and shows where a normalized CompaniesData-style dataset adds value.
The deeper question is not whether a source exists. The useful question is which source can be trusted for identity, which one proves events or filings, which one is usable at scale, which one is only a manual service, and which fields become legally sensitive once the data is reused commercially.
Quick Answer
Iceland becomes publishable in Burst A because the Skatturinn API portal provides a concrete official public company-registry API signal.
For practical work, the most useful source stack is: Skatturinn API portal, Company registration, Company registry data/certificates guidance, Register of beneficial owners forms, Iceland open-data portal, Statistics Iceland.
The safe editorial answer is this: Iceland has strong public and official business-data sources, but public data is not automatically bulk-downloadable, marketing-ready or free of personal-data constraints.
A serious Iceland dataset normally needs at least four layers: the legal register for entity identity, official publications or filings for change events, public procurement/regulator/IP/statistical sources for enrichment, and a separate compliance layer for privacy, contact-data use, suppression and lawful outreach.
Key Takeaways
- Best starting point: Skatturinn's company-registration services and public API portal, supported by Icelandic statistics, procurement, IP and regulator sources.
- Core source stack: Skatturinn API portal, Company registration, Company registry data/certificates guidance, Register of beneficial owners forms, Iceland open-data portal, Statistics Iceland.
- Reuse rule: public visibility is not the same as bulk reuse, resale permission or marketing-contact permission.
- Buyer value: the useful dataset is the normalized, deduplicated and source-auditable version, not a raw list of portal links.
- Commercial separation: official company records, enriched company profiles and business contact data should remain separate layers with separate compliance notes.
Editorial Methodology
This article uses an official-source-first method. Sources are included when they help verify legal existence, public filings, procurement activity, taxpayer or identifier context, IP ownership, regulated status, statistics or lawful compliance context. Commercial providers and contact-data products are not used as authority for official reuse rights.
- Prefer the national registry, company house, gazette or official business-registration authority before any secondary source.
- Classify access as search, API, bulk download, paid extract, subscription, document workflow, data catalogue or unclear/manual access.
- Separate legal-entity data from establishment statistics, procurement suppliers, listed-company disclosures, tax identifiers and private contact data.
- Treat beneficial owners, officers, addresses, signatures, insolvency notices and sole-trader records as privacy-sensitive unless the source and law clearly support reuse.
- Hold or omit unstable source links when live QA shows 403, 429, 5xx, DNS, TLS or timeout behaviour that would create broken-link noise.
What Counts as Company Data in Iceland?
| Layer | Examples | Typical business use |
|---|---|---|
| Registry identity | Legal name, registration number, status, legal form, registered office | Entity matching, deduplication and KYB |
| Register events | Incorporation, changes, filings, extracts, publications | Corporate timeline and legal traceability |
| Open-data/API layer | Official datasets, APIs, CSV/JSON/XML services where available | Automated ingestion and monitoring |
| Statistics | Business demography, enterprise counts, sector/geography totals | Market sizing and data-quality benchmarks |
| Procurement | Tenders, awards, suppliers and contracting authorities | Public-sector sales intelligence |
| IP and regulators | Trademarks, patents, supervised entities and decisions | Enrichment and compliance screening |
| Contact data | Email, phone, contact roles and segmentation | Marketing only with a separate lawful basis |
In Iceland, these layers should not be collapsed into one undifferentiated database. A registry result may prove legal existence, a procurement notice may prove public-sector activity, an IP record may prove brand or invention ownership, and a regulator list may prove supervision. Those are different facts with different update cycles, identifiers and reuse boundaries.
Reuse Rights and Compliance
Across jurisdictions, public-sector-information and open-data policies can support reuse of public-sector data, and high-value dataset rules increasingly treat company and company-ownership data as important public information. In practice, Iceland's actual reuse position still depends on each source, endpoint, licence and access method.
- Cite official sources and preserve update dates where the source provides them.
- Do not imply that a derived dataset is endorsed by the registry or public authority.
- Do not mix public register data with marketing-contact permission.
- Check whether API, bulk download, paid extract and web-search access have different terms.
- Treat officers, beneficial owners and natural-person data as GDPR-sensitive where applicable.
Iceland has an official company registration layer through Skatturinn and a useful statistical/open-data environment, but official company-data API/bulk access is not yet verified. The article should be cautious and explain the difference between company registration, statistical business data and paid certificates/data requests.
Coverage, Access and Update Risk
The most common mistake in Iceland company-data work is to confuse visibility with completeness. A public search screen can be authoritative for one entity lookup without being suitable for bulk ingestion. A downloadable dataset can be reusable for a defined snapshot while still excluding filings, documents, directors, inactive entities or historical changes.
- Coverage: identify whether the source covers companies, business names, branches, non-profits, sole traders, listed issuers, regulated entities or only a sector subset.
- Freshness: preserve the source update date and avoid mixing live portal results with old downloaded files without version labels.
- Identifiers: map registration numbers, tax identifiers, procurement supplier IDs, LEI records and exchange tickers as separate keys until verified.
- Language and formats: normalize local-language names, legal forms, transliteration, accents, abbreviations and address formats carefully.
- Operational access: document whether the workflow is public search, API, bulk file, paid extract, login-only service, PDF, CKAN/OData/SPARQL or manual request.
Reuse Checklist for Iceland
| Layer | Useful for | Reuse caution in Iceland |
|---|---|---|
| Public search | Good for verification and manual QA | May prohibit scraping, bulk extraction or automated reuse |
| API or dataset | Best route for repeatable ingestion | Endpoint terms, attribution and rate limits still apply |
| Paid extract or certificate | Useful for legal certainty | Usually contractual, document-level and not an open dataset |
| Procurement and regulator data | Strong enrichment and monitoring layer | Subset coverage; not a universal company register |
| Officer, owner or address fields | Useful for KYB and compliance where lawful | Privacy-sensitive and never automatic marketing consent |
| Business emails and phones | Commercial outreach layer | Requires separate lawful basis, suppression logic and contact-data governance |
Resource Pack
Use this resource pack as a working map for verification, ingestion planning and source-risk review. The small source logos are decorative credibility cues only; the authority still comes from the official URL, owner, access model and reuse note.
Registry and legal identity
Company registry data/certificates guidance
Use: Requests for data/certificates and fees
Watch: PDF/service model
API, bulk and open-data access
Skatturinn API portal
Use: Official API catalogue including company-register public API access
Watch: Authentication, fields and terms must be checked endpoint by endpointCompany registration
Use: Official registration context
Watch: Not a data APIIceland open-data portal
Use: National open datasets
Watch: Company-register coverage needs checkSkatturinn API home
Use: Official API portal context for public access to Skatturinn data services
Watch: Use as API evidence and navigation context, not as proof of unrestricted bulk reusePrivate Limited Companies
Use: Official registration requirements for Icelandic private limited companies
Watch: Registration guidance, not a machine-readable company datasetPublic Limited Companies
Use: Official registration requirements for Icelandic public limited companies
Watch: Registration guidance, not a complete data API or filings archive
Procurement and public spending
Public procurement
Use: Central public procurement
Watch: Supplier-only coverageEU/TED procurement
Use: EEA procurement notices
Watch: Threshold/public-contract coverage onlyIceland procurement portal
Use: Public procurement notices and supplier-market context
Watch: Procurement is a subset of entities with public-contract activity
Statistics and market context
Statistics Iceland
Use: Business demography/statistics
Watch: Not legal company profilesStatistics Iceland PX API
Use: Machine-readable Statistics Iceland API catalogue for official aggregate statistics
Watch: Aggregate/statistical layer only; it does not provide legal company profiles
IP, brands and intangible assets
Icelandic Intellectual Property Office
Use: Trademarks, patents and designs
Watch: Rights separate
Regulators and compliance
Register of beneficial owners forms
Use: Beneficial owner registration context
Watch: Not open company datasetCentral Bank / Financial Supervisory Authority
Use: Regulated financial entities
Watch: Sector-specific
Additional verification sources
Icelandic Competition Authority
Use: Competition decisions
Watch: Decision-based
Main Official Sources: Deep Dive
1.
Skatturinn API portal
Owner: Iceland Revenue and Customs. Access: https://api.skatturinn.is/apis.
- What it gives: Official API catalogue including company-register public API access
- Reuse value: Strong official technical source
- Main limitation: Authentication, fields and terms must be checked endpoint by endpoint
Skatturinn API portal is a Iceland Revenue and Customs source for Iceland. Its main practical value is Official API catalogue including company-register public API access Access is through https://api.skatturinn.is/apis, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.
For reuse, the working rule is: Strong official technical source. The main limitation is Authentication, fields and terms must be checked endpoint by endpoint In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.
2.
Company registration
Owner: Skatturinn / RSK. Access: https://www.skatturinn.is/english/company-registration/.
- What it gives: Official registration context
- Reuse value: Official source
- Main limitation: Not a data API
Company registration is a Skatturinn / RSK source for Iceland. Its main practical value is Official registration context Access is through https://www.skatturinn.is/english/company-registration/, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.
For reuse, the working rule is: Official source. The main limitation is Not a data API In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.
3.
Company registry data/certificates guidance
Owner: Skatturinn. Access: https://www.skatturinn.is/media/efni-med-greinum/afgreiddu-thig_EN_vef.pdf.
- What it gives: Requests for data/certificates and fees
- Reuse value: Official access context
- Main limitation: PDF/service model
Company registry data/certificates guidance is a Skatturinn source for Iceland. Its main practical value is Requests for data/certificates and fees Access is through https://www.skatturinn.is/media/efni-med-greinum/afgreiddu-thig_EN_vef.pdf, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.
For reuse, the working rule is: Official access context. The main limitation is PDF/service model In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.
4.
Register of beneficial owners forms
Owner: Skatturinn. Access: https://www.skatturinn.is/media/rsk17/rsk_1727.en.pdf.
- What it gives: Beneficial owner registration context
- Reuse value: Official compliance source
- Main limitation: Not open company dataset
Register of beneficial owners forms is a Skatturinn source for Iceland. Its main practical value is Beneficial owner registration context Access is through https://www.skatturinn.is/media/rsk17/rsk_1727.en.pdf, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.
For reuse, the working rule is: Official compliance source. The main limitation is Not open company dataset In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.
5.
Iceland open-data portal
Owner: Government of Iceland. Access: https://opingogn.is/.
- What it gives: National open datasets
- Reuse value: Dataset-specific reuse
- Main limitation: Company-register coverage needs check
Iceland open-data portal is a Government of Iceland source for Iceland. Its main practical value is National open datasets Access is through https://opingogn.is/, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.
For reuse, the working rule is: Dataset-specific reuse. The main limitation is Company-register coverage needs check In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.
6.
Statistics Iceland
Owner: Statistics Iceland. Access: https://www.statice.is/.
- What it gives: Business demography/statistics
- Reuse value: Official aggregate data
- Main limitation: Not legal company profiles
Statistics Iceland is a Statistics Iceland source for Iceland. Its main practical value is Business demography/statistics Access is through https://www.statice.is/, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.
For reuse, the working rule is: Official aggregate data. The main limitation is Not legal company profiles In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.
7.
Public procurement
Owner: Rikiskaup. Access: https://www.rikiskaup.is/.
- What it gives: Central public procurement
- Reuse value: Procurement signal
- Main limitation: Supplier-only coverage
Public procurement is a Rikiskaup source for Iceland. Its main practical value is Central public procurement Access is through https://www.rikiskaup.is/, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.
For reuse, the working rule is: Procurement signal. The main limitation is Supplier-only coverage In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.
8.
EU/TED procurement
Owner: EU Publications Office. Access: https://data.ted.europa.eu/.
- What it gives: EEA procurement notices
- Reuse value: Procurement signal
- Main limitation: Threshold/public-contract coverage only
EU/TED procurement is a EU Publications Office source for Iceland. Its main practical value is EEA procurement notices Access is through https://data.ted.europa.eu/, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.
For reuse, the working rule is: Procurement signal. The main limitation is Threshold/public-contract coverage only In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.
9.
Icelandic Intellectual Property Office
Owner: Hugverkastofan. Access: https://www.hugverk.is/en.
- What it gives: Trademarks, patents and designs
- Reuse value: IP signal
- Main limitation: Rights separate
Icelandic Intellectual Property Office is a Hugverkastofan source for Iceland. Its main practical value is Trademarks, patents and designs Access is through https://www.hugverk.is/en, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.
For reuse, the working rule is: IP signal. The main limitation is Rights separate In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.
10.
Central Bank / Financial Supervisory Authority
Owner: Central Bank of Iceland. Access: https://www.cb.is/financial-supervision/.
- What it gives: Regulated financial entities
- Reuse value: Compliance source
- Main limitation: Sector-specific
Central Bank / Financial Supervisory Authority is a Central Bank of Iceland source for Iceland. Its main practical value is Regulated financial entities Access is through https://www.cb.is/financial-supervision/, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.
For reuse, the working rule is: Compliance source. The main limitation is Sector-specific In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.
Practical Options
Official open-data or API route
Start with Skatturinn's company registration and API portal, then add opingogn.is, Statistics Iceland, procurement, Hugverkastofan and Central Bank sources.
For production use, treat this route as an ingestion plan rather than a single download. Start with the official registry or data catalogue, keep raw source snapshots, record access terms, then add enrichment sources one by one with field-level provenance.
Manual verification and document route
Some countries expose important company facts through certificates, PDF filings, gazette notices, paid extracts or login-based services. Those sources can be valuable, but they should be documented as controlled workflows. Do not describe them as open APIs or bulk datasets unless the authority clearly publishes that access model.
Contact-data and marketing-list route
For sales outreach, company identity data is only the first layer. Business emails, phone numbers, contact roles, suppression logic and segmentation require a separate compliant contact-data process. That layer should be documented separately from official registry reuse.
Private reports and risk products
Private company-report providers can be useful for manual due diligence in Iceland, but the editorial focus here is not a directory of competitors. The strategic value is understanding which official sources exist and where normalization is required.
If a user needs CRM-ready company records, the practical path is to combine official-source provenance with enrichment, deduplication, quality checks and lawful delivery controls. That is different from buying a generic lead list: the official-source layer explains what can be verified, while the commercial dataset layer explains how the records can be used operationally.
API, Beneficial-Ownership and Person-Data Boundaries
Iceland has a real official API signal, but that does not make every registry-adjacent field open for every use. Skatturinn’s API portal confirms a public-facing company-registry API route, while certificates, filings, annual-account materials, beneficial-owner forms, addresses and role/person fields can follow different legal and operational rules. Treat the API as a company-identity and verification layer first, then review each endpoint, field and document class before building redistribution, monitoring or enrichment workflows.
- Allowed claim: Iceland has official company-registration sources and an official Skatturinn API portal with a public company-registry API signal.
- Blocked claim: every filing, financial statement, beneficial-owner document or natural-person field is freely reusable in bulk.
- Operational rule: separate company identity, statistical context, procurement/IP/regulator enrichment, documents and contact data into different data-model layers.
Contact-Data Boundary
Public company records are not a cold-email licence. If the business need is enriched company records, segmentation, email or phone workflows for an English or international audience, route the workflow through CompaniesData.cloud. For Spanish-speaking or Hispanic outreach workflows, CentraldeComunicacion.es is the preferred property. This article does not recommend third-party contact-data sellers as evidence for official Icelandic reuse rights.
What Is Missing from Official Open Data?
- Certificates, filings, financial data and beneficial-owner details can have separate access routes.
- The public API needs endpoint and terms checks before operational reuse.
- Official registry access does not include business emails or phones.
This is why company-data products often add value even when the underlying public sources are strong: official data is frequently split across authorities, formats, languages, identifiers and access models.
Missing data should be treated explicitly in the dataset design. If an official source lacks bulk downloads, CompaniesData should not pretend that the bulk file exists; it should record the source limitation, add alternate official enrichment where lawful, and expose confidence fields so users know which attributes came from which layer.
Recommended Data Model
A practical CompaniesData-style model for Iceland should keep source evidence and commercial-use fields separate. The core table should hold legal entity identity, status, registration identifiers, legal form, jurisdiction, registered address and source dates. Separate enrichment tables can then store procurement awards, IP assets, regulator status, listed-company signals, LEI matches, sanctions/compliance hits and statistics-sector context.
- Entity identity: legal name, normalized name, registration number, jurisdiction, legal form and lifecycle status.
- Source provenance: source URL, authority, retrieval date, access method, licence/reuse note and confidence flag.
- Event history: incorporation, amendments, filings, gazette notices, insolvency or dissolution where legally public.
- Enrichment: procurement, IP, regulator, exchange, LEI and official statistics layers with their own source dates.
- Commercial delivery: CRM-ready exports, segmentation and contact-data fields only when a separate lawful basis and suppression workflow exist.
How CompaniesData Adds Value
For Iceland, CompaniesData's role is to turn fragmented source material into a usable business dataset: normalized company names, deduplicated entities, consistent country and activity fields, source provenance, update tracking and enrichment hooks.
- Normalize register identifiers and legal names.
- Match official company records with procurement, IP, LEI and regulator signals.
- Flag source provenance so every derived profile can be audited.
- Separate company identity from contact-data and marketing-permission layers.
- Package data for analysis, CRM enrichment and market research instead of forcing users to parse portals manually.
For Iceland, the editorial value of CompaniesData is not claiming that every record is open or that every field can be reused without conditions. The value is the opposite: making source boundaries visible, normalizing messy records, adding explainable enrichment and delivering a dataset that users can audit instead of a black-box scrape.
Request a CompaniesData sample for Iceland if you need a practical dataset rather than a list of source portals.
Source Matrix
| Source | Owner | What it gives | Reuse value | Limitations |
|---|---|---|---|---|
| Iceland Revenue and Customs | Official API catalogue including company-register public API access | Strong official technical source | Authentication, fields and terms must be checked endpoint by endpoint | |
| Skatturinn / RSK | Official registration context | Official source | Not a data API | |
| Skatturinn | Requests for data/certificates and fees | Official access context | PDF/service model | |
| Skatturinn | Beneficial owner registration context | Official compliance source | Not open company dataset | |
| Government of Iceland | National open datasets | Dataset-specific reuse | Company-register coverage needs check | |
| Statistics Iceland | Business demography/statistics | Official aggregate data | Not legal company profiles | |
| Rikiskaup | Central public procurement | Procurement signal | Supplier-only coverage | |
| EU Publications Office | EEA procurement notices | Procurement signal | Threshold/public-contract coverage only | |
| Hugverkastofan | Trademarks, patents and designs | IP signal | Rights separate | |
| Central Bank of Iceland | Regulated financial entities | Compliance source | Sector-specific | |
| Samkeppniseftirlitid | Competition decisions | Risk signal | Decision-based | |
| Iceland Revenue and Customs | Official API portal context for public access to Skatturinn data services | Official technical access context; endpoint terms and subscriptions remain source-specific | Use as API evidence and navigation context, not as proof of unrestricted bulk reuse | |
| Iceland Revenue and Customs / Skatturinn | Official registration requirements for Icelandic private limited companies | Official registry guidance; cite source and separate registration evidence from data reuse rights | Registration guidance, not a machine-readable company dataset | |
| Iceland Revenue and Customs / Skatturinn | Official registration requirements for Icelandic public limited companies | Official registry guidance; cite source and separate registration evidence from data reuse rights | Registration guidance, not a complete data API or filings archive | |
| Statistics Iceland | Machine-readable Statistics Iceland API catalogue for official aggregate statistics | Official statistics API terms and source-reference requirements | Aggregate/statistical layer only; it does not provide legal company profiles | |
| Iceland public procurement ecosystem | Public procurement notices and supplier-market context | Procurement-specific publication terms and notice-level constraints | Procurement is a subset of entities with public-contract activity | |
| Global Legal Entity Identifier Foundation | Open LEI cross-checks for Icelandic legal entities with LEIs | GLEIF API/open-data terms; attribution and API conditions apply | LEI coverage is a regulated-market/KYB subset, not a national company register |
Iceland is an "official but not open-bulk verified" article. Use it later than Estonia/Finland/Ireland.
FAQ
Is there a single free official bulk company database for Iceland?
Not always. Iceland has official company-data sources, but bulk access, API access, paid extracts and web search can be separate products. Do not assume a complete free bulk file unless the specific source proves it.
What is the best first source for Iceland company data?
The best first source is Skatturinn's company-registration services and public API portal, supported by Icelandic statistics, procurement, IP and regulator sources. It should then be combined with statistics, procurement, IP and regulator sources.
Can public company data be reused commercially?
Often yes, but only under the conditions of the specific source. Attribution, update-date preservation, no-endorsement wording and GDPR controls may apply.
Can I use registry data for cold email marketing?
No automatic conclusion follows from public registry access. Marketing requires a separate lawful basis, suppression handling and contact-data compliance review.
Why use CompaniesData instead of manually collecting Iceland sources?
Manual collection is slow because identifiers, formats, languages and coverage differ by source. CompaniesData adds normalization, matching, deduplication, provenance and practical delivery formats.
How often should Iceland company data be refreshed?
Refresh cadence depends on the source. Registry searches and APIs can support frequent checks, while gazettes, procurement portals, statistical releases and paid extracts may update on different schedules. A reliable dataset should store retrieval dates and source-specific update notes.
What should be audited before publishing or selling an enriched dataset?
Audit source authority, licence terms, personal-data exposure, contact-data lawful basis, field provenance, suppression rules, update dates and whether any official source prohibits automated reuse or resale.
Sources
Skatturinn API portal – Iceland Revenue and Customs
Company registration – Skatturinn / RSK
Company registry data/certificates guidance – Skatturinn
Register of beneficial owners forms – Skatturinn
Iceland open-data portal – Government of Iceland
Statistics Iceland – Statistics Iceland
Public procurement – Rikiskaup
EU/TED procurement – EU Publications Office
Icelandic Intellectual Property Office – Hugverkastofan
Central Bank / Financial Supervisory Authority – Central Bank of Iceland
Icelandic Competition Authority – Samkeppniseftirlitid
Skatturinn API home – Iceland Revenue and Customs
Private Limited Companies – Iceland Revenue and Customs / Skatturinn
Public Limited Companies – Iceland Revenue and Customs / Skatturinn
Statistics Iceland PX API – Statistics Iceland
Iceland procurement portal – Iceland public procurement ecosystem
GLEIF LEI records for Iceland – Global Legal Entity Identifier Foundation
Leave a Reply
Want to join the discussion?Feel free to contribute!