BIZTRAC BETA
Rental and operating of own or leased real estate

SANDVIKSVEIEN 36 AS

Org. no. 929245652 Limited company (AS) Bærum Incorporated 1979 Active
Ownership graph ↗
Revenue 2024 NOK 3.2m
Operating profit NOK 1.9m
Equity NOK 5.6m
Incorporated 1979
Share capital NOK 612,000

SANDVIKSVEIEN 36 AS is registered as a limited company in Bærum, Akershus with organisation number 929245652. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1979. Registered share capital is NOK 612,000, divided into 120 shares. The company's stated purpose is: “Utbygge og eie fast eiendom, å drive handel og skipsfart samt hva som herved står iforbindelse, herunder å engasjere seg i andre selskaper med samme eller lignende formål ved aksjeeie eller på annen måte.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.2m in revenue and NOK 1.9m in operating profit.

Key figures · 2024

Revenue
NOK 3.2m
Operating profit
NOK 1.9m
Equity
NOK 5.6m
Est. value
NOK 6.7m

Financial health · 2024

Liquidity
0.34
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
15.2%
Satisfactory
Equity as a share of total capital

Who owns SANDVIKSVEIEN 36 AS?

BØLE VEKST AS
SANDVIKSVEIEN 36 AS
NOK 3.2m rev. · NOK 1.9m profit

SANDVIKSVEIEN 36 AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SANDVIKSVEIEN 36 AS

Who owns SANDVIKSVEIEN 36 AS?

BØLE VEKST AS is the largest registered owner, with 90.0%.

What is the revenue of SANDVIKSVEIEN 36 AS?

SANDVIKSVEIEN 36 AS had revenue of NOK 3.2m in 2024.

Who is the general manager of SANDVIKSVEIEN 36 AS?

Eirik Bøle is registered as general manager of SANDVIKSVEIEN 36 AS.

Where is SANDVIKSVEIEN 36 AS based?

SANDVIKSVEIEN 36 AS has its business address in Fornebu.

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.