BIZTRAC BETA
Rental and operating of own or leased real estate

RØHNEGÅRDEN SANDVIKA AS

Org. no. 934694325 Limited company (AS) Bærum Incorporated 1983 Active
Ownership graph ↗
Revenue 2025 NOK 2.8m
Operating profit NOK 2.0m
Equity NOK 16.2m
Incorporated 1983
Share capital NOK 100,000

RØHNEGÅRDEN SANDVIKA AS is registered as a limited company in Bærum, Akershus with organisation number 934694325. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1983. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Eie og drive fast eiendom samt alt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.8m in revenue and NOK 2.0m in operating profit.

Key figures · 2025

Revenue
NOK 2.8m
Operating profit
NOK 2.0m
Equity
NOK 16.2m
Est. value
NOK 16.1m

Financial health · 2025

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

Who owns RØHNEGÅRDEN SANDVIKA AS?

FINSTADS AUTOCO AS
RØHNEGÅRDEN SANDVIKA AS
NOK 2.8m rev. · NOK 2.0m profit

RØHNEGÅRDEN SANDVIKA AS has 1 registered shareholder:

All shareholders and roles →

Group structure

RØHNEGÅRDEN SANDVIKA AS er morselskap for 9 datterselskaper:

Frequently asked questions about RØHNEGÅRDEN SANDVIKA AS

Who owns RØHNEGÅRDEN SANDVIKA AS?

FINSTADS AUTOCO AS is the largest registered owner, with 100.0%.

What is the revenue of RØHNEGÅRDEN SANDVIKA AS?

RØHNEGÅRDEN SANDVIKA AS had revenue of NOK 2.8m in 2025.

Who is the general manager of RØHNEGÅRDEN SANDVIKA AS?

Per Gunnar Tron is registered as general manager of RØHNEGÅRDEN SANDVIKA AS.

Where is RØHNEGÅRDEN SANDVIKA AS based?

RØHNEGÅRDEN SANDVIKA AS has its business address in Sandvika.

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.