BIZTRAC BETA
Rental and operating of own or leased real estate

TRYVANNSTÅRNET AS

Org. no. 930332658 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −28,000
Equity NOK 123.2m
Incorporated 2022
Share capital NOK 201,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−28k kr).

TRYVANNSTÅRNET AS is registered as a limited company in Oslo, Oslo with organisation number 930332658. 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 201,000, divided into 706 shares. The company's stated purpose is: “Investere i fast eiendom eller selskaper som eier fast eiendom, eie og leie ut fast eiendom; samt alt hva herved står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −28,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −28,000
Equity
NOK 123.2m
Est. value
NOK 130.4m

Financial health · 2024

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

Who owns TRYVANNSTÅRNET AS?

EIENDOMSSPAR AS
TRYVANNSTÅRNET AS
NOK 0 rev. · NOK −28,000 profit

TRYVANNSTÅRNET AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TRYVANNSTÅRNET AS

Who owns TRYVANNSTÅRNET AS?

EIENDOMSSPAR AS is the largest registered owner, with 100.0%.

What is the revenue of TRYVANNSTÅRNET AS?

TRYVANNSTÅRNET AS had revenue of NOK 0 in 2024.

Who is the general manager of TRYVANNSTÅRNET AS?

Børre Vegard Skjolden is registered as general manager of TRYVANNSTÅRNET AS.

Where is TRYVANNSTÅRNET AS based?

TRYVANNSTÅRNET 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.