BIZTRAC BETA
Machining of metals

VARGHAUGEN MOTOR AS

Org. no. 929274660 Limited company (AS) Bodø Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK −154,000
Equity NOK 94,000
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−154k kr).

VARGHAUGEN MOTOR AS is registered as a limited company in Bodø, Nordland with organisation number 929274660. The business is classified under machining of metals (NACE 25.530). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Masseforflytning, salg av varer og tjenester, transport og håndverkstjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK −154,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
Operating profit
NOK −154,000
Equity
NOK 94,000
Est. value
NOK 632,000

Financial health · 2025

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

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

Who owns VARGHAUGEN MOTOR AS?

VARGHAUGEN HOLDING AS
VARGHAUGEN MOTOR AS
NOK 1.1m rev. · NOK −154,000 profit

VARGHAUGEN MOTOR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VARGHAUGEN MOTOR AS

Who owns VARGHAUGEN MOTOR AS?

VARGHAUGEN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of VARGHAUGEN MOTOR AS?

VARGHAUGEN MOTOR AS had revenue of NOK 1.1m in 2025.

Who is the general manager of VARGHAUGEN MOTOR AS?

Jürgen Ivar Larsen is registered as general manager of VARGHAUGEN MOTOR AS.

Where is VARGHAUGEN MOTOR AS based?

VARGHAUGEN MOTOR AS has its business address in Bodø.

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.