BIZTRAC BETA
Uoppgitt

ØVRE ONSAKER HOLDING AS

Org. no. 823557582 Limited company (AS) Hole Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK 0
Equity NOK 5.9m
Incorporated 2019
Share capital NOK 130,000

ØVRE ONSAKER HOLDING AS is registered as a limited company in Hole, Buskerud with organisation number 823557582. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2019. Registered share capital is NOK 130,000, divided into 30 shares. The company's stated purpose is: “Investere i aksjer og andre produkter/tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 5.9m
Est. value
NOK 4.0m

Financial health · 2024

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

Who owns ØVRE ONSAKER HOLDING AS?

TORBJØRN SLÅTTO
ØVRE ONSAKER HOLDING AS
NOK 0 rev. · NOK 0 profit

ØVRE ONSAKER HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ØVRE ONSAKER HOLDING AS own?

ØVRE ONSAKER HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ØVRE ONSAKER HOLDING AS

Who owns ØVRE ONSAKER HOLDING AS?

TORBJØRN SLÅTTO is the largest registered owner, with 100.0%.

What is the revenue of ØVRE ONSAKER HOLDING AS?

ØVRE ONSAKER HOLDING AS had revenue of NOK 0 in 2024.

Who is the general manager of ØVRE ONSAKER HOLDING AS?

Torbjørn Slåtto is registered as general manager of ØVRE ONSAKER HOLDING AS.

Where is ØVRE ONSAKER HOLDING AS based?

ØVRE ONSAKER HOLDING AS has its business address in Røyse.

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.