BIZTRAC BETA
COMPANY REGISTER PROFILE
915576249 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Business and other management consultancy activities

ASLAK DALEHAUG AS

Org. no. 915576249 Limited company (AS) Luster Incorporated 2015 Active
Ownership graph ↗
Operating profit NOK −29,000
Equity NOK 4.7m
Incorporated 2015
Share capital NOK 40,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−29k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

ASLAK DALEHAUG AS is registered as a limited company in Luster, Vestland with organisation number 915576249. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2015. Registered share capital is NOK 40,000, divided into 40000 shares. The company's stated purpose is: “Selskapets virksomhet er å drive med konsulentbistand.”.

Key figures · 2025

Operating profit
NOK −29,000
▼ −24 %
Equity
NOK 4.7m
▲ +13 %
Est. value
NOK 7.7m

Financial health · 2025

Liquidity
7.85
Very good
Current assets ÷ current liabilities
Profitability
9.2%
Satisfactory
Return on total assets
Solidity
33.6%
Good
Equity as a share of total capital

Who owns ASLAK DALEHAUG AS?

ASLAK DALEHAUG AS has 2 registered shareholders:

All shareholders and roles →

Which companies does ASLAK DALEHAUG AS own?

ASLAK DALEHAUG AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about ASLAK DALEHAUG AS

Who owns ASLAK DALEHAUG AS?

SIRI JOHANNE SOLBERG DALEHAUG is the largest registered owner, with 50.0%.

Who is the general manager of ASLAK DALEHAUG AS?

Aslak Dalehaug is registered as general manager of ASLAK DALEHAUG AS.

Where is ASLAK DALEHAUG AS based?

ASLAK DALEHAUG AS has its business address in Skjolden.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.