BIZTRAC BETA
COMPANY REGISTER PROFILE
957878040 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Repair and maintenance of motor vehicles

VÆRØY AUTO AS

Org. no. 957878040 Limited company (AS) Værøy Incorporated 1990 Active
Ownership graph ↗
Revenue 2025 NOK 1.6m
Operating profit NOK −74,000
Equity NOK 88,000
Incorporated 1990
Share capital NOK 101,000

Signals

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

VÆRØY AUTO AS is registered as a limited company in Værøy, Nordland with organisation number 957878040. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 1990. Registered share capital is NOK 101,000, divided into 101 shares. The company's stated purpose is: “Bil-/mekanisk verksted, samt arbeide som står i tilknytning til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.6m in revenue and NOK −74,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.6m
▲ +10 %
Operating profit
NOK −74,000
▼ −223 %
Equity
NOK 88,000
▼ −44 %
Est. value
NOK 1.1m

Financial health · 2025

Liquidity
0.99
Weak
Current assets ÷ current liabilities
Profitability
-17.6%
Not satisfactory
Return on total assets
Solidity
18.6%
Weak
Equity as a share of total capital

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

Who owns VÆRØY AUTO AS?

VÆRØY AUTO AS has 6 registered shareholders:

All shareholders and roles →

Frequently asked questions about VÆRØY AUTO AS

Who owns VÆRØY AUTO AS?

JAN ARVE REFSVIK is the largest registered owner, with 51.5%.

What is the revenue of VÆRØY AUTO AS?

VÆRØY AUTO AS had revenue of NOK 1.6m in 2025.

Who is the general manager of VÆRØY AUTO AS?

Jan Arve Refsvik is registered as general manager of VÆRØY AUTO AS.

Where is VÆRØY AUTO AS based?

VÆRØY AUTO AS has its business address in Værøy.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.