BIZTRAC BETA
Rental and operating of own or leased real estate

SVERDRUPSGATE 1 AS

Org. no. 921580215 Limited company (AS) Time Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 3.7m
Operating profit NOK 2.7m
Equity NOK 245,000
Incorporated 2018
Share capital NOK 135,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-03-26 Adresseendring registrert 2026-03-26.

SVERDRUPSGATE 1 AS is registered as a limited company in Time, Rogaland with organisation number 921580215. 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 135,000, divided into 450 shares. The company's stated purpose is: “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 2024 financial year, show NOK 3.7m in revenue and NOK 2.7m in operating profit.

Key figures · 2024

Revenue
NOK 3.7m
Operating profit
NOK 2.7m
Equity
NOK 245,000
Est. value
NOK 4.7m

Financial health · 2024

Liquidity
0.67
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
1.2%
Not satisfactory
Equity as a share of total capital

Who owns SVERDRUPSGATE 1 AS?

DKAR NÆRINGSEIENDOM AS
SVERDRUPSGATE 1 AS
NOK 3.7m rev. · NOK 2.7m profit

SVERDRUPSGATE 1 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SVERDRUPSGATE 1 AS

Who owns SVERDRUPSGATE 1 AS?

DKAR NÆRINGSEIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of SVERDRUPSGATE 1 AS?

SVERDRUPSGATE 1 AS had revenue of NOK 3.7m in 2024.

Where is SVERDRUPSGATE 1 AS based?

SVERDRUPSGATE 1 AS has its business address in Bryne.

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.