BIZTRAC BETA
Manufacture of other builders' carpentry and joinery

DALUT AS

Org. no. 911721244 Limited company (AS) Tana Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 49,000
Operating profit NOK −11,000
Equity NOK −43,000
Incorporated 2013
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−43k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−11k kr).

DALUT AS is registered as a limited company in Tana, Finnmark with organisation number 911721244. The business is classified under manufacture of other builders' carpentry and joinery (NACE 16.230). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Produsere elementlavvoer, sneskotergarasjer, bilgarasjer, grillstuer mv. Reiseliv. Fjellturisme. ”. The most recent filed accounts, for the 2024 financial year, show NOK 49,000 in revenue and NOK −11,000 in operating profit.

Key figures · 2024

Revenue
NOK 49,000
Operating profit
NOK −11,000
Equity
NOK −43,000

Financial health · 2024

Liquidity
0.21
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-373.4%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns DALUT AS?

Per Andreas Holm
DALUT AS
NOK 49,000 rev. · NOK −11,000 profit

DALUT AS has 1 registered shareholder:

All shareholders and roles →

Which companies does DALUT AS own?

DALUT AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about DALUT AS

Who owns DALUT AS?

Per Andreas Holm is the largest registered owner, with 100.0%.

What is the revenue of DALUT AS?

DALUT AS had revenue of NOK 49,000 in 2024.

Where is DALUT AS based?

DALUT AS has its business address in Sirma.

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.