BIZTRAC BETA
Beverage serving activities

DYRNESVAAGEN INNOVASJON AS

Org. no. 917151156 Limited company (AS) Smøla Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 1.3m
Operating profit NOK 101,000
Equity NOK 87,000
Incorporated 2016
Employees 9
Share capital NOK 60,000

DYRNESVAAGEN INNOVASJON AS is registered as a limited company in Smøla, Møre og Romsdal with organisation number 917151156. The business is classified under beverage serving activities (NACE 56.300). The company was incorporated in 2016 and has 9 registered employees. Registered share capital is NOK 60,000, divided into 60 shares. The company's stated purpose is: “Kjøp/salg/utleie av musikkutstyr, drift/vedlikehold av teknisk/mekanisk utstyr, utvikling/drift av eiendom og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.3m in revenue and NOK 101,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.3m
Operating profit
NOK 101,000
Equity
NOK 87,000
Est. value
NOK 420,000

Financial health · 2024

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

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

Who owns DYRNESVAAGEN INNOVASJON AS?

MARIT NEERLAND HOPSHAUG
DYRNESVAAGEN INNOVASJON AS
NOK 1.3m rev. · NOK 101,000 profit

DYRNESVAAGEN INNOVASJON AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about DYRNESVAAGEN INNOVASJON AS

Who owns DYRNESVAAGEN INNOVASJON AS?

MARIT NEERLAND HOPSHAUG is the largest registered owner, with 25.0%.

What is the revenue of DYRNESVAAGEN INNOVASJON AS?

DYRNESVAAGEN INNOVASJON AS had revenue of NOK 1.3m in 2024.

Where is DYRNESVAAGEN INNOVASJON AS based?

DYRNESVAAGEN INNOVASJON AS has its business address in Smøla.

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.