biztrac. BETA
COMPANY REGISTER PROFILE
936522238 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Buying and selling of own real estate

HLS EIENDOM AS

Org. no. 936522238 Limited company (AS) Haugesund Incorporated 2025 Active
Revenue 2025 NOK 0
Operating profit NOK −2,000
Equity NOK 28,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−2k kr).

HLS EIENDOM AS is registered as a limited company in Haugesund, Rogaland with organisation number 936522238. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Erverve, eie, utvikle, forvalte, leie ut og selge bolig- og næringseiendom, samt yte eiendomsrelaterte tjenester, samt virksomhet som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −2,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −2,000
Equity
NOK 28,000
▲ +1 %
Est. value
NOK 26,000

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
100.0%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns HLS EIENDOM AS?

HLS EIENDOM AS
NOK 0 rev. · NOK −2,000 profit

HLS EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HLS EIENDOM AS

Who owns HLS EIENDOM AS?

STAVA HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of HLS EIENDOM AS?

HLS EIENDOM AS had revenue of NOK 0 in 2025.

Where is HLS EIENDOM AS based?

HLS EIENDOM AS has its business address in Haugesund.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.