BIZTRAC BETA
Construction of residential and non-residential buildings

DÆHLI LANDBRUK AS

Org. no. 825898492 Limited company (AS) Råde Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 652,000
Operating profit NOK 89,000
Equity NOK 405,000
Incorporated 2020
Share capital NOK 30,000

DÆHLI LANDBRUK AS is registered as a limited company in Råde, Østfold with organisation number 825898492. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Entreprenøroppdrag innenfor landbruk og andre med egne maskiner. Tømreroppdrag med salg av varer og tjenester i den forbindelse. Utleie av maskiner. Herunder også å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 652,000 in revenue and NOK 89,000 in operating profit.

Key figures · 2024

Revenue
NOK 652,000
Operating profit
NOK 89,000
Equity
NOK 405,000
Est. value
NOK 419,000

Financial health · 2024

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

Who owns DÆHLI LANDBRUK AS?

MIKAL DÆHLI UNNERUD
DÆHLI LANDBRUK AS
NOK 652,000 rev. · NOK 89,000 profit

DÆHLI LANDBRUK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DÆHLI LANDBRUK AS

Who owns DÆHLI LANDBRUK AS?

MIKAL DÆHLI UNNERUD is the largest registered owner, with 100.0%.

What is the revenue of DÆHLI LANDBRUK AS?

DÆHLI LANDBRUK AS had revenue of NOK 652,000 in 2024.

Where is DÆHLI LANDBRUK AS based?

DÆHLI LANDBRUK AS has its business address in Saltnes.

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.