BIZTRAC BETA
Rental and operating of own or leased real estate

TRIGA EIENDOM AS

Org. no. 983714323 Limited company (AS) Oslo Incorporated 2001 Active
Ownership graph ↗
Revenue 2024 NOK 942,000
Operating profit NOK −2.0m
Equity NOK 79.9m
Incorporated 2001
Share capital NOK 330,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−2,0 mill kr).

TRIGA EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 983714323. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2001. Registered share capital is NOK 330,000, divided into 300 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 2024 financial year, show NOK 942,000 in revenue and NOK −2.0m in operating profit.

Key figures · 2024

Revenue
NOK 942,000
Operating profit
NOK −2.0m
Equity
NOK 79.9m
Est. value
NOK 55.8m

Financial health · 2024

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

Who owns TRIGA EIENDOM AS?

FASTIGHETSUTVECKLING IB 62 AB
TRIGA EIENDOM AS
NOK 942,000 rev. · NOK −2.0m profit

TRIGA EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TRIGA EIENDOM AS own?

TRIGA EIENDOM AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about TRIGA EIENDOM AS

Who owns TRIGA EIENDOM AS?

FASTIGHETSUTVECKLING IB 62 AB is the largest registered owner, with 100.0%.

What is the revenue of TRIGA EIENDOM AS?

TRIGA EIENDOM AS had revenue of NOK 942,000 in 2024.

Where is TRIGA EIENDOM AS based?

TRIGA 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 15.06.2026.

Report a problem

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