BIZTRAC BETA
Uoppgitt

DAG SOLHEIM AS

Org. no. 990243859 Limited company (AS) Sunnfjord Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 54,000
Operating profit NOK −7,000
Equity NOK 6.0m
Incorporated 2006
Share capital NOK 100,000

Signals

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

DAG SOLHEIM AS is registered as a limited company in Sunnfjord, Vestland with organisation number 990243859. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2006. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Investeringar i aksjar, verdipapir og eigedom og det som dermed står i tilknyting, samt å drive med forretningsmessig tenesteyting.”. The most recent filed accounts, for the 2025 financial year, show NOK 54,000 in revenue and NOK −7,000 in operating profit.

Key figures · 2025

Revenue
NOK 54,000
Operating profit
NOK −7,000
Equity
NOK 6.0m
Est. value
NOK 4.0m

Financial health · 2025

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

Who owns DAG SOLHEIM AS?

DAG SOLHEIM
DAG SOLHEIM AS
NOK 54,000 rev. · NOK −7,000 profit

DAG SOLHEIM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does DAG SOLHEIM AS own?

DAG SOLHEIM AS holds stakes in 7 companies:

See the full ownership structure →

Frequently asked questions about DAG SOLHEIM AS

Who owns DAG SOLHEIM AS?

DAG SOLHEIM is the largest registered owner, with 100.0%.

What is the revenue of DAG SOLHEIM AS?

DAG SOLHEIM AS had revenue of NOK 54,000 in 2025.

Who is the general manager of DAG SOLHEIM AS?

Dag Solheim is registered as general manager of DAG SOLHEIM AS.

Where is DAG SOLHEIM AS based?

DAG SOLHEIM AS has its business address in Førde.

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.