BIZTRAC BETA
Rental and operating of own or leased real estate

HØYANGER EIENDOM AS

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

Signals

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

HØYANGER EIENDOM AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 927632403. 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 4.7m, 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 2.0m in revenue and NOK 421,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.0m
Operating profit
NOK 421,000
Equity
NOK 15.6m
Est. value
NOK 12.2m

Financial health · 2025

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

Who owns HØYANGER EIENDOM AS?

COM EIENDOM AS
HØYANGER EIENDOM AS
NOK 2.0m rev. · NOK 421,000 profit

HØYANGER EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HØYANGER EIENDOM AS

Who owns HØYANGER EIENDOM AS?

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

What is the revenue of HØYANGER EIENDOM AS?

HØYANGER EIENDOM AS had revenue of NOK 2.0m in 2025.

Where is HØYANGER EIENDOM AS based?

HØYANGER 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.