BIZTRAC BETA
Water collection, treatment and supply

LI HYTTEKOMFORT AS

Org. no. 998333237 Limited company (AS) Stavanger Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 434,000
Operating profit NOK −125,000
Equity NOK 4.3m
Incorporated 2012
Share capital NOK 7.7m

Signals

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

LI HYTTEKOMFORT AS is registered as a limited company in Stavanger, Rogaland with organisation number 998333237. The business is classified under water collection, treatment and supply (NACE 36.000). The company was incorporated in 2012. Registered share capital is NOK 7.7m, divided into 7700 shares. The company's stated purpose is: “Oppføring og drift av sanitært avløpsanlegg, samt naturlig tilstøtende aktivitet.”. The most recent filed accounts, for the 2025 financial year, show NOK 434,000 in revenue and NOK −125,000 in operating profit.

Key figures · 2025

Revenue
NOK 434,000
Operating profit
NOK −125,000
Equity
NOK 4.3m
Est. value
NOK 2.9m

Financial health · 2025

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

Who owns LI HYTTEKOMFORT AS?

ANNE LANGELAND ESPEDAL
LI HYTTEKOMFORT AS
NOK 434,000 rev. · NOK −125,000 profit

LI HYTTEKOMFORT AS has 20+ registered shareholders:

All shareholders and roles →

Frequently asked questions about LI HYTTEKOMFORT AS

Who owns LI HYTTEKOMFORT AS?

ANNE LANGELAND ESPEDAL is the largest registered owner, with 3.8%.

What is the revenue of LI HYTTEKOMFORT AS?

LI HYTTEKOMFORT AS had revenue of NOK 434,000 in 2025.

Who is the general manager of LI HYTTEKOMFORT AS?

Odd Langeland is registered as general manager of LI HYTTEKOMFORT AS.

Where is LI HYTTEKOMFORT AS based?

LI HYTTEKOMFORT AS has its business address in Stavanger.

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.