BIZTRAC BETA
Retail sale of motor vehicle parts and accessories

HAVNEN PRO-TUNING AS

Org. no. 931717960 Limited company (AS) Sogndal Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 975,000
Operating profit NOK 330,000
Equity NOK 3.7m
Incorporated 2023
Share capital NOK 30,000

HAVNEN PRO-TUNING AS is registered as a limited company in Sogndal, Vestland with organisation number 931717960. The business is classified under retail sale of motor vehicle parts and accessories (NACE 47.820). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Finansiell holdingsselskap, omfatter morselskap i eller deler av finanskonsern. Handel med deler og utstyr til motorvogn, unntatt motorsykler.”. The most recent filed accounts, for the 2024 financial year, show NOK 975,000 in revenue and NOK 330,000 in operating profit.

Key figures · 2024

Revenue
NOK 975,000
Operating profit
NOK 330,000
Equity
NOK 3.7m
Est. value
NOK 3.0m

Financial health · 2024

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

Who owns HAVNEN PRO-TUNING AS?

ODDGEIR HAVNEN
HAVNEN PRO-TUNING AS
NOK 975,000 rev. · NOK 330,000 profit

HAVNEN PRO-TUNING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HAVNEN PRO-TUNING AS own?

HAVNEN PRO-TUNING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HAVNEN PRO-TUNING AS

Who owns HAVNEN PRO-TUNING AS?

ODDGEIR HAVNEN is the largest registered owner, with 100.0%.

What is the revenue of HAVNEN PRO-TUNING AS?

HAVNEN PRO-TUNING AS had revenue of NOK 975,000 in 2024.

Where is HAVNEN PRO-TUNING AS based?

HAVNEN PRO-TUNING AS has its business address in Kaupanger.

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.