BIZTRAC BETA
Rental and operating of own or leased real estate

TRE SØSTRE EIENDOM 1 AS

Org. no. 997485963 Limited company (AS) Oslo Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 4.1m
Operating profit NOK 3.1m
Equity NOK 11.7m
Incorporated 2011
Share capital NOK 7.5m

Signals

1 flags
  • Nylig endring 2026-03-23 Adresseendring registrert 2026-03-23.

TRE SØSTRE EIENDOM 1 AS is registered as a limited company in Oslo, Oslo with organisation number 997485963. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2011. Registered share capital is NOK 7.5m, divided into 1000 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 2025 financial year, show NOK 4.1m in revenue and NOK 3.1m in operating profit.

Key figures · 2025

Revenue
NOK 4.1m
Operating profit
NOK 3.1m
Equity
NOK 11.7m
Est. value
NOK 12.9m

Financial health · 2025

Liquidity
0.64
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
26.8%
Good
Equity as a share of total capital

Who owns TRE SØSTRE EIENDOM 1 AS?

NORSK AREAL AS
TRE SØSTRE EIENDOM 1 AS
NOK 4.1m rev. · NOK 3.1m profit

TRE SØSTRE EIENDOM 1 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TRE SØSTRE EIENDOM 1 AS

Who owns TRE SØSTRE EIENDOM 1 AS?

NORSK AREAL AS is the largest registered owner, with 100.0%.

What is the revenue of TRE SØSTRE EIENDOM 1 AS?

TRE SØSTRE EIENDOM 1 AS had revenue of NOK 4.1m in 2025.

Who is the general manager of TRE SØSTRE EIENDOM 1 AS?

Aage Hagen is registered as general manager of TRE SØSTRE EIENDOM 1 AS.

Where is TRE SØSTRE EIENDOM 1 AS based?

TRE SØSTRE EIENDOM 1 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.