biztrac. BETA
COMPANY REGISTER PROFILE
989209531 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

OK INVEST HOLDING AS

Org. no. 989209531 Limited company (AS) Bærum Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −931,000
Equity NOK 120.1m
Incorporated 2005
Share capital NOK 260,000

Signals

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

OK INVEST HOLDING AS is registered as a limited company in Bærum, Akershus with organisation number 989209531. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 260,000, divided into 160 shares. The company's stated purpose is: “Kjøp, salg, investering i aksjer og andre verdipapirer samt fast eiendom med dertil tilhørende virksomhet.”.

Key figures · 2025

Operating profit
NOK −931,000
▼ −2391 %
Equity
NOK 120.1m
▲ +18 %
Est. value
NOK 91.8m

Financial health · 2025

Liquidity
23.17
Very good
Current assets ÷ current liabilities
Profitability
18.2%
Very good
Return on total assets
Solidity
95.1%
Very good
Equity as a share of total capital

Who owns OK INVEST HOLDING AS?

OK INVEST HOLDING AS
· NOK −931,000 profit

OK INVEST HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does OK INVEST HOLDING AS own?

OK INVEST HOLDING AS holds stakes in 13 companies:

See the full ownership structure →

Frequently asked questions about OK INVEST HOLDING AS

Who owns OK INVEST HOLDING AS?

Odd Kåre Markegård is the largest registered owner, with 100.0%.

Who is the general manager of OK INVEST HOLDING AS?

Odd Kåre Markegård is registered as general manager of OK INVEST HOLDING AS.

Where is OK INVEST HOLDING AS based?

OK INVEST HOLDING AS has its business address in Østerås.

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.