BIZTRAC BETA
Rental and operating of own or leased real estate

STORGATA-22 AS

Org. no. 922303088 Limited company (AS) Horten Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 214,000
Operating profit NOK 165,000
Equity NOK 463,000
Incorporated 2018
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

STORGATA-22 AS is registered as a limited company in Horten, Vestfold with organisation number 922303088. 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 30,000, divided into 1000 shares. The company's stated purpose is: “Å være et investeringsselskap, herunder investeringer i aksjer, andeler i selskap etter selskapsloven og utenlandske selskaper, obligasjoner, fast eiendom, og annet som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 214,000 in revenue and NOK 165,000 in operating profit.

Key figures · 2024

Revenue
NOK 214,000
Operating profit
NOK 165,000
Equity
NOK 463,000
Est. value
NOK 619,000

Financial health · 2024

Liquidity
0.70
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
30.1%
Good
Equity as a share of total capital

Who owns STORGATA-22 AS?

POLARISE PROPERTY AS
STORGATA-22 AS
NOK 214,000 rev. · NOK 165,000 profit

STORGATA-22 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STORGATA-22 AS

Who owns STORGATA-22 AS?

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

What is the revenue of STORGATA-22 AS?

STORGATA-22 AS had revenue of NOK 214,000 in 2024.

Where is STORGATA-22 AS based?

STORGATA-22 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.