biztrac. BETA
COMPANY REGISTER PROFILE
924588772 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

TROSVIKSTRANDA HOLDING AS

Org. no. 924588772 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Operating profit NOK −643,000
Equity NOK 20.5m
Incorporated 2019
Share capital NOK 160,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−643k kr).
  • Nylig endring 2026-07-10 Aksjekapital registrert 2026-07-10.

TROSVIKSTRANDA HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 924588772. 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 160,000, divided into 1000 shares. The company's stated purpose is: “Investering i eiendom, aksjer og andre eierandeler i andre selskaper og foretak samt all annen virksomhet som hermed står i forbindelse.”.

Former names: EIENDOMSSELSKAPET 57 AS

Key figures · 2025

Operating profit
NOK −643,000
▲ +96 %
Equity
NOK 20.5m
▼ −21 %
Est. value
NOK 18.7m

Financial health · 2025

Liquidity
4.80
Very good
Current assets ÷ current liabilities
Profitability
1.6%
Weak
Return on total assets
Solidity
29.0%
Good
Equity as a share of total capital

Who owns TROSVIKSTRANDA HOLDING AS?

TROSVIKSTRANDA HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does TROSVIKSTRANDA HOLDING AS own?

TROSVIKSTRANDA HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about TROSVIKSTRANDA HOLDING AS

Who owns TROSVIKSTRANDA HOLDING AS?

STOR-OSLO EIENDOM HOLDING AS is the largest registered owner, with 50.0%.

Where is TROSVIKSTRANDA HOLDING AS based?

TROSVIKSTRANDA HOLDING AS has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.