BIZTRAC BETA
Rental and operating of own or leased real estate

O H SLÅKE INVEST AS

Org. no. 975780392 Limited company (AS) Frogn Incorporated 1995 Active
Ownership graph ↗
Revenue 2024 NOK 16.1m
Operating profit NOK 6.0m
Equity NOK 197.4m
Incorporated 1995
Share capital NOK 1.0m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

O H SLÅKE INVEST AS is registered as a limited company in Frogn, Akershus with organisation number 975780392. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1995. Registered share capital is NOK 1.0m, divided into 400 shares. The company's stated purpose is: “Eiendoms- og investeringsvirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 16.1m in revenue and NOK 6.0m in operating profit.

Key figures · 2024

Revenue
NOK 16.1m
Operating profit
NOK 6.0m
Equity
NOK 197.4m
Est. value
NOK 146.7m

Financial health · 2024

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

Who owns O H SLÅKE INVEST AS?

HAKTOR SLÅKE
O H SLÅKE INVEST AS
NOK 16.1m rev. · NOK 6.0m profit

O H SLÅKE INVEST AS has 4 registered shareholders:

All shareholders and roles →

Which companies does O H SLÅKE INVEST AS own?

O H SLÅKE INVEST AS holds stakes in 16 companies:

See the full ownership structure →

Frequently asked questions about O H SLÅKE INVEST AS

Who owns O H SLÅKE INVEST AS?

HAKTOR SLÅKE is the largest registered owner, with 30.0%.

What is the revenue of O H SLÅKE INVEST AS?

O H SLÅKE INVEST AS had revenue of NOK 16.1m in 2024.

Where is O H SLÅKE INVEST AS based?

O H SLÅKE INVEST AS has its business address in Drøbak.

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.