BIZTRAC BETA
Other captive investment companies

OLSEN IT AS

Org. no. 913231325 Limited company (AS) Drammen Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 13,000
Operating profit NOK −2,000
Equity NOK 1.5m
Incorporated 2014
Share capital NOK 30,000

Signals

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

OLSEN IT AS is registered as a limited company in Drammen, Buskerud with organisation number 913231325. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Selskapets virksomhet er investering og deltakelse i andre virksomheter ved kjøp og eie av aksjer og andeler i andre selskaper, samt konsulentvirksomhet hva som herved står i forbindelse. I tillegg hva styret finner interessant for selskapet.”. The most recent filed accounts, for the 2025 financial year, show NOK 13,000 in revenue and NOK −2,000 in operating profit.

Key figures · 2025

Revenue
NOK 13,000
Operating profit
NOK −2,000
Equity
NOK 1.5m
Est. value
NOK 1.2m

Financial health · 2025

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

Who owns OLSEN IT AS?

RIKARD OLSEN
OLSEN IT AS
NOK 13,000 rev. · NOK −2,000 profit

OLSEN IT AS has 1 registered shareholder:

All shareholders and roles →

Which companies does OLSEN IT AS own?

OLSEN IT AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about OLSEN IT AS

Who owns OLSEN IT AS?

RIKARD OLSEN is the largest registered owner, with 100.0%.

What is the revenue of OLSEN IT AS?

OLSEN IT AS had revenue of NOK 13,000 in 2025.

Where is OLSEN IT AS based?

OLSEN IT AS has its business address in Drammen.

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.