biztrac. BETA
COMPANY REGISTER PROFILE
996311627 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Electrical installation

DYRANUT AS

Org. no. 996311627 Limited company (AS) Vinje Incorporated 2010 Active
Revenue 2025 NOK 420,000
Operating profit NOK 28,000
Equity NOK 769.9m
Incorporated 2010
Share capital NOK 2.5m

DYRANUT AS is registered as a limited company in Vinje, Telemark with organisation number 996311627. The business is classified under electrical installation (NACE 43.210). The company was incorporated in 2010. Registered share capital is NOK 2.5m, divided into 1 shares. The company's stated purpose is: “Eie og forvaltning av selskaper, aksjer og eiendommer og alt som naturlig hører inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 420,000 in revenue and NOK 28,000 in operating profit.

Former names: NLI UTVIKLING I AS

Key figures · 2025

Revenue
NOK 420,000
▼ −30 %
Operating profit
NOK 28,000
▼ −22 %
Equity
NOK 769.9m
▲ +1 %
Est. value
NOK 353.9m

Financial health · 2025

Liquidity
2398.34
Very good
Current assets ÷ current liabilities
Profitability
1.1%
Weak
Return on total assets
Solidity
99.1%
Very good
Equity as a share of total capital

Who owns DYRANUT AS?

DYRANUT AS
NOK 420,000 rev. · NOK 28,000 profit

DYRANUT AS has 1 registered shareholder:

All shareholders and roles →

Which companies does DYRANUT AS own?

DYRANUT AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about DYRANUT AS

Who owns DYRANUT AS?

Børre Loe Nordheim-Larsen is the largest registered owner, with 100.0%.

What is the revenue of DYRANUT AS?

DYRANUT AS had revenue of NOK 420,000 in 2025.

Who is the general manager of DYRANUT AS?

Børre Loe Nordheim-Larsen is registered as general manager of DYRANUT AS.

Where is DYRANUT AS based?

DYRANUT 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 03.10.2026.

Report a problem

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