BIZTRAC BETA
Rental and operating of own or leased real estate

TORNES EIENDOM AS

Org. no. 931670905 Limited company (AS) Ålesund Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 385,000
Operating profit NOK 201,000
Equity NOK 683,000
Incorporated 2023
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.

TORNES EIENDOM AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 931670905. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Kjøp, utvikling, drift, forvaltning og salg av fast eiendom samt det som naturlig står i forhold til dette, herunder også deltakelse i andre selskap med lignende formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 385,000 in revenue and NOK 201,000 in operating profit.

Key figures · 2025

Revenue
NOK 385,000
Operating profit
NOK 201,000
Equity
NOK 683,000
Est. value
NOK 988,000

Financial health · 2025

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

Who owns TORNES EIENDOM AS?

COM EIENDOM AS
TORNES EIENDOM AS
NOK 385,000 rev. · NOK 201,000 profit

TORNES EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TORNES EIENDOM AS

Who owns TORNES EIENDOM AS?

COM EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of TORNES EIENDOM AS?

TORNES EIENDOM AS had revenue of NOK 385,000 in 2025.

Where is TORNES EIENDOM AS based?

TORNES EIENDOM AS has its business address in Ålesund.

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.