BIZTRAC BETA
Rental and leasing of construction and civil engineering machinery and equipment

LOMHEIM AS

Org. no. 989189492 Limited company (AS) Luster Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 1.5m
Operating profit NOK 242,000
Equity NOK 5.5m
Incorporated 2005
Share capital NOK 654,000

LOMHEIM AS is registered as a limited company in Luster, Vestland with organisation number 989189492. The business is classified under rental and leasing of construction and civil engineering machinery and equipment (NACE 77.320). The company was incorporated in 2005. Registered share capital is NOK 654,000, divided into 654 shares. The company's stated purpose is: “Kjøpe, selge og eie aksjer. Eie, drive og leie ut anleggsmaskiner og andre aktiva som naturlig faller inn under slik virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.5m in revenue and NOK 242,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.5m
Operating profit
NOK 242,000
Equity
NOK 5.5m
Est. value
NOK 3.9m

Financial health · 2025

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

Who owns LOMHEIM AS?

DAG LOMHEIM
LOMHEIM AS
NOK 1.5m rev. · NOK 242,000 profit

LOMHEIM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LOMHEIM AS own?

LOMHEIM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LOMHEIM AS

Who owns LOMHEIM AS?

DAG LOMHEIM is the largest registered owner, with 100.0%.

What is the revenue of LOMHEIM AS?

LOMHEIM AS had revenue of NOK 1.5m in 2025.

Who is the general manager of LOMHEIM AS?

Dag Lomheim is registered as general manager of LOMHEIM AS.

Where is LOMHEIM AS based?

LOMHEIM AS has its business address in Hafslo.

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.