BIZTRAC BETA
Manufacture of other parts and accessories for motor vehicles

DYNAMOSERVICE HEGRA AS

Org. no. 990200165 Limited company (AS) Stjørdal Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 482,000
Operating profit NOK 140,000
Equity NOK 718,000
Incorporated 2006
Share capital NOK 30,000

DYNAMOSERVICE HEGRA AS is registered as a limited company in Stjørdal, Trøndelag with organisation number 990200165. The business is classified under manufacture of other parts and accessories for motor vehicles (NACE 29.320). The company was incorporated in 2006. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Reparasjoner og overhaling av startere, dynamoer og andre elektriske artikler, samt alt som hører naturlig til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 482,000 in revenue and NOK 140,000 in operating profit.

Key figures · 2025

Revenue
NOK 482,000
Operating profit
NOK 140,000
Equity
NOK 718,000
Est. value
NOK 910,000

Financial health · 2024

Liquidity
5.97
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
83.2%
Very good
Equity as a share of total capital

Who owns DYNAMOSERVICE HEGRA AS?

TERJE VIK
DYNAMOSERVICE HEGRA AS
NOK 482,000 rev. · NOK 140,000 profit

DYNAMOSERVICE HEGRA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DYNAMOSERVICE HEGRA AS

Who owns DYNAMOSERVICE HEGRA AS?

TERJE VIK is the largest registered owner, with 100.0%.

What is the revenue of DYNAMOSERVICE HEGRA AS?

DYNAMOSERVICE HEGRA AS had revenue of NOK 482,000 in 2025.

Who is the general manager of DYNAMOSERVICE HEGRA AS?

Terje Vik is registered as general manager of DYNAMOSERVICE HEGRA AS.

Where is DYNAMOSERVICE HEGRA AS based?

DYNAMOSERVICE HEGRA AS has its business address in Hegra.

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.