BIZTRAC BETA
Rental and operating of own or leased real estate

RØRTEK EIENDOM AS

Org. no. 927084945 Limited company (AS) Ålesund Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 2.0m
Operating profit NOK 725,000
Equity NOK 9.5m
Incorporated 2021
Share capital NOK 9.5m

Signals

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

RØRTEK EIENDOM AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 927084945. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2021. Registered share capital is NOK 9.5m, divided into 1000 shares. The company's stated purpose is: “Eie og forvalte eiendom, samt eie selskaper innenfor samme bransje.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.0m in revenue and NOK 725,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.0m
Operating profit
NOK 725,000
Equity
NOK 9.5m
Est. value
NOK 7.4m

Financial health · 2024

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

Who owns RØRTEK EIENDOM AS?

RØRTEK AS
RØRTEK EIENDOM AS
NOK 2.0m rev. · NOK 725,000 profit

RØRTEK EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RØRTEK EIENDOM AS

Who owns RØRTEK EIENDOM AS?

RØRTEK AS is the largest registered owner, with 100.0%.

What is the revenue of RØRTEK EIENDOM AS?

RØRTEK EIENDOM AS had revenue of NOK 2.0m in 2025.

Who is the general manager of RØRTEK EIENDOM AS?

Jan Magnus Rønes Håhjem is registered as general manager of RØRTEK EIENDOM AS.

Where is RØRTEK EIENDOM AS based?

RØRTEK 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.