BIZTRAC BETA
Rental and operating of own or leased real estate

STRANDGATA 106-108 EIENDOM AS

Org. no. 991078630 Limited company (AS) Bergen Incorporated 2007 Active
Ownership graph ↗
Revenue 2025 NOK 10.0m
Operating profit NOK 3.7m
Equity NOK 54.5m
Incorporated 2007
Share capital NOK 20.7m

Signals

1 flags
  • Nylig endring 2026-06-03 Adresseendring registrert 2026-06-03.

STRANDGATA 106-108 EIENDOM AS is registered as a limited company in Bergen, Vestland with organisation number 991078630. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2007. Registered share capital is NOK 20.7m, divided into 20700 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 2025 financial year, show NOK 10.0m in revenue and NOK 3.7m in operating profit.

Key figures · 2025

Revenue
NOK 10.0m
Operating profit
NOK 3.7m
Equity
NOK 54.5m
Est. value
NOK 45.0m

Financial health · 2025

Liquidity
2.96
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
60.8%
Very good
Equity as a share of total capital

Who owns STRANDGATA 106-108 EIENDOM AS?

SIVA EIENDOM HOLDING AS
STRANDGATA 106-108 EIENDOM AS
NOK 10.0m rev. · NOK 3.7m profit

STRANDGATA 106-108 EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STRANDGATA 106-108 EIENDOM AS

Who owns STRANDGATA 106-108 EIENDOM AS?

SIVA EIENDOM HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of STRANDGATA 106-108 EIENDOM AS?

STRANDGATA 106-108 EIENDOM AS had revenue of NOK 10.0m in 2025.

Where is STRANDGATA 106-108 EIENDOM AS based?

STRANDGATA 106-108 EIENDOM AS has its business address in Bergen.

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.