BIZTRAC BETA
Rental and operating of own or leased real estate

STORGATA 72 HOLDING AS

Org. no. 920938418 Limited company (AS) Horten Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 874,000
Operating profit NOK 274,000
Equity NOK 977,000
Incorporated 2018
Share capital NOK 100,000

STORGATA 72 HOLDING AS is registered as a limited company in Horten, Vestfold with organisation number 920938418. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2018. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Eiendomsvirksomhet, herunder erverv, utvikling, drift, utleie, kjøp og salg av fast eiendom og annet som hører naturlig sammen med dette. Eie og forvalte aksjer og selskapsandeler i andre selskaper, og annet som hører naturlig sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 874,000 in revenue and NOK 274,000 in operating profit.

Key figures · 2024

Revenue
NOK 874,000
Operating profit
NOK 274,000
Equity
NOK 977,000
Est. value
NOK 1.1m

Financial health · 2024

Liquidity
0.91
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
11.4%
Satisfactory
Equity as a share of total capital

Who owns STORGATA 72 HOLDING AS?

POLARISE PROPERTY AS
STORGATA 72 HOLDING AS
NOK 874,000 rev. · NOK 274,000 profit

STORGATA 72 HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about STORGATA 72 HOLDING AS

Who owns STORGATA 72 HOLDING AS?

POLARISE PROPERTY AS is the largest registered owner, with 50.0%.

What is the revenue of STORGATA 72 HOLDING AS?

STORGATA 72 HOLDING AS had revenue of NOK 874,000 in 2024.

Where is STORGATA 72 HOLDING AS based?

STORGATA 72 HOLDING AS has its business address in Horten.

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.