BIZTRAC BETA
Rental and operating of own or leased real estate

R.V. SANDVIKEN AS

Org. no. 963496532 Limited company (AS) Lom Incorporated 1992 Active
Ownership graph ↗
Revenue 2025 NOK 72,000
Operating profit NOK −472,000
Equity NOK 16.1m
Incorporated 1992
Share capital NOK 100,000

Signals

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

R.V. SANDVIKEN AS is registered as a limited company in Lom, Innlandet with organisation number 963496532. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1992. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Å eie aksjer og verdipapirer i andre selskaper, samt forvalte avkastningen av disse investeringene.”. The most recent filed accounts, for the 2025 financial year, show NOK 72,000 in revenue and NOK −472,000 in operating profit.

Key figures · 2025

Revenue
NOK 72,000
Operating profit
NOK −472,000
Equity
NOK 16.1m
Est. value
NOK 11.1m

Financial health · 2025

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

Who owns R.V. SANDVIKEN AS?

ROLF VEGARD SANDVIKEN
R.V. SANDVIKEN AS
NOK 72,000 rev. · NOK −472,000 profit

R.V. SANDVIKEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about R.V. SANDVIKEN AS

Who owns R.V. SANDVIKEN AS?

ROLF VEGARD SANDVIKEN is the largest registered owner, with 100.0%.

What is the revenue of R.V. SANDVIKEN AS?

R.V. SANDVIKEN AS had revenue of NOK 72,000 in 2025.

Who is the general manager of R.V. SANDVIKEN AS?

Rolf Vegard Sandviken is registered as general manager of R.V. SANDVIKEN AS.

Where is R.V. SANDVIKEN AS based?

R.V. SANDVIKEN AS has its business address in Lom.

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.