biztrac. BETA
COMPANY REGISTER PROFILE
850724482 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Retail sale of motor vehicles

ROVIK AUTO AS

Org. no. 850724482 Limited company (AS) Gjesdal Incorporated 1989 Active
Ownership graph ↗
Revenue 2025 NOK 236,000
Operating profit NOK −111,000
Equity NOK 5.3m
Incorporated 1989
Share capital NOK 400,000

Signals

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

ROVIK AUTO AS is registered as a limited company in Gjesdal, Rogaland with organisation number 850724482. The business is classified under retail sale of motor vehicles (NACE 47.810). The company was incorporated in 1989. Registered share capital is NOK 400,000. The company's stated purpose is: “Verkstedsdrift og handel samt deltakelse i annen virksomhet ved kjøp av andeler aksjer eller på annen måte.”. The most recent filed accounts, for the 2025 financial year, show NOK 236,000 in revenue and NOK −111,000 in operating profit.

Key figures · 2025

Revenue
NOK 236,000
▲ +0 %
Operating profit
NOK −111,000
▼ −72 %
Equity
NOK 5.3m
▼ −4 %
Est. value
NOK 6.7m

Financial health · 2025

Liquidity
2.29
Very good
Current assets ÷ current liabilities
Profitability
-0.8%
Not satisfactory
Return on total assets
Solidity
61.9%
Very good
Equity as a share of total capital

Who owns ROVIK AUTO AS?

ROVIK AUTO AS
NOK 236,000 rev. · NOK −111,000 profit

ROVIK AUTO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ROVIK AUTO AS

Who owns ROVIK AUTO AS?

Haavar Rovik is the largest registered owner, with 100.0%.

What is the revenue of ROVIK AUTO AS?

ROVIK AUTO AS had revenue of NOK 236,000 in 2025.

Who is the general manager of ROVIK AUTO AS?

Haavar Rovik is registered as general manager of ROVIK AUTO AS.

Where is ROVIK AUTO AS based?

ROVIK AUTO AS has its business address in Ålgård.

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

Report a problem

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