Open Company Data in Uganda: Official Sources, APIs and Reuse Rights

Uganda has a commercially useful official company-data ecosystem, but it should be described as controlled official lookup plus official enrichment rather than a single free bulk register. The core route is the Uganda Registration Services Bureau (URSB), including registry search and OBRS/BRS online workflows. Around that core, PPDA and Uganda e-GP add procurement activity, URA adds TIN and taxpayer context, UBOS adds business-statistics context, Bank of Uganda and CMA Uganda add regulated-sector layers, Uganda Securities Exchange adds listed-company profiles, and GLEIF adds LEI matching for covered entities.

The previous CompaniesData Uganda page mapped the right source stack, but Wave 182 estimated it at about 1,885 words and found that it failed the newer deep-reference standard. This article rebuilds Uganda as a reference article with methodology, coverage and update-risk analysis, reuse checklist, source-by-source deep dives, practical manual/API/bulk options, missing data gaps, recommended data model, CompaniesData normalization value, Resource Pack, official sources and FAQ.

The safe editorial claim is narrow: Uganda has strong official sources for verification, registration workflows and enrichment. The unsafe claim is that every company record can be downloaded freely, reused without terms, or converted into sales-prospecting contact lists. A production dataset should preserve source provenance, access dates, field limitations and lawful-use notes beside every normalized record.

Key Takeaways

• Primary registry source: URSB is the official registry authority, with OBRS/BRS and registry-search routes supporting business registration and lookup workflows.
• Procurement is strong enrichment: PPDA and e-GP expose supplier, bid-notice, procurement and contract-award context, but not the full company universe.
• Tax and privacy need caution: URA TIN and taxpayer routes are useful for known-entity validation, not marketing permission.
• Regulators are partial layers: UBOS, Bank of Uganda, CMA Uganda, USE and GLEIF improve context but cover statistics, financial-sector, capital-market, listed-company or LEI subsets.
• No complete bulk claim: this cycle did not verify a complete free official URSB company-register bulk download or unrestricted company API.

Editorial Methodology

This article uses an official-sources-first method. Each source was classified by authority, access model, reuse note, business use and limitation, then checked under browser, Googlebot and Bingbot-style profiles. A source is treated as clean linked evidence only when it returns usable public content and matches expected semantics. Sources that fail status, challenge, timeout, TLS, crawler or semantic checks remain in the research map but are held from the clean linked matrix until manual review.

The content QA applies the current CompaniesData country-page bar: minimum 2,400 words, preferred 2,800 to 3,800, Key Takeaways, methodology, coverage/access/update risk, reuse checklist, source matrix, source-by-source deep dives, practical access options, missing-data gaps, recommended data model, CompaniesData value, grouped Resource Pack, official sources and expanded FAQ.

Evidence is separated by type. A registry route proves authority or lookup workflow, not necessarily bulk reuse. A procurement portal proves supplier events, not every registered company. A tax route supports validation but does not create outreach permission. Regulator, listed-company, statistics and LEI sources enrich subsets and should not be merged into a single unqualified company profile.

Coverage, Access and Update-Risk Analysis

Registry coverage: URSB is the core registry authority. URSB registry searches, OBRS and BRS support name search, company-service and document workflows. They are strong for manual verification and business registration context, but search routes, detailed extracts and certification workflows may be controlled, paid or account-based. Do not describe them as a complete open bulk register without direct official proof.

Procurement coverage: PPDA and Uganda e-GP add supplier, bid notice, procurement and contract-award context. The registered-suppliers route can be highly useful for public-sector sales intelligence and supplier matching. It remains an event and supplier layer; match suppliers back to URSB identity before deduplication.

Tax coverage: URA and TIN routes can support taxpayer-service context and known-entity validation. TINs and taxpayer fields need privacy, retention and purpose controls. They should not be mixed into email, phone or lead-list workflows without a separate lawful basis.

Statistics and regulated-sector coverage: UBOS provides business and industry publications and official statistics; Bank of Uganda covers supervised financial institutions; CMA Uganda covers capital-market licensees; USE covers listed companies; GLEIF provides structured LEI records for covered entities. These are valuable enrichment layers but partial by design.

Update risk: Uganda source routes may change through URSB/OBRS redesigns, e-GP maintenance, URA soft blocks, UBOS publication moves, regulator redesigns or crawler treatment differences. A public update should rerun source-live QA, WordPress render checks, canonical/sitemap crawler checks, source-logo rendering and supported indexing workflows after publication.

Reuse Checklist

• Preserve provenance: store source name, authority, URL, access date, profile result and extraction route for every claim.
• Check terms separately: URSB, OBRS/BRS, PPDA, e-GP, URA, UBOS, Bank of Uganda, CMA, USE and GLEIF can carry different access and reuse terms.
• No endorsement: do not imply that any Ugandan authority endorses a derived CompaniesData dataset.
• Bulk caution: do not claim complete free official URSB bulk data without direct proof for fields, licence and update cadence.
• Privacy controls: flag officers, owners, TINs, addresses, emails, phones and approved-person fields for purpose and retention review.
• Marketing separation: public registry, tax or procurement visibility is not consent for cold email, phone outreach or sales-prospecting enrichment.

Source Matrix

Source	Owner / authority	Access model	Reuse note	Main limitation
URSB main portal	Uganda Registration Services Bureau	public portal / business registration, IP, insolvency and registry services	URSB website, privacy and service terms	Authority portal and service context; not proof of unrestricted registry bulk reuse.
PPDA Uganda	Public Procurement and Disposal of Public Assets Authority	public procurement regulator portal and guidance	PPDA terms and procurement-publication rules	Procurement subset only; not the national company register.
Uganda e-GP registered suppliers	PPDA Uganda	public supplier listing route and supplier registration workflow	e-GP supplier-listing and portal terms	Supplier list is procurement-specific and needs registry matching.
URA search TIN route	Uganda Revenue Authority	TIN search / taxpayer-service route	URA e-services and privacy rules	May be soft-blocked or controlled; not contact-data permission.
Uganda Bureau of Statistics	Uganda Bureau of Statistics	public statistics portal and publications	UBOS terms and publication-specific rules	Aggregate/statistical context, not legal-entity registry identity.
UBOS statistical publications	Uganda Bureau of Statistics	public publications including business and industry reports	UBOS publication terms	Statistical/report layer, often historical or aggregate.
Bank of Uganda supervision	Bank of Uganda	public supervision pages and licensed institution categories	Bank of Uganda website and publication terms	Financial-sector subset only.
Capital Markets Authority Uganda	Capital Markets Authority Uganda	public regulator site / licensing and market-player context	CMA Uganda terms and publication rules	Sector-specific enrichment only.
CMA Uganda licensed firms	Capital Markets Authority Uganda	public licensee / approved-persons page	CMA Uganda publication terms	Capital-market subset and may include natural-person data.
Uganda Securities Exchange	Uganda Securities Exchange	public exchange site, listings and market data	USE market-data and website terms	Listed companies are a small subset of registered entities.
USE listed equities	Uganda Securities Exchange	public listed securities and equities page	USE issuer-page and market-data terms	Issuer pages cover listed securities only.
GLEIF LEI records for Uganda	Global Legal Entity Identifier Foundation	public JSON API	GLEIF API terms	LEI coverage is partial and skewed toward financial or cross-border entities.

Source-by-Source Deep Dives

URSB main portal

Authority: Uganda Registration Services Bureau. Type: official registration services authority. Access model: public portal / business registration, IP, insolvency and registry services. Reuse note: URSB website, privacy and service terms.

URSB is the primary Ugandan registry authority for business registration, IP and insolvency context. Use it for authority claims, not as proof of open bulk reuse.

Main limitation: Authority portal and service context; not proof of unrestricted registry bulk reuse.

PPDA Uganda

Authority: Public Procurement and Disposal of Public Assets Authority. Type: official procurement regulator. Access model: public procurement regulator portal and guidance. Reuse note: PPDA terms and procurement-publication rules.

PPDA and e-GP provide procurement-event evidence: suppliers, bid notices, awards and contract activity. Model them as events and match suppliers back to registry identity.

Main limitation: Procurement subset only; not the national company register.

Uganda e-GP registered suppliers

Authority: PPDA Uganda. Type: official registered-suppliers route. Access model: public supplier listing route and supplier registration workflow. Reuse note: e-GP supplier-listing and portal terms.

PPDA and e-GP provide procurement-event evidence: suppliers, bid notices, awards and contract activity. Model them as events and match suppliers back to registry identity.

Main limitation: Supplier list is procurement-specific and needs registry matching.

URA search TIN route

Authority: Uganda Revenue Authority. Type: official TIN search route. Access model: TIN search / taxpayer-service route. Reuse note: URA e-services and privacy rules.

URA routes support TIN and taxpayer-service context for known entities. Treat taxpayer fields as fiscal evidence with privacy, purpose and retention controls.

Main limitation: May be soft-blocked or controlled; not contact-data permission.

Uganda Bureau of Statistics

Authority: Uganda Bureau of Statistics. Type: official statistics authority. Access model: public statistics portal and publications. Reuse note: UBOS terms and publication-specific rules.

UBOS supports market sizing and business-statistics context. Store it as aggregate or report evidence, not legal-entity identity.

Main limitation: Aggregate/statistical context, not legal-entity registry identity.

UBOS statistical publications

Authority: Uganda Bureau of Statistics. Type: official statistical publications archive. Access model: public publications including business and industry reports. Reuse note: UBOS publication terms.

UBOS supports market sizing and business-statistics context. Store it as aggregate or report evidence, not legal-entity identity.

Main limitation: Statistical/report layer, often historical or aggregate.

Bank of Uganda supervision

Authority: Bank of Uganda. Type: central bank supervision and licensed-institution context. Access model: public supervision pages and licensed institution categories. Reuse note: Bank of Uganda website and publication terms.

Bank of Uganda supervision adds licensed financial-institution context. It is a regulated-sector subset, not the general company universe.

Main limitation: Financial-sector subset only.

Capital Markets Authority Uganda

Authority: Capital Markets Authority Uganda. Type: capital markets regulator. Access model: public regulator site / licensing and market-player context. Reuse note: CMA Uganda terms and publication rules.

CMA Uganda provides capital-market regulator and licensee context. It is useful for compliance enrichment but sector-specific and may include natural-person data.

Main limitation: Sector-specific enrichment only.

CMA Uganda licensed firms

Authority: Capital Markets Authority Uganda. Type: capital-market licensed firms and approved persons. Access model: public licensee / approved-persons page. Reuse note: CMA Uganda publication terms.

CMA Uganda provides capital-market regulator and licensee context. It is useful for compliance enrichment but sector-specific and may include natural-person data.

Main limitation: Capital-market subset and may include natural-person data.

Uganda Securities Exchange

Authority: Uganda Securities Exchange. Type: regulated exchange and listed-company context. Access model: public exchange site, listings and market data. Reuse note: USE market-data and website terms.

USE is the listed-company and market-data layer. It supports issuer enrichment, but listed entities are a small subset of registered businesses.

Main limitation: Listed companies are a small subset of registered entities.

USE listed equities

Authority: Uganda Securities Exchange. Type: listed equities route. Access model: public listed securities and equities page. Reuse note: USE issuer-page and market-data terms.

USE is the listed-company and market-data layer. It supports issuer enrichment, but listed entities are a small subset of registered businesses.

Main limitation: Issuer pages cover listed securities only.

GLEIF LEI records for Uganda

Authority: Global Legal Entity Identifier Foundation. Type: LEI API. Access model: public JSON API. Reuse note: GLEIF API terms.

GLEIF provides structured LEI records for covered Ugandan entities. It helps global matching; lack of an LEI is not evidence that a company does not exist.

Main limitation: LEI coverage is partial and skewed toward financial or cross-border entities.

Held Source-Risk Findings

Current result: the following routes remain in the research map but are not treated as clean linked evidence for this article. They need manual browser, TLS, semantic, crawler or source-terms review before publication.

• URSB registry searches: held. Reason: browser status=200 semantic=False challenge=False; googlebot status=200 semantic=False challenge=False; bingbot status=200 semantic=False challenge=False
• URSB Online Business Registry System: held. Reason: browser status=200 semantic=False challenge=False; googlebot status=200 semantic=False challenge=False; bingbot status=200 semantic=False challenge=False
• URSB BRS name search: held. Reason: browser status=200 semantic=False challenge=True; googlebot status=200 semantic=False challenge=True; bingbot status=200 semantic=False challenge=True
• Uganda e-GP portal: held. Reason: googlebot status=ReadTimeout semantic=False challenge=True
• Uganda Revenue Authority: held. Reason: browser status=200 semantic=False challenge=False; googlebot status=200 semantic=False challenge=False; bingbot status=200 semantic=False challenge=False

Practical Manual, API and Bulk Options

Manual registry verification: start with URSB registry searches, OBRS or BRS name search for known names, registration references and status context. Store the search term, result date, source route, public identifier where lawful and confidence. Treat legal documents and certification as controlled evidence unless reuse terms explicitly allow broader use.

Procurement enrichment: use PPDA and e-GP for supplier registration, bid notices, awards, contract activity and public-buyer context. Store procurement as events: procuring entity, supplier, notice or award, reference number, date, value where public, source URL and match confidence.

Tax, statistics and regulator enrichment: use URA for TIN/taxpayer context, UBOS for business-statistics benchmarks, Bank of Uganda for supervised financial institutions, CMA Uganda for capital-market participants, USE for listed entities and GLEIF for LEI records. Keep these as enrichment tables with source-specific limitations.

API and bulk status: GLEIF is a clean structured API for LEI-covered entities. e-GP provides public procurement routes. This cycle did not verify a complete official URSB bulk company-register download, so registry bulk reuse remains blocked pending direct official proof.

Missing Data Gaps

• Complete registry bulk: no complete free official URSB company-register bulk file was verified.
• Controlled documents: detailed searches, legal documents, extracts and certification may require login, payment or purpose-specific use.
• Beneficial ownership: no complete lawful public beneficial-ownership dataset was cleared for automatic publication.
• Procurement matching: e-GP supplier names and references may not align cleanly with URSB records.
• Natural-person fields: owners, approved persons, directors, TINs and contact details require privacy review.
• Contact enrichment: official company data does not provide business email, phone or lead-list permission.

Recommended Data Model

A Uganda dataset should use a registry-first core with separate enrichment layers. The core entity table should include normalized legal name, public registration reference where lawful, legal form, status evidence, jurisdiction, source authority, source route, access date and confidence. It should not flatten URSB, URA, procurement and market data into one unqualified profile.

Use separate tables for URSB/OBRS/BRS observations, document-service evidence, URA taxpayer context, PPDA/e-GP procurement events, UBOS statistical reports, Bank of Uganda supervised institutions, CMA Uganda licensees and approved persons, USE issuers and GLEIF LEIs. Every field should carry source URL, update date, access model and reuse note.

The matching layer should be conservative: official identifiers first, then normalized names, alternative spellings, addresses, sector, procurement supplier names, regulator evidence, exchange symbols and LEI metadata. Ambiguous matches should stay reviewable.

CompaniesData Normalization and Enrichment Value

CompaniesData adds value in Uganda by turning scattered official evidence into a structured, auditable business dataset. Manual researchers have to move between URSB, OBRS/BRS, PPDA, e-GP, URA, UBOS, Bank of Uganda, CMA Uganda, USE and GLEIF, each with different formats, access models, privacy implications and field meanings.

A normalized CompaniesData workflow can standardize names, deduplicate entities, preserve provenance, match procurement activity to registry identity, link LEIs and listed-company records, flag taxpayer and natural-person sensitivity, and provide exports for research, compliance screening, CRM hygiene and analysis. For English and international contact-data needs, the owned route is CompaniesData.cloud. Official-source company identity and compliant contact enrichment remain separate workflows.

Grouped Resource Pack

Official Sources

• URSB main portal – Uganda Registration Services Bureau
• PPDA Uganda – Public Procurement and Disposal of Public Assets Authority
• Uganda e-GP registered suppliers – PPDA Uganda
• URA search TIN route – Uganda Revenue Authority
• Uganda Bureau of Statistics – Uganda Bureau of Statistics
• UBOS statistical publications – Uganda Bureau of Statistics
• Bank of Uganda supervision – Bank of Uganda
• Capital Markets Authority Uganda – Capital Markets Authority Uganda
• CMA Uganda licensed firms – Capital Markets Authority Uganda
• Uganda Securities Exchange – Uganda Securities Exchange
• USE listed equities – Uganda Securities Exchange
• GLEIF LEI records for Uganda – Global Legal Entity Identifier Foundation

FAQ

What is the best first source for company data in Uganda?

Start with URSB and its OBRS/BRS registry-search routes. Then add PPDA/e-GP, URA, UBOS, Bank of Uganda, CMA Uganda, USE and GLEIF depending on the use case.

Does Uganda have a complete free official company bulk download?

Not verified in this cycle. Public search and service workflows exist, but a search interface or certification route is not the same as a complete open bulk API.

Can e-GP supplier data replace registry data?

No. e-GP supplier and award records are valuable procurement signals, but they cover procurement participants and events. Match them back to URSB identity.

Can URA TIN data be used for outreach?

No. TIN and taxpayer context is fiscal evidence. It needs purpose, privacy and source-terms controls and is not permission for cold email, calls or lead lists.

Why include UBOS, BOU, CMA, USE and GLEIF?

They provide statistics, supervised-financial-institution, capital-market, listed-company and global identifier context. Each layer enriches the profile but remains partial.

How does CompaniesData help?

CompaniesData normalizes names, reconciles official sources, tracks provenance, flags limitations and separates company identity from contact-data workflows.