BIZTRAC BETA
Site preparation

BRØRNE DAGALID AS

Org. no. 977341906 Limited company (AS) Vinje Incorporated 1997 Active
Ownership graph ↗
Revenue 2024 NOK 4.5m
Operating profit NOK −490,000
Equity NOK 6.1m
Incorporated 1997
Share capital NOK 150,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−490k kr).

BRØRNE DAGALID AS is registered as a limited company in Vinje, Telemark with organisation number 977341906. The business is classified under site preparation (NACE 43.120). The company was incorporated in 1997. Registered share capital is NOK 150,000. The company's stated purpose is: “Maskinentreprenør, samt utleige av fast eigedom og det som naturleg høyrer til under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.5m in revenue and NOK −490,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.5m
Operating profit
NOK −490,000
Equity
NOK 6.1m
Est. value
NOK 4.2m

Financial health · 2024

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

Who owns BRØRNE DAGALID AS?

HALVOR DAGALID
BRØRNE DAGALID AS
NOK 4.5m rev. · NOK −490,000 profit

BRØRNE DAGALID AS has 2 registered shareholders:

All shareholders and roles →

Which companies does BRØRNE DAGALID AS own?

BRØRNE DAGALID AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BRØRNE DAGALID AS

Who owns BRØRNE DAGALID AS?

HALVOR DAGALID is the largest registered owner, with 50.0%.

What is the revenue of BRØRNE DAGALID AS?

BRØRNE DAGALID AS had revenue of NOK 4.5m in 2024.

Who is the general manager of BRØRNE DAGALID AS?

Olav Henning Dagalid is registered as general manager of BRØRNE DAGALID AS.

Where is BRØRNE DAGALID AS based?

BRØRNE DAGALID AS has its business address in Rauland.

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.