BIZTRAC BETA
Plumbing installation

ØIVIND LYSTAD AS

Org. no. 936860478 Limited company (AS) Kristiansund Incorporated 1985 Active
Ownership graph ↗
Revenue 2024 NOK 65.0m
Operating profit NOK −4.3m
Equity NOK 5.6m
Incorporated 1985
Employees 25
Share capital NOK 508,000

Signals

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

ØIVIND LYSTAD AS is registered as a limited company in Kristiansund, Møre og Romsdal with organisation number 936860478. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 1985 and has 25 registered employees. Registered share capital is NOK 508,000, divided into 5080 shares. The company's stated purpose is: “Drive autorisert rørleggerforretning og handelsvirksomhet, samt hva hermed står i forbindelse, samt delta i andre virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 65.0m in revenue and NOK −4.3m in operating profit.

Key figures · 2024

Revenue
NOK 65.0m
Operating profit
NOK −4.3m
Equity
NOK 5.6m
Est. value
NOK 24.4m

Financial health · 2024

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

Who owns ØIVIND LYSTAD AS?

LYSTAD HOLDING AS
ØIVIND LYSTAD AS
NOK 65.0m rev. · NOK −4.3m profit

ØIVIND LYSTAD AS has 6 registered shareholders:

All shareholders and roles →

Which companies does ØIVIND LYSTAD AS own?

ØIVIND LYSTAD AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ØIVIND LYSTAD AS

Who owns ØIVIND LYSTAD AS?

LYSTAD HOLDING AS is the largest registered owner, with 66.0%.

What is the revenue of ØIVIND LYSTAD AS?

ØIVIND LYSTAD AS had revenue of NOK 65.0m in 2024.

Where is ØIVIND LYSTAD AS based?

ØIVIND LYSTAD AS has its business address in Kristiansund N.

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.