BIZTRAC BETA
Rental and operating of own or leased real estate

HTL EIENDOM AS

Org. no. 966046759 Limited company (AS) Hustadvika Incorporated 1993 Active
Ownership graph ↗
Revenue 2024 NOK 1.8m
Operating profit NOK 647,000
Equity NOK 3.7m
Incorporated 1993
Share capital NOK 300,000

HTL EIENDOM AS is registered as a limited company in Hustadvika, Møre og Romsdal with organisation number 966046759. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1993. Registered share capital is NOK 300,000. The company's stated purpose is: “Drive utleie av fast eiendom samt alt som står i forbindelse med dette, herunder deltakelse i andre selskaper med lignende virksomhet. ”. The most recent filed accounts, for the 2024 financial year, show NOK 1.8m in revenue and NOK 647,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.8m
Operating profit
NOK 647,000
Equity
NOK 3.7m
Est. value
NOK 3.6m

Financial health · 2025

Liquidity
0.34
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
25.9%
Good
Equity as a share of total capital

Who owns HTL EIENDOM AS?

ELLING HENØEN
HTL EIENDOM AS
NOK 1.8m rev. · NOK 647,000 profit

HTL EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HTL EIENDOM AS own?

HTL EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HTL EIENDOM AS

Who owns HTL EIENDOM AS?

ELLING HENØEN is the largest registered owner, with 100.0%.

What is the revenue of HTL EIENDOM AS?

HTL EIENDOM AS had revenue of NOK 1.8m in 2024.

Who is the general manager of HTL EIENDOM AS?

Elling Henøen is registered as general manager of HTL EIENDOM AS.

Where is HTL EIENDOM AS based?

HTL EIENDOM AS has its business address in Elnesvågen.

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.