Luxembourg RCS Company Register Records

Luxembourg has a high-value company-data ecosystem, but it should not be described as a simple open bulk file. The most reliable editorial route starts with Luxembourg Business Registers and Guichet RCS/RESA guidance, then adds open-data governance, official statistics, procurement, financial-regulator, intellectual-property, exchange and LEI sources as separate layers.

This refresh replaces a short Luxembourg article that was useful as a source list but did not meet the current CompaniesData depth bar. The new version treats Luxembourg as a controlled, commercially important jurisdiction: official sources first, clear reuse limits, no overclaim around RCS bulk/API access, and explicit caution around beneficial ownership, personal data and marketing-contact use.

The safe answer is this: Luxembourg has strong official registry context and useful public-sector data infrastructure, but public availability is not the same as unrestricted scraping, a complete free API, a beneficial-ownership dataset for general reuse or a sales-prospecting contact list.

Key Takeaways

• Best official registry route: Luxembourg Business Registers plus Guichet RCS/RESA guidance form the core legal-disclosure route.
• Best open-data context: data.public.lu, the Luxembourg open-data policy and LETZDATA help identify public-sector data routes, but each dataset still needs its own licence and access review.
• Best enrichment layers: STATEC, public procurement, CSSF entity search, IPIL, LuxSE and GLEIF add market, regulator, IP, issuer and LEI signals.
• Key blocked or held sources: direct LBR /mjrcs/ and /mjrcs-rbe/ paths returned 404, the old CSSF supervised-entities URL returned 404, BOIP looked controlled, and EU VIES was blocked for bot profiles.
• Main compliance boundary: company-register data is not marketing-contact consent. Business emails, phone numbers, lead lists and outreach enrichment require a separate lawful basis.

Editorial Methodology

This article follows the CompaniesData country-source standard. Official registry and government sources are prioritized first. Public-sector catalogues, statistics, procurement, regulator, IP, exchange and LEI sources are used as supporting layers only when they return real content under normal browser and search-bot-style checks. Private contact-data competitors are not used as evidence for official reuse rights.

Every final linked source was checked from this environment on 2026-06-14. A source can be official and still be held if it returns a 404, challenge page, bot-profile block, unclear semantics or a route that is too sensitive for automatic publication. Source logos in the matrix and resource pack are decorative favicon cues only; the evidence remains the official URL, source owner, access model and reuse note.

Coverage, Access and Update-Risk Analysis

Luxembourg should be modelled as a registry-led identity stack with separate enrichment layers. LBR and RCS/RESA guidance explain the legal-publication backbone. Open-data portals and catalogues explain public-sector reuse infrastructure. STATEC provides aggregate economic and business-demography context. Procurement portals identify public-contract activity. CSSF identifies supervised financial entities. IPIL and LuxSE provide IP and capital-markets context. GLEIF provides LEI records for entities that participate in the LEI system.

Registry coverage: a Luxembourg company profile should store legal name, register number where available, legal form, status, registered-office/address fields where lawful, source URL, access date and document or event provenance. If a field involves a natural person, representative, address, beneficial owner or sensitive legal notice, it should carry a privacy and lawful-use flag.

Access model: Luxembourg has strong public official sources, but the current clean evidence does not justify a claim that the complete RCS is available as a free reusable bulk download or open API. Some material is portal, document, publication, account, fee or terms controlled.

Update risk: RCS filings, RESA publications, open datasets, statistics, procurement notices, CSSF records, IP context, issuer information and LEI records update on different schedules. A normalized dataset should carry source-specific timestamps rather than one generic Luxembourg freshness date.

Reuse Checklist

• Start with authority: record whether the source is LBR, Guichet, a ministry, a data catalogue, STATEC, procurement, CSSF, IPIL, LuxSE or GLEIF.
• Separate access from reuse: a public web page, search portal or document service is not automatically a bulk reuse licence.
• Keep source provenance: preserve source URL, owner, access date, source route, update date and reuse note.
• Flag personal data: officers, representatives, beneficial owners, addresses and legal notices need GDPR and proportionality review.
• Do not overclaim RBE: beneficial ownership should remain special-review material unless source terms, lawful basis and privacy controls are explicitly cleared.
• Avoid endorsement language: do not imply that Luxembourg authorities endorse a derived CompaniesData dataset.
• Keep contact data separate: for English or international audiences, route compliant enrichment to CompaniesData.cloud, not to third-party contact-data sellers.

Practical Manual, API and Bulk Options

Manual verification: use LBR and Guichet as the official starting point for company-register context, publications and legal-disclosure workflows. This is suitable for verification and source understanding, but not enough by itself for a bulk ingestion claim.

Open-data and catalogue work: use data.public.lu and LETZDATA to discover public-sector datasets and governance context. Check each dataset licence, metadata, API route, file format, update date and attribution requirement before reuse.

Statistics and market sizing: use STATEC for aggregate context, market benchmarking and business-demography analysis. Do not use aggregate statistics as a substitute for legal entity profiles.

Procurement enrichment: PMP and marches.public.lu add public-sector tender and supplier signals. They are useful for sales and market analysis, but they identify public-contract activity rather than the full company universe.

Regulator, IP, exchange and LEI enrichment: CSSF, IPIL, LuxSE and GLEIF add sector-specific signals. These layers should be matched back to the registry identity layer with confidence scores and field provenance.

Source-by-Source Deep Dives

1. Guichet RCS and RESA publication guidance

Authority: Guichet.lu / Luxembourg public administration. Source type: official registry guidance. Access model: public guidance page for RCS lodgings and RESA publication. Reuse position: official public information; cite source; not a bulk licence.

Explains how RCS filings and RESA publicity fit into Luxembourg company disclosure. In a CompaniesData workflow, this layer should be stored with source owner, URL, access date, native identifier, field scope, language and reuse note before it is joined to other Luxembourg evidence.

Limitations and operating notes: Guidance source only. It is not a machine-readable company register or a permission to republish every filing. Luxembourg is commercially useful because the official-source stack is broad, but that breadth does not remove source-by-source checks for API access, document fees, attribution, personal data, beneficial ownership, update cadence or marketing use.

2. Luxembourg Business Registers

Authority: Luxembourg Business Registers. Source type: official registry portal. Access model: official portal for RCS/RBE/eCDF services and register navigation. Reuse position: portal and service-specific terms; cite LBR; check document and personal-data limits.

Primary official route for Luxembourg company-register services and register context. In a CompaniesData workflow, this layer should be stored with source owner, URL, access date, native identifier, field scope, language and reuse note before it is joined to other Luxembourg evidence.

Limitations and operating notes: Portal access is not proof of a free complete reusable bulk API; some services are search, document, account or fee based. Luxembourg is commercially useful because the official-source stack is broad, but that breadth does not remove source-by-source checks for API access, document fees, attribution, personal data, beneficial ownership, update cadence or marketing use.

3. data.public.lu

Authority: Luxembourg open-data portal. Source type: national open-data portal. Access model: dataset catalogue with dataset-level licences and APIs where published. Reuse position: dataset-specific open-data terms; check attribution and licence on each dataset.

Discovery layer for public datasets that can support company-data context and enrichment. In a CompaniesData workflow, this layer should be stored with source owner, URL, access date, native identifier, field scope, language and reuse note before it is joined to other Luxembourg evidence.

Limitations and operating notes: Catalogue presence does not prove complete RCS bulk coverage or contact-data permission. Luxembourg is commercially useful because the official-source stack is broad, but that breadth does not remove source-by-source checks for API access, document fees, attribution, personal data, beneficial ownership, update cadence or marketing use.

4. Luxembourg open-data policy

Authority: The Luxembourg Government. Source type: official policy context. Access model: policy and public-sector reuse context. Reuse position: policy context only; source-specific terms still control actual datasets.

Supports nuanced claims about open-data strategy and public-sector data reuse. In a CompaniesData workflow, this layer should be stored with source owner, URL, access date, native identifier, field scope, language and reuse note before it is joined to other Luxembourg evidence.

Limitations and operating notes: Not a company dataset, not a registry extract and not a bulk/API endpoint. This source is included as a conditional/context layer, so market-data, regulator, IP or policy terms must be checked before automated reuse. Luxembourg is commercially useful because the official-source stack is broad, but that breadth does not remove source-by-source checks for API access, document fees, attribution, personal data, beneficial ownership, update cadence or marketing use.

5. LETZDATA public sector data catalogue

Authority: LETZDATA / Luxembourg Data Factory. Source type: official data catalogue. Access model: public-sector data catalogue and governance layer. Reuse position: dataset-specific terms; Public Sector Data Catalogue context.

Helps teams locate public-sector datasets and governance information beyond the company register. In a CompaniesData workflow, this layer should be stored with source owner, URL, access date, native identifier, field scope, language and reuse note before it is joined to other Luxembourg evidence.

Limitations and operating notes: Dataset discovery layer; every dataset still needs its own access, licence and update review. Luxembourg is commercially useful because the official-source stack is broad, but that breadth does not remove source-by-source checks for API access, document fees, attribution, personal data, beneficial ownership, update cadence or marketing use.

6. STATEC statistics portal

Authority: STATEC. Source type: official statistics. Access model: statistics portal, publications and aggregate datasets. Reuse position: statistics reuse terms and source-reference requirements.

Provides business-demography, economic and coverage benchmarks around legal company data. In a CompaniesData workflow, this layer should be stored with source owner, URL, access date, native identifier, field scope, language and reuse note before it is joined to other Luxembourg evidence.

Limitations and operating notes: Aggregate statistics do not replace company-level register profiles. Luxembourg is commercially useful because the official-source stack is broad, but that breadth does not remove source-by-source checks for API access, document fees, attribution, personal data, beneficial ownership, update cadence or marketing use.

7. Luxembourg procurement platform PMP

Authority: Grand Duchy of Luxembourg public procurement platform. Source type: official procurement platform. Access model: public procurement notices and tenders. Reuse position: procurement-notice and portal-specific terms; cite source.

Adds public-sector demand, supplier and tender signals to known Luxembourg entities. In a CompaniesData workflow, this layer should be stored with source owner, URL, access date, native identifier, field scope, language and reuse note before it is joined to other Luxembourg evidence.

Limitations and operating notes: Procurement is a subset; it cannot be used as all-company coverage. Luxembourg is commercially useful because the official-source stack is broad, but that breadth does not remove source-by-source checks for API access, document fees, attribution, personal data, beneficial ownership, update cadence or marketing use.

8. marches.public.lu

Authority: Luxembourg public procurement portal. Source type: public procurement portal. Access model: procurement information portal and notices. Reuse position: procurement-specific terms and notice-level limits.

Supplementary route for public procurement context and supplier-market monitoring. In a CompaniesData workflow, this layer should be stored with source owner, URL, access date, native identifier, field scope, language and reuse note before it is joined to other Luxembourg evidence.

Limitations and operating notes: Tender coverage is partial and event-based; use as enrichment only. Luxembourg is commercially useful because the official-source stack is broad, but that breadth does not remove source-by-source checks for API access, document fees, attribution, personal data, beneficial ownership, update cadence or marketing use.

9. CSSF entity search

Authority: Commission de Surveillance du Secteur Financier. Source type: official financial-regulator entity search. Access model: regulated-entity search. Reuse position: sector-specific regulator terms; cite CSSF; no general company-register claim.

Financial-sector compliance enrichment for supervised Luxembourg entities. In a CompaniesData workflow, this layer should be stored with source owner, URL, access date, native identifier, field scope, language and reuse note before it is joined to other Luxembourg evidence.

Limitations and operating notes: Sector-specific; it covers regulated entities and does not replace RCS coverage. Luxembourg is commercially useful because the official-source stack is broad, but that breadth does not remove source-by-source checks for API access, document fees, attribution, personal data, beneficial ownership, update cadence or marketing use.

10. IPIL

Authority: Institut de la Propriete Intellectuelle Luxembourg. Source type: official intellectual-property institute. Access model: IP guidance, services and Luxembourg IP context. Reuse position: IP-specific terms; use as enrichment and context.

Adds intellectual-property context for Luxembourg businesses and IP-heavy sectors. In a CompaniesData workflow, this layer should be stored with source owner, URL, access date, native identifier, field scope, language and reuse note before it is joined to other Luxembourg evidence.

Limitations and operating notes: IP context is not company-register coverage and usually requires separate owner matching. Luxembourg is commercially useful because the official-source stack is broad, but that breadth does not remove source-by-source checks for API access, document fees, attribution, personal data, beneficial ownership, update cadence or marketing use.

11. Luxembourg Stock Exchange

Authority: Luxembourg Stock Exchange. Source type: official market and issuer portal. Access model: market, issuer and securities information portal. Reuse position: market-data and website terms; use as contextual enrichment only.

Issuer and securities context for listed or capital-markets-linked entities. In a CompaniesData workflow, this layer should be stored with source owner, URL, access date, native identifier, field scope, language and reuse note before it is joined to other Luxembourg evidence.

Limitations and operating notes: Market data may be licence-controlled and is not a national company register. This source is included as a conditional/context layer, so market-data, regulator, IP or policy terms must be checked before automated reuse. Luxembourg is commercially useful because the official-source stack is broad, but that breadth does not remove source-by-source checks for API access, document fees, attribution, personal data, beneficial ownership, update cadence or marketing use.

12. GLEIF LEI records for Luxembourg

Authority: GLEIF. Source type: global legal-entity identifier data. Access model: public API and open LEI data. Reuse position: GLEIF API and open-data terms.

LEI cross-checks for Luxembourg legal entities in finance, KYB and compliance workflows. In a CompaniesData workflow, this layer should be stored with source owner, URL, access date, native identifier, field scope, language and reuse note before it is joined to other Luxembourg evidence.

Limitations and operating notes: LEI coverage is a subset and should not be treated as comprehensive Luxembourg company coverage. Luxembourg is commercially useful because the official-source stack is broad, but that breadth does not remove source-by-source checks for API access, document fees, attribution, personal data, beneficial ownership, update cadence or marketing use.

Recommended Data Model

A practical Luxembourg dataset should be built around an entity table and separate source tables. The core table should hold normalized legal name, country, register identifier where available, legal form, status, address or registered-office fields where lawful, source URL, access date, update date and internal CompaniesData identifier. Separate tables should hold RCS/RESA events, public-data catalogue references, statistics context, procurement notices, CSSF supervised-entity matches, IP context, LuxSE issuer or market references and LEI records.

• Entity core: legal name, normalized name, register number, legal form, status, address fields, country and source confidence.
• Event layer: filings, publications, document references, procurement notices, regulator records, IP references and LEI updates.
• Provenance layer: source owner, exact URL, access model, licence or terms note, access date, parser version and update cadence.
• Risk flags: personal-data caution, RBE/beneficial-ownership special review, market-data licence caution, contact-data blocked and manual-review required.
• Delivery fields: normalized names, deduplicated identifiers, activity and geography segments, confidence scores and suppression markers.

Missing-Data Gaps

Luxembourg’s official source environment is strong, but several gaps matter for commercial users. The current live checks do not support a claim of a complete free RCS bulk/API. Direct LBR subpaths for RCS and RBE returned 404 from this node, so the article uses the LBR homepage and Guichet RCS/RESA guidance as stable evidence instead. Beneficial ownership needs special privacy and lawful-use clearance. CSSF, procurement, IPIL, LuxSE and GLEIF are valuable but partial.

The main operational gap is fragmentation. Company identity, legal events, open-data catalogues, statistics, procurement, regulator records, IP context, issuer context and LEI data live in different systems with different identifiers, languages, update schedules and reuse limits. A serious dataset needs normalization and provenance rather than a single scrape.

How CompaniesData Adds Value

CompaniesData turns the Luxembourg source stack into a usable dataset by normalizing names and identifiers, deduplicating entities, tracking source provenance, mapping regulator and procurement signals, adding LEI and IP context where available, and keeping personal-data and marketing-use flags separate from the company identity layer.

For Luxembourg, the value is not replacing official sources. The value is making them operational: matching records across sources, retaining access dates, separating registry facts from contact-data permissions, and packaging the result for CRM enrichment, market analysis, KYB and research workflows.

For English and international users, request a CompaniesData sample for Luxembourg if you need a practical dataset rather than a list of portals. For Spanish-speaking or Hispanic outreach workflows, CentraldeComunicacion.es is the preferred contact-data property.

Source Matrix

Source	Owner / authority	Access model	Reuse note	Main limitation
Guichet RCS and RESA publication guidance	Guichet.lu / Luxembourg public administration	public guidance page for RCS lodgings and RESA publication	official public information; cite source; not a bulk licence	Clean public source. Guidance source only. It is not a machine-readable company register or a permission to republish every filing.
Luxembourg Business Registers	Luxembourg Business Registers	official portal for RCS/RBE/eCDF services and register navigation	portal and service-specific terms; cite LBR; check document and personal-data limits	Clean public source. Portal access is not proof of a free complete reusable bulk API; some services are search, document, account or fee based.
data.public.lu	Luxembourg open-data portal	dataset catalogue with dataset-level licences and APIs where published	dataset-specific open-data terms; check attribution and licence on each dataset	Clean public source. Catalogue presence does not prove complete RCS bulk coverage or contact-data permission.
Luxembourg open-data policy	The Luxembourg Government	policy and public-sector reuse context	policy context only; source-specific terms still control actual datasets	Conditional context. Not a company dataset, not a registry extract and not a bulk/API endpoint.
LETZDATA public sector data catalogue	LETZDATA / Luxembourg Data Factory	public-sector data catalogue and governance layer	dataset-specific terms; Public Sector Data Catalogue context	Clean public source. Dataset discovery layer; every dataset still needs its own access, licence and update review.
STATEC statistics portal	STATEC	statistics portal, publications and aggregate datasets	statistics reuse terms and source-reference requirements	Clean public source. Aggregate statistics do not replace company-level register profiles.
Luxembourg procurement platform PMP	Grand Duchy of Luxembourg public procurement platform	public procurement notices and tenders	procurement-notice and portal-specific terms; cite source	Clean public source. Procurement is a subset; it cannot be used as all-company coverage.
marches.public.lu	Luxembourg public procurement portal	procurement information portal and notices	procurement-specific terms and notice-level limits	Clean public source. Tender coverage is partial and event-based; use as enrichment only.
CSSF entity search	Commission de Surveillance du Secteur Financier	regulated-entity search	sector-specific regulator terms; cite CSSF; no general company-register claim	Clean public source. Sector-specific; it covers regulated entities and does not replace RCS coverage.
IPIL	Institut de la Propriete Intellectuelle Luxembourg	IP guidance, services and Luxembourg IP context	IP-specific terms; use as enrichment and context	Clean public source. IP context is not company-register coverage and usually requires separate owner matching.
Luxembourg Stock Exchange	Luxembourg Stock Exchange	market, issuer and securities information portal	market-data and website terms; use as contextual enrichment only	Conditional context. Market data may be licence-controlled and is not a national company register.
GLEIF LEI records for Luxembourg	GLEIF	public API and open LEI data	GLEIF API and open-data terms	Clean public source. LEI coverage is a subset and should not be treated as comprehensive Luxembourg company coverage.

Resource Pack

Held Sources and Source-Risk Notes

The following sources remain researched but are not linked as clean evidence in the main matrix. They should be manually reviewed before a future RBE, VAT, BOIP or direct-register-access claim is published.

• LBR direct /mjrcs/ path: returned 404 for browser, Googlebot and Bingbot profiles; use the LBR homepage and Guichet guidance instead.
• LBR direct /mjrcs-rbe/ path: returned 404 for browser, Googlebot and Bingbot profiles; beneficial-ownership content remains a privacy and access-model caveat, not a clean open-data claim.
• Old CSSF supervised-entities URL: returned 404 in this cycle; replaced with the current CSSF entity-search application.
• BOIP direct public route: looked controlled/no-cache from this environment; use IPIL for Luxembourg IP context and hold BOIP for manual review.
• EU VIES: browser profile returned real content but Googlebot/Bingbot profiles received a web-filter 502; keep as contextual VAT-check knowledge only.

FAQ

What is the best starting point for Luxembourg company data?

Start with Luxembourg Business Registers and Guichet RCS/RESA guidance, then add open-data catalogues, STATEC statistics, procurement, CSSF, IPIL, LuxSE and GLEIF as separate enrichment layers.

Is Luxembourg company data available as a complete free bulk API?

The current clean evidence does not support that claim. Luxembourg has strong official sources and public-sector data infrastructure, but RCS bulk/API reuse must be verified source by source.

Can beneficial ownership data be treated as open company data?

No automatic conclusion should be made. RBE and beneficial-ownership material require special review for access model, lawful basis, privacy, proportionality, sanctions/compliance use and retention.

Can I use Luxembourg registry data for cold email marketing?

Not automatically. Registry visibility is not marketing consent. Emails, phone numbers, lead lists and outreach segmentation require a separate lawful basis and suppression process.

Why use CompaniesData instead of collecting Luxembourg sources manually?

Manual collection is slow because sources differ by identifier, language, format, update cadence and reuse rights. CompaniesData adds normalization, deduplication, provenance, enrichment joins and practical delivery formats.

Official Sources

• Guichet RCS and RESA publication guidance – official registry guidance
• Luxembourg Business Registers – official registry portal
• data.public.lu – national open-data portal
• Luxembourg open-data policy – official policy context
• LETZDATA public sector data catalogue – official data catalogue
• STATEC statistics portal – official statistics
• Luxembourg procurement platform PMP – official procurement platform
• marches.public.lu – public procurement portal
• CSSF entity search – official financial-regulator entity search
• IPIL – official intellectual-property institute
• Luxembourg Stock Exchange – official market and issuer portal
• GLEIF LEI records for Luxembourg – global legal-entity identifier data