BIZTRAC BETA
COMPANY REGISTER PROFILE
924889462 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

ØLBERG INVEST AS

Org. no. 924889462 Limited company (AS) Stavanger Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −94,000
Incorporated 2020
Share capital NOK 4.8m

Signals

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

ØLBERG INVEST AS is registered as a limited company in Stavanger, Rogaland with organisation number 924889462. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 4.8m, divided into 4827 shares. The company's stated purpose is: “Investeringer i verdipapirer og eiendom.”.

Key figures · 2025

Operating profit
NOK −94,000
▼ −1 %

Financial health · 2025

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

Who owns ØLBERG INVEST AS?

ØLBERG INVEST AS has 13 registered shareholders:

All shareholders and roles →

Which companies does ØLBERG INVEST AS own?

ØLBERG INVEST AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about ØLBERG INVEST AS

Who owns ØLBERG INVEST AS?

HØJEN INVEST AS is the largest registered owner, with 10.7%.

Where is ØLBERG INVEST AS based?

ØLBERG INVEST AS has its business address in Stavanger.

Property

Business address c/o Asle Stenvaagnes Vedeveien 37, 4026 Stavanger
Cadastral unit 1103-28/282/0/0
Building Enebolig · 1 unit

2 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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

Report a problem

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