BIZTRAC BETA
Uoppgitt

DVALE FJELLSTUE AS

Org. no. 931135058 Limited company (AS) Ål Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −8,000
Equity NOK 436,000
Incorporated 2023
Share capital NOK 278,000

Signals

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

DVALE FJELLSTUE AS is registered as a limited company in Ål, Buskerud with organisation number 931135058. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 278,000, divided into 37 shares. The company's stated purpose is: “Investeringer, forvaltning, drift og rådgivning samt annen tjenesteyting innenfor industri, energi, eiendom og lignede virksomhet, herunder ved eierskap og investering i annen virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −8,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −8,000
Equity
NOK 436,000
Est. value
NOK 570,000

Financial health · 2025

Liquidity
Not available
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 DVALE FJELLSTUE AS?

KNUT MARTIN KARLSEN
DVALE FJELLSTUE AS
NOK 0 rev. · NOK −8,000 profit

DVALE FJELLSTUE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does DVALE FJELLSTUE AS own?

DVALE FJELLSTUE AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about DVALE FJELLSTUE AS

Who owns DVALE FJELLSTUE AS?

KNUT MARTIN KARLSEN is the largest registered owner, with 100.0%.

What is the revenue of DVALE FJELLSTUE AS?

DVALE FJELLSTUE AS had revenue of NOK 0 in 2025.

Where is DVALE FJELLSTUE AS based?

DVALE FJELLSTUE AS has its business address in Torpo.

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.