BIZTRAC BETA
Rental and operating of own or leased real estate

STORGATA 31 SON AS

Org. no. 929719379 Limited company (AS) Vestby Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 3.8m
Operating profit NOK 3.0m
Equity NOK 1.6m
Incorporated 2022
Share capital NOK 200,000

Signals

2 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-06-08 Adresseendring registrert 2026-06-08.

STORGATA 31 SON AS is registered as a limited company in Vestby, Akershus with organisation number 929719379. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 200,000, divided into 100 shares. The company's stated purpose is: “Omsetning og drift av fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.8m in revenue and NOK 3.0m in operating profit.

Key figures · 2024

Revenue
NOK 3.8m
Operating profit
NOK 3.0m
Equity
NOK 1.6m
Est. value
NOK 6.6m

Financial health · 2025

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

Who owns STORGATA 31 SON AS?

LANDLORD EIENDOM AS
STORGATA 31 SON AS
NOK 3.8m rev. · NOK 3.0m profit

STORGATA 31 SON AS has 1 registered shareholder:

All shareholders and roles →

Group structure

STORGATA 31 SON AS er morselskap for 12 datterselskaper:

Frequently asked questions about STORGATA 31 SON AS

Who owns STORGATA 31 SON AS?

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

What is the revenue of STORGATA 31 SON AS?

STORGATA 31 SON AS had revenue of NOK 3.8m in 2024.

Where is STORGATA 31 SON AS based?

STORGATA 31 SON AS has its business address in Vestby.

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.