biztrac. BETA
COMPANY REGISTER PROFILE
888309942 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

STOREBRAND VOGELLUND 35 AS

Org. no. 888309942 Limited company (AS) Bærum Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 9.6m
Operating profit NOK 8.6m
Equity NOK 169.3m
Incorporated 2005
Share capital NOK 1.7m

STOREBRAND VOGELLUND 35 AS is registered as a limited company in Bærum, Akershus with organisation number 888309942. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 1.7m, divided into 1 shares. The company's stated purpose is: “Eie og forvalte eiendommen, og hva hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 9.6m in revenue and NOK 8.6m in operating profit.

Former names: BILGRUPPEN EIENDOM AS, STOREBRAND HOLMEN UTVIKLING AS

Key figures · 2025

Revenue
NOK 9.6m
▼ −1 %
Operating profit
NOK 8.6m
▼ −67 %
Equity
NOK 169.3m
▲ +1 %
Est. value
NOK 141.5m

Financial health · 2025

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

Who owns STOREBRAND VOGELLUND 35 AS?

STOREBRAND VOGELLUND 35 AS
NOK 9.6m rev. · NOK 8.6m profit

STOREBRAND VOGELLUND 35 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STOREBRAND VOGELLUND 35 AS

Who owns STOREBRAND VOGELLUND 35 AS?

STOREBRAND EIENDOM VEKST AS is the largest registered owner, with 100.0%.

What is the revenue of STOREBRAND VOGELLUND 35 AS?

STOREBRAND VOGELLUND 35 AS had revenue of NOK 9.6m in 2025.

Where is STOREBRAND VOGELLUND 35 AS based?

STOREBRAND VOGELLUND 35 AS has its business address in Lysaker.

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.