Cyprus business register

Select the Q3 2025 edition if you need 312,480 legal entities: 196,940 active and 115,540 dissolved, all with HE numbers (100%), VAT IDs (88.7%), NACE Rev.2 codes (83.2%), incorporation dates (97.6%), and registered addresses with district (91.4%); directors/officers coverage: 72.3%, phone: 58.9%, email: 64.1%, website: 41.8%.

Use this set to build targeted outreach lists (filter by NACE sections C, J, M), map markets by district (Nicosia, Limassol, Larnaca, Paphos, Famagusta), and screen entities by status, VAT activity, and age. For quick wins, prioritize firms with 5+ officers, active VAT, and recent filings in the last 12 months.

Included fields: legal name, trade name, HE number, VAT ID, status, incorporation date, dissolution date, NACE code + label, share capital (where public), registered address, district, postal code, directors/secretary, shareholder names (where public), UBO reference link, phone, email, website, source URL, last_seen_at, last_updated_at.

Quality metrics: 99.2% deduplication, ASCII/UTF‑8 normalization, phone line-type detection, email syntax + MX checks, address geocoding to district; change logs delivered as delta files with created/updated/removed flags.

Access options: secure download link within 10 minutes after order; formats: CSV, XLSX, JSON, Parquet; UTF‑8, semicolon or comma delimiter; compressed size ~180–220 MB; sample of 1,000 rows available on request with full schema.

Recommendations: verify VAT via VIES, enrich NACE groups for segmentation, set alerts on status_changed_at for risk monitoring, and use district filters to balance coverage vs. response rates (Limassol and Nicosia deliver the highest contact density).

Licensing tiers: Starter (50k entities), Growth (full active set), Pro (full set + monthly refresh), with team seats and API add-on for automated pulls.

Cyprus Companies Data You Receive: Legal name, HE number, address, directors/shareholders, contact fields, NACE codes, company status, update schedule, verification sources

Use the HE identifier as the single source of truth: store it in two fields (raw “HE 123456” and numeric 123456) and never match entities by name alone; map status to a strict enum; refresh status daily, officers weekly, and full profiles monthly; require two independent sources before accepting any change.

Field structure and formats

Legal name: capture the official name as filed and an ASCII-normalized variant for searching. Preserve diacritics in UTF‑8. Keep an alias list for historical names with start/end dates. Avoid trimming legal suffixes during matching; store suffix separately in a dedicated field.

HE number: expected pattern “HE 1–6 digits”; recommended regex ^HE\s?\d{1,6}$. Persist three fields: prefix (“HE”), numeric part (int), and display form (“HE 123456”). Enforce uniqueness on the numeric part. Record first-seen and last-verified timestamps.

Address: split into unit, building, street name, street number, locality, district, postal code, and ISO country code (“CY”). Keep a formatted line for mailing exactly as filed. Add geocoding fields (lat, lon, geocoder, precision) with precision tags such as rooftop, interpolated, or centroid.

Directors/shareholders: store natural-person or legal-entity flag, full name, role (director, secretary, shareholder, member), appointment date, cessation date, and ownership percentage where disclosed. Add UBO layer capturing persons with ≥25% ownership or control, including control-by-other-means notes. Maintain history, not just current state.

Contact fields: email (RFC 5322 validated), phone in E.164 (+357… with national significant number), website (normalized to https, stripped of tracking parameters), and public-facing social links. Tag each field with its discovery source (official filing, website, press release) and crawl date.

NACE codes: store primary and up to five secondary codes per entity using NACE Rev. 2. Persist both the 4‑digit code and the English description. Keep a confidence score when inferred from text and a boolean flag when sourced from filings.

Status: use a controlled list–active, pending strike-off, struck off, under liquidation (voluntary/compulsory), dissolved, under receivership/examiner, re-domiciled out. Include status effective date and legal basis (e.g., Gazette notice ID). Do not delete dissolved entries; mark with status and retention reason.

Refresh cadence and verification sources

Update schedule: daily crawl for status shifts and Gazette notices, weekly officer and address diffs, monthly full profile reconciliation, quarterly NACE re-evaluation. Emit change logs with old/new values, source URLs, and hashes of the source documents. Timestamp each field with last_verified_at rather than only record-level updated_at.

Verification sources: cross-check against the national registrar portal, Government Gazette notices, tax/VAT registries (including VIES for VAT IDs), official court/bankruptcy bulletins, and the entity’s own statutory filings. For each verification, store source type, URL, retrieval date, evidence hash (SHA‑256 of PDF/HTML), and, where applicable, a page reference. Reject changes that lack corroboration from at least two independent sources, or quarantine them pending manual review.

Quality controls: enforce phone format with E.164 validation, MX checks for emails (no test domains), and address normalization against a postal dataset. Flag risky patterns (PO boxes without physical address when a registered office is expected, officer roles with impossible dates, ownership sums exceeding 100%). Keep a suppression list for private emails discovered outside public filings and honor takedown requests with audit trails.

Recommended schema tips: index by numeric HE, secondary indexes on normalized name and postal code; store names in case-folded form for search plus a canonical display name; separate current snapshot and history tables to speed lookups; expose a “data_freshness_score” derived from field-level verification ages.

How to Buy and Access: Pricing tiers, payment methods, VAT invoice, license scope, instant download/API, CSV/XLSX formats, delivery time

Choose a tier by volume and access mode: Starter (≤10,000 rows, one-off download), Growth (≤100,000 rows), Full (complete set). Optional API add‑on enables real‑time lookups and updates.

Indicative pricing: Starter €149, Growth €590, Full €1,990; API add‑on €79/month or €790/year. Volume-based or multi‑seat discounts available on request. Taxes excluded.

Payment methods: Visa, Mastercard, American Express, PayPal, Apple Pay, Google Pay, SEPA/SWIFT wire. Pro‑forma can be issued before payment; PO-based checkout available for larger orders.

VAT invoice: generated automatically after checkout with legal entity name, address, tax ID, and line‑item details. EU rules: valid VAT number → reverse charge (0%); no VAT number → VAT added at the buyer’s rate; outside the EU → 0% VAT. VAT IDs are validated via VIES.

License scope: Standard (single user, internal use, no resale, no public redistribution), Team (up to 10 users within one legal entity), Extended (redistribution in derived products or SaaS, attribution required; rate limits apply for API caching). Data may be used for analytics, enrichment, and lead qualification; resale of raw files is prohibited.

Instant access: files are available immediately after successful payment via a secure link on the order page and in your account; a confirmation email with a time‑limited link is also sent. API keys are issued within 2–5 minutes; typical throttles per plan: 10 req/s (Starter), 50 req/s (Growth), 200 req/s (Full).

Formats: CSV (UTF‑8, RFC4180 quoting, comma or semicolon), XLSX (one sheet per table), JSON via API. Large files ship as .zip or .gz. A data dictionary and column schema are included. Line endings: LF. Nulls represented as empty fields.

Delivery time: card/PayPal/Apple/Google payments → access in seconds; SEPA wire → same day to next working day; SWIFT → 1–3 working days. Need it faster after a wire? Send remittance advice to trigger manual release.

Updates: snapshot downloads refreshed monthly; API reflects daily changes. Minor corrections may be pushed between cycles; re‑download at no extra cost within your update window.

Integrate and Use: Import to CRM (Salesforce, HubSpot), dedupe and normalize records, segment by NACE/location/status, GDPR-safe outreach steps, support channel

Import the CSV into Salesforce via Data Import Wizard (simple loads) or Data Loader (bulk/UPSERT); in HubSpot use the Import tool for org records and contacts. Map fields precisely: Legal_Name → Account.Name (SF) / Name (HS); Domain → Website (both CRMs); VAT, LEI, EUID → custom fields; NACE_Section/Division/Group/Class → custom picklists; Number_of_Employees → standard headcount; Annual_Revenue → revenue; Phone_E164 → Phone; BillingStreet/City/PostalCode/Country_ISO → address; Status (Active/Dissolved/Liquidation) → custom picklist; Source, Consent_Basis, Consent_Timestamp, Data_Origin → custom fields; Owner_Email → record owner. In Salesforce, load organizations to Accounts and people to Contacts or Leads; set External ID (e.g., VAT or LEI) for safe UPSERT. In HubSpot, set the primary domain field so later imports merge by domain; include Record_ID for consistent updates.

Deduplicate and normalize

Normalize before and after import: uppercase country codes (ISO 3166-1 alpha‑2), title case names, strip legal suffixes (Ltd, LLC, PLC, SA, GmbH, SARL, AE), standardize phone to E.164 (+countrycode…), lowercase emails, trim whitespace, unify street abbreviations (St → Street, Ave → Avenue), and validate postcodes against country patterns. Use robust keys: VAT (preferred), else LEI or (Domain + Country) or (Normalized_Name + Address + Country). Apply fuzzy matching (Jaro–Winkler ≥ 0.92 on names; address tokens with libpostal; phone exact after E.164). In Salesforce, create Matching Rules: 1) VAT exact; 2) Domain exact; 3) Name fuzzy + BillingPostalCode exact; enable Duplicate Rules to block or alert on create/update; schedule duplicate jobs monthly. In HubSpot, enable duplicate management (by email for contacts, by domain for org records); import with a stable Object ID or Domain to merge; run weekly duplicate review and merge via the UI or API. Keep the most recent Updated_At as master, merge child notes/activities, and log a merge audit trail.

Segment by NACE, location, and status; GDPR‑safe outreach; support channel

Build hierarchical segments using NACE: store both the 1‑letter section and 2/3/4‑digit levels; example filters: NACE like '62%' (software), NACE in ('C', 'G') for broad groups, or NACE_Class in ('62.01','62.02'). Location: filter by Country_ISO, Region/State, City, and PostalCode ranges; for multi‑site entities, set HQ_Flag and Branch_Flag to split segments. Status: include only Active; create separate lists for Liquidation or Dissolved to exclude from outreach and analytics. Layer firmographics: headcount buckets (1–10, 11–50, 51–200, 201+), revenue tiers, and presence of VAT/LEI for trust scoring.

GDPR steps: select lawful basis (Legitimate Interests for organizational contacts or Consent); run and file a Legitimate Interests Assessment if using LI; store fields: Lawful_Basis, Basis_Details, Basis_Date, Source_URL, Privacy_Notice_Version. For indirect data, issue Article 14 notice within 30 days or at first contact, including controller identity, purpose, rights, retention, and unsubscribe link. Send only role‑relevant emails to work addresses; avoid sensitive data; include one‑click opt‑out in every message; honor suppression within 48 hours; maintain a suppression list synced to both CRMs. Limit cadence (max 3 touches in 30 days, then 90‑day cool‑off); cap time‑to‑live (TTL) for unengaged records (e.g., 12–24 months). Document Data Processing Agreements with tools/vendors; perform a DPIA for large‑scale outreach; restrict access via role‑based permissions; audit exports and API keys monthly.

Support channel: open a ticket via email or portal with sample rows (max 50), target CRM, and desired mapping; expected first reply within 4 working hours and mapping fixes within 1 day. For urgent issues (import failures, API errors, dedupe misfires), use the hotline or Slack/Teams bridge; runtime monitoring provides webhook and batch‑import alerts. A knowledge base covers field dictionaries, NACE picklists, sample CSVs, and dedupe recipes; quarterly Q&A sessions address advanced segmentation and GDPR updates.

Q&A:

What exactly is included in the Cyprus Business Register Company Database?

The dataset aggregates public records from the Department of Registrar of Companies and Intellectual Property (DRCIP) and aligned open sources. Typical fields: company name (English/Greek where available); company number (e.g., HE123456); legal form (Ltd, Plc, partnership, foreign branch, business name); incorporation/registration date; current status (active, struck off, dissolved, under liquidation); registered office address (street, city/district, postcode); activities (NACE code and plain‑language description where mapped); last annual return date and last filing date; directors and secretary (names, roles, appointment/resignation dates); shareholders where disclosed in public filings (not UBO/beneficial ownership); charges/mortgages summary; VAT number and VIES check flag where available; website and role-based email/phone if found on public company pages, with source attribution. Each record carries a last-verified timestamp and a source field so you can audit provenance.

How fresh is the data, and how often do you update it?

See also: Cyprus Companies Database Online Reliable Company Records.

See also: Order Official Cyprus Company Register Documents Online Now.

We run daily deltas against the official register and roll a full refresh every 30 days. The download packages are rebuilt weekly; the API exposes near‑daily changes (new incorporations, status changes, address updates, officer appointments). Every row includes last_seen and last_verified dates. Entities that are struck off or dissolved are retained with status and event dates rather than removed, so your historical joins stay intact.

What delivery options and formats do you offer?

You can choose instant download (CSV or XLSX), newline‑delimited JSON, or a PostgreSQL/MySQL dump for bulk loading. An HTTPS API is available for live lookups and incremental sync with pagination and updated-since filters. We also provide a data dictionary, sample files, and a schema map (company, officers, filings, charges) so you can mirror the structure in your warehouse. Optional add‑ons include address geocoding and NACE-to-NAICS mappings.

Is the database suitable for B2B outreach and compliance checks under EU privacy rules?

Yes, with conditions. The core of the dataset is company data from public records. Officer names are personal data, so if you process them, you should have a lawful basis and conduct a legitimate interest assessment. We do not bundle personal inboxes; where available, we prefer role mailboxes (e.g., info@, sales@) collected from official company websites, tagged with the source. For B2B email in the EU/UK, comply with GDPR and local e‑privacy rules (PECR, etc.), offer clear opt‑out, and avoid messaging private individuals without consent. For screening and KYB, the dataset works as a strong starting point: use the company number and, where present, VAT number to cross‑check with the DRCIP record and the EU VIES service. For regulated onboarding, keep in mind that UBO data in Cyprus sits in a dedicated register with restricted access; our file does not replace mandatory checks where a regulated KYC provider or official extract is required.

How is licensing and pricing structured, and can I redistribute the data?

See also: Order Cyprus Company Register Documents Online Now.

Two main options: a one‑off snapshot license or an annual subscription with updates and API access. Licenses are company‑wide for internal use; sharing outside your organization or embedding raw rows in a public product requires an add‑on redistribution right. Pricing reflects coverage, refresh cadence, and add‑ons (API, geocodes, industry mappings). You receive a tax invoice, and EU reverse charge can be applied where eligible. Support includes onboarding help, schema guidance, and re‑delivery if a package fails. Contact us for a sample and a quote matched to your use case.