BIZTRAC BETA
Rental and operating of own or leased real estate

TRYSIL SENTRUMSEIENDOM AS

Org. no. 929682335 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −3,000
Equity NOK 12.5m
Incorporated 2022
Share capital NOK 125,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−3k kr).

TRYSIL SENTRUMSEIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 929682335. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 125,000, divided into 12500 shares. The company's stated purpose is: “Utvikling, forvaltning og investering i andre selskaper, samt investering i fast eiendom og andre formuesgoder og alt som står i forbindelse med de forannevnte virksomheter.”.

Key figures · 2025

Operating profit
NOK −3,000
Equity
NOK 12.5m
Est. value
NOK 10.9m

Financial health · 2025

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

Who owns TRYSIL SENTRUMSEIENDOM AS?

TM SPORT AS
TRYSIL SENTRUMSEIENDOM AS
· NOK −3,000 profit

TRYSIL SENTRUMSEIENDOM AS has 5 registered shareholders:

All shareholders and roles →

Which companies does TRYSIL SENTRUMSEIENDOM AS own?

TRYSIL SENTRUMSEIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TRYSIL SENTRUMSEIENDOM AS

Who owns TRYSIL SENTRUMSEIENDOM AS?

TM SPORT AS is the largest registered owner, with 20.0%.

Who is the general manager of TRYSIL SENTRUMSEIENDOM AS?

Ola Tøraasen is registered as general manager of TRYSIL SENTRUMSEIENDOM AS.

Where is TRYSIL SENTRUMSEIENDOM AS based?

TRYSIL SENTRUMSEIENDOM 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 15.06.2026.

Report a problem

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