BIZTRAC BETA
Rental and operating of own or leased real estate

SØREGATEN 22 AS

Org. no. 926096753 Limited company (AS) Stavanger Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 2.1m
Operating profit NOK −666,000
Equity NOK 7.2m
Incorporated 2020
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−666k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

SØREGATEN 22 AS is registered as a limited company in Stavanger, Rogaland with organisation number 926096753. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Eie og investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.1m in revenue and NOK −666,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.1m
Operating profit
NOK −666,000
Equity
NOK 7.2m
Est. value
NOK 6.6m

Financial health · 2025

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

Who owns SØREGATEN 22 AS?

RETAIL OFFICE STAVANGER AS
SØREGATEN 22 AS
NOK 2.1m rev. · NOK −666,000 profit

SØREGATEN 22 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SØREGATEN 22 AS

Who owns SØREGATEN 22 AS?

RETAIL OFFICE STAVANGER AS is the largest registered owner, with 100.0%.

What is the revenue of SØREGATEN 22 AS?

SØREGATEN 22 AS had revenue of NOK 2.1m in 2025.

Where is SØREGATEN 22 AS based?

SØREGATEN 22 AS has its business address in Stavanger.

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.