BIZTRAC BETA
Rental and operating of own or leased real estate

SØLVBERGET EIENDOM AS

Org. no. 923929452 Limited company (AS) Stavanger Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 8.2m
Operating profit NOK 2.2m
Equity NOK 11.9m
Incorporated 2019
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.

SØLVBERGET EIENDOM AS is registered as a limited company in Stavanger, Rogaland with organisation number 923929452. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30000 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 8.2m in revenue and NOK 2.2m in operating profit.

Key figures · 2025

Revenue
NOK 8.2m
Operating profit
NOK 2.2m
Equity
NOK 11.9m
Est. value
NOK 11.9m

Financial health · 2025

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

Who owns SØLVBERGET EIENDOM AS?

RETAIL OFFICE STAVANGER AS
SØLVBERGET EIENDOM AS
NOK 8.2m rev. · NOK 2.2m profit

SØLVBERGET EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SØLVBERGET EIENDOM AS

Who owns SØLVBERGET EIENDOM AS?

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

What is the revenue of SØLVBERGET EIENDOM AS?

SØLVBERGET EIENDOM AS had revenue of NOK 8.2m in 2025.

Where is SØLVBERGET EIENDOM AS based?

SØLVBERGET EIENDOM 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.