BIZTRAC BETA
Rental and operating of own or leased real estate

TORNEROSE EIENDOM AS

Org. no. 990726914 Limited company (AS) Bergen Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 2.2m
Operating profit NOK 367,000
Equity NOK 5.2m
Incorporated 2006
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

TORNEROSE EIENDOM AS is registered as a limited company in Bergen, Vestland with organisation number 990726914. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2006. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Erverve og eie næringseiendommer, drive eiendomsutvikling og dertil hørende næringsvirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.2m in revenue and NOK 367,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.2m
Operating profit
NOK 367,000
Equity
NOK 5.2m
Est. value
NOK 4.1m

Financial health · 2024

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

Who owns TORNEROSE EIENDOM AS?

MTB EIENDOMSUTVIKLING AS
TORNEROSE EIENDOM AS
NOK 2.2m rev. · NOK 367,000 profit

TORNEROSE EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Group structure

TORNEROSE EIENDOM AS er morselskap for 20 datterselskaper:

Frequently asked questions about TORNEROSE EIENDOM AS

Who owns TORNEROSE EIENDOM AS?

MTB EIENDOMSUTVIKLING AS is the largest registered owner, with 100.0%.

What is the revenue of TORNEROSE EIENDOM AS?

TORNEROSE EIENDOM AS had revenue of NOK 2.2m in 2024.

Where is TORNEROSE EIENDOM AS based?

TORNEROSE EIENDOM AS has its business address in Bergen.

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.