BIZTRAC BETA
COMPANY REGISTER PROFILE
918187456 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Development of building projects

NORDRYGGEN AS

Org. no. 918187456 Limited company (AS) Vinje Incorporated 2016 Active
Ownership graph ↗
Operating profit NOK −97,000
Equity NOK −3.2m
Incorporated 2016
Share capital NOK 120,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−3,2 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−97k kr).

NORDRYGGEN AS is registered as a limited company in Vinje, Telemark with organisation number 918187456. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2016. Registered share capital is NOK 120,000, divided into 150 shares. The company's stated purpose is: “Å eie, utvikling, drift og utleie av fast eiendom, entreprenør innen bygg og anlegg,transport og kranarbeid, samt annen virksomhet som står i naturlig tilknytning til dette, herunder å delta i andre selskaper med lignende virksomhet.”.

Former names: DYRDAL EIENDOM AS

Key figures · 2025

Operating profit
NOK −97,000
▼ −8787 %
Equity
NOK −3.2m
▲ +6 %

Financial health · 2025

Liquidity
0.14
Not satisfactory
Current assets ÷ current liabilities
Profitability
-5.4%
Not satisfactory
Return on total assets
Solidity
-165.2%
Weak
Equity as a share of total capital

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

Who owns NORDRYGGEN AS?

NORDRYGGEN AS
· NOK −97,000 profit

NORDRYGGEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NORDRYGGEN AS

Who owns NORDRYGGEN AS?

DYRDAL AS is the largest registered owner, with 100.0%.

Who is the general manager of NORDRYGGEN AS?

Asbjørn Dyrdal is registered as general manager of NORDRYGGEN AS.

Where is NORDRYGGEN AS based?

NORDRYGGEN AS has its business address in Vinje.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

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