biztrac. BETA
COMPANY REGISTER PROFILE
925311189 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Site preparation

OTTADALEN HOLDING AS

Org. no. 925311189 Limited company (AS) Sel Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −22,000
Equity NOK 23.8m
Incorporated 2020
Share capital NOK 374,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−22k kr).
  • Nylig endring 2026-08-25 Adresseendring registrert 2026-08-25.

OTTADALEN HOLDING AS is registered as a limited company in Sel, Innlandet with organisation number 925311189. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2020. Registered share capital is NOK 374,000, divided into 850 shares. The company's stated purpose is: “Eie og forvalte aksjer og andeler i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −22,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −22,000
▲ +69 %
Equity
NOK 23.8m
▲ +1 %
Est. value
NOK 11.0m

Financial health · 2025

Liquidity
7.14
Very good
Current assets ÷ current liabilities
Profitability
0.9%
Not satisfactory
Return on total assets
Solidity
94.3%
Very good
Equity as a share of total capital

Who owns OTTADALEN HOLDING AS?

OTTADALEN HOLDING AS has 4 registered shareholders:

All shareholders and roles →

Which companies does OTTADALEN HOLDING AS own?

OTTADALEN HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about OTTADALEN HOLDING AS

Who owns OTTADALEN HOLDING AS?

Torbjørn Bråten is the largest registered owner, with 65.4%.

What is the revenue of OTTADALEN HOLDING AS?

OTTADALEN HOLDING AS had revenue of NOK 0 in 2025.

Where is OTTADALEN HOLDING AS based?

OTTADALEN HOLDING AS has its business address in Otta.

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.