BIZTRAC BETA
Site preparation

LEIKANGER MASKINSERVICE AS

Org. no. 985337853 Limited company (AS) Sogndal Incorporated 2003 Active
Ownership graph ↗
Revenue 2025 NOK 1.2m
Operating profit NOK −1.3m
Equity NOK 5.8m
Incorporated 2003
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−1,3 mill kr).

LEIKANGER MASKINSERVICE AS is registered as a limited company in Sogndal, Vestland with organisation number 985337853. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2003. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Maskinentreprenør, transport og anna verksemd som har samanheng med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK −1.3m in operating profit.

Key figures · 2025

Revenue
NOK 1.2m
Operating profit
NOK −1.3m
Equity
NOK 5.8m
Est. value
NOK 2.9m

Financial health · 2025

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

Who owns LEIKANGER MASKINSERVICE AS?

HÅVARD ØLMHEIM
LEIKANGER MASKINSERVICE AS
NOK 1.2m rev. · NOK −1.3m profit

LEIKANGER MASKINSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LEIKANGER MASKINSERVICE AS

Who owns LEIKANGER MASKINSERVICE AS?

HÅVARD ØLMHEIM is the largest registered owner, with 100.0%.

What is the revenue of LEIKANGER MASKINSERVICE AS?

LEIKANGER MASKINSERVICE AS had revenue of NOK 1.2m in 2025.

Who is the general manager of LEIKANGER MASKINSERVICE AS?

Håvard Ølmheim is registered as general manager of LEIKANGER MASKINSERVICE AS.

Where is LEIKANGER MASKINSERVICE AS based?

LEIKANGER MASKINSERVICE AS has its business address in Leikanger.

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.