biztrac. BETA
COMPANY REGISTER PROFILE
990324492 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Investigation and private security activities

ORINOCO AS

Org. no. 990324492 Limited company (AS) Oslo Incorporated 2006 Active
Revenue 2025 NOK 14.4m
Operating profit NOK 9.7m
Equity NOK 330.3m
Incorporated 2006
Share capital NOK 1.5m

Signals

1 flags
  • Nylig endring 2026-09-21 Aksjekapital registrert 2026-09-21.

ORINOCO AS is registered as a limited company in Oslo, Oslo with organisation number 990324492. The business is classified under investigation and private security activities (NACE 80.010). The company was incorporated in 2006. Registered share capital is NOK 1.5m, divided into 148678 shares. The company's stated purpose is: “Deltagelse i alarmvirksomhet, import, handel, agentur og alt som står i forbindelse dermed, samt investeringer, garantistillelser og deltagelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 14.4m in revenue and NOK 9.7m in operating profit.

Key figures · 2025

Revenue
NOK 14.4m
▼ −2 %
Operating profit
NOK 9.7m
▼ −61 %
Equity
NOK 330.3m
▲ +1 %
Est. value
NOK 215.3m

Financial health · 2025

Liquidity
9.47
Very good
Current assets ÷ current liabilities
Profitability
3.0%
Weak
Return on total assets
Solidity
97.8%
Very good
Equity as a share of total capital

Who owns ORINOCO AS?

ORINOCO AS
NOK 14.4m rev. · NOK 9.7m profit

ORINOCO AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ORINOCO AS own?

ORINOCO AS holds stakes in 16 companies:

See the full ownership structure →

Frequently asked questions about ORINOCO AS

Who owns ORINOCO AS?

Nicolas Brun-Lie is the largest registered owner, with 100.0%.

What is the revenue of ORINOCO AS?

ORINOCO AS had revenue of NOK 14.4m in 2025.

Where is ORINOCO AS based?

ORINOCO AS has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.