BIZTRAC BETA
Steam and air conditioning supply

LOM BIOVARME AS

Org. no. 999150829 Limited company (AS) Lom Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 2.5m
Operating profit NOK 356,000
Equity NOK 3.6m
Incorporated 2012
Share capital NOK 2.0m

LOM BIOVARME AS is registered as a limited company in Lom, Innlandet with organisation number 999150829. The business is classified under steam and air conditioning supply (NACE 35.300). The company was incorporated in 2012. Registered share capital is NOK 2.0m, divided into 2032 shares. The company's stated purpose is: “Å drive produksjon og salg av biovarme og hva dermed står i forbindelse, samt ved aksjetegning eller på andre måter engasjere seg i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.5m in revenue and NOK 356,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.5m
Operating profit
NOK 356,000
Equity
NOK 3.6m
Est. value
NOK 3.6m

Financial health · 2025

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

Who owns LOM BIOVARME AS?

ODD HELGE EGGEN KVAMME
LOM BIOVARME AS
NOK 2.5m rev. · NOK 356,000 profit

LOM BIOVARME AS has 4 registered shareholders:

All shareholders and roles →

Which companies does LOM BIOVARME AS own?

LOM BIOVARME AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about LOM BIOVARME AS

Who owns LOM BIOVARME AS?

ODD HELGE EGGEN KVAMME is the largest registered owner, with 25.0%.

What is the revenue of LOM BIOVARME AS?

LOM BIOVARME AS had revenue of NOK 2.5m in 2025.

Who is the general manager of LOM BIOVARME AS?

Hallvard Helland is registered as general manager of LOM BIOVARME AS.

Where is LOM BIOVARME AS based?

LOM BIOVARME AS has its business address in Lom.

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.