BIZTRAC BETA
Other captive investment companies

ORN INVEST AS

Org. no. 993350796 Limited company (AS) Lier Incorporated 2008 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −37,000
Equity NOK 6.1m
Incorporated 2008
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−37k kr).

ORN INVEST AS is registered as a limited company in Lier, Buskerud with organisation number 993350796. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2008. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Selskapets virksomhet er selv, gjennom hel- og deleide selskaper eller ved samarbeide med andre virksomheter, å forestå investeringer, eie og forvalte aksjer, andeler og fast eiendom, og all hermed forbundet virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −37,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −37,000
Equity
NOK 6.1m
Est. value
NOK 16.5m

Financial health · 2025

Liquidity
6.95
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
85.6%
Very good
Equity as a share of total capital

Who owns ORN INVEST AS?

ODDBJØRN RØNNINGEN
ORN INVEST AS
NOK 0 rev. · NOK −37,000 profit

ORN INVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ORN INVEST AS

Who owns ORN INVEST AS?

ODDBJØRN RØNNINGEN is the largest registered owner, with 100.0%.

What is the revenue of ORN INVEST AS?

ORN INVEST AS had revenue of NOK 0 in 2025.

Who is the general manager of ORN INVEST AS?

Oddbjørn Rønningen is registered as general manager of ORN INVEST AS.

Where is ORN INVEST AS based?

ORN INVEST AS has its business address in Lierskogen.

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

Report a problem

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