BIZTRAC BETA
Rental and operating of own or leased real estate

STORGATA 6 LILLESTRØM AS

Org. no. 911714027 Limited company (AS) Oslo Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 9.1m
Operating profit NOK 2.4m
Equity NOK 106.0m
Incorporated 2013
Share capital NOK 100,000

STORGATA 6 LILLESTRØM AS is registered as a limited company in Oslo, Oslo with organisation number 911714027. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2013. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drift og utvikling og utleie av fast eiendom og all annen tilknyttet og beslektet økonomisk virksomhet, samt deltakelse i andre virksomheter og selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 9.1m in revenue and NOK 2.4m in operating profit.

Key figures · 2024

Revenue
NOK 9.1m
Operating profit
NOK 2.4m
Equity
NOK 106.0m
Est. value
NOK 77.0m

Financial health · 2024

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

Who owns STORGATA 6 LILLESTRØM AS?

ASTORIA AS
STORGATA 6 LILLESTRØM AS
NOK 9.1m rev. · NOK 2.4m profit

STORGATA 6 LILLESTRØM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STORGATA 6 LILLESTRØM AS

Who owns STORGATA 6 LILLESTRØM AS?

ASTORIA AS is the largest registered owner, with 100.0%.

What is the revenue of STORGATA 6 LILLESTRØM AS?

STORGATA 6 LILLESTRØM AS had revenue of NOK 9.1m in 2024.

Who is the general manager of STORGATA 6 LILLESTRØM AS?

Lars Kristian Vehus is registered as general manager of STORGATA 6 LILLESTRØM AS.

Where is STORGATA 6 LILLESTRØM AS based?

STORGATA 6 LILLESTRØM AS has its business address in Oslo.

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.