BIZTRAC BETA
Business and other management consultancy activities

DINGJELD AS

Org. no. 998582911 Limited company (AS) Bærum Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −35,000
Equity NOK −404,000
Incorporated 2012
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−404k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−35k kr).

DINGJELD AS is registered as a limited company in Bærum, Akershus with organisation number 998582911. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Bedriftsrådgivning og annen administrativ rådgivning, investering og deltakelse i andre virksomheter som korresponderer med selskapets virksomhet, samt annet som naturlig faller inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −35,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −35,000
Equity
NOK −404,000

Financial health · 2024

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

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

Who owns DINGJELD AS?

NORDIC INNOVATION LTD
DINGJELD AS
NOK 0 rev. · NOK −35,000 profit

DINGJELD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DINGJELD AS

Who owns DINGJELD AS?

NORDIC INNOVATION LTD is the largest registered owner, with 100.0%.

What is the revenue of DINGJELD AS?

DINGJELD AS had revenue of NOK 0 in 2025.

Where is DINGJELD AS based?

DINGJELD AS has its business address in Høvik.

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.