BIZTRAC BETA
Computer consultancy and computer facilities management activities

DYNAPRO AS

Org. no. 933183386 Limited company (AS) Asker Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 16.7m
Operating profit NOK 453,000
Equity NOK 548,000
Incorporated 2024
Employees 7
Share capital NOK 32,000

DYNAPRO AS is registered as a limited company in Asker, Akershus with organisation number 933183386. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2024 and has 7 registered employees. Registered share capital is NOK 32,000, divided into 900 shares. The company's stated purpose is: “Å levere tjenester innen IT og andre produkter og tjenester som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignede virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2025 financial year, show NOK 16.7m in revenue and NOK 453,000 in operating profit.

Key figures · 2025

Revenue
NOK 16.7m
Operating profit
NOK 453,000
Equity
NOK 548,000
Est. value
NOK 4.1m

Financial health · 2025

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

Who owns DYNAPRO AS?

HELSKAR AS
DYNAPRO AS
NOK 16.7m rev. · NOK 453,000 profit

DYNAPRO AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about DYNAPRO AS

Who owns DYNAPRO AS?

HELSKAR AS is the largest registered owner, with 33.3%.

What is the revenue of DYNAPRO AS?

DYNAPRO AS had revenue of NOK 16.7m in 2025.

Who is the general manager of DYNAPRO AS?

Geir Støen is registered as general manager of DYNAPRO AS.

Where is DYNAPRO AS based?

DYNAPRO AS has its business address in Asker.

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.