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

TRIANGELGÅRDEN OFFENTLIG EIENDOM AS

Org. no. 924445777 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −476,000
Equity NOK 70.6m
Incorporated 2020
Share capital NOK 1.1m

Signals

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

TRIANGELGÅRDEN OFFENTLIG EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 924445777. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2020. Registered share capital is NOK 1.1m, divided into 1150000 shares. The company's stated purpose is: “Investere i, utvikle og drive fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”.

Former names: WR START UP 328 AS

Key figures · 2025

Operating profit
NOK −476,000
▼ −3 %
Equity
NOK 70.6m
▼ −6 %
Est. value
NOK 64.4m

Financial health · 2025

Liquidity
11.90
Very good
Current assets ÷ current liabilities
Profitability
2.3%
Weak
Return on total assets
Solidity
22.5%
Good
Equity as a share of total capital

Who owns TRIANGELGÅRDEN OFFENTLIG EIENDOM AS?

TRIANGELGÅRDEN OFFENTLIG EIENDOM AS has 20+ registered shareholders:

All shareholders and roles →

Which companies does TRIANGELGÅRDEN OFFENTLIG EIENDOM AS own?

TRIANGELGÅRDEN OFFENTLIG EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TRIANGELGÅRDEN OFFENTLIG EIENDOM AS

Who owns TRIANGELGÅRDEN OFFENTLIG EIENDOM AS?

FINANSHUSET HAMAR AS is the largest registered owner, with 25.0%.

Where is TRIANGELGÅRDEN OFFENTLIG EIENDOM AS based?

TRIANGELGÅRDEN OFFENTLIG EIENDOM 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.