BIZTRAC BETA
Other technical consultancy

LEIDULF LYNGSTAD AS

Org. no. 921418779 Limited company (AS) Molde Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 2.0m
Operating profit NOK 347,000
Equity NOK 1.3m
Incorporated 2018
Share capital NOK 30,000

LEIDULF LYNGSTAD AS is registered as a limited company in Molde, Møre og Romsdal with organisation number 921418779. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Utføre prosess studier, prosess ingeniørtjenester og undervisning for ulike aktører innen olje- og gassrelatert industri og institusjoner samt alt som står i forbindelse med dette, herunder å delta i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.0m in revenue and NOK 347,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.0m
Operating profit
NOK 347,000
Equity
NOK 1.3m
Est. value
NOK 2.4m

Financial health · 2025

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

Who owns LEIDULF LYNGSTAD AS?

LEIDULF ARNE LYNGSTAD
LEIDULF LYNGSTAD AS
NOK 2.0m rev. · NOK 347,000 profit

LEIDULF LYNGSTAD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LEIDULF LYNGSTAD AS

Who owns LEIDULF LYNGSTAD AS?

LEIDULF ARNE LYNGSTAD is the largest registered owner, with 100.0%.

What is the revenue of LEIDULF LYNGSTAD AS?

LEIDULF LYNGSTAD AS had revenue of NOK 2.0m in 2025.

Who is the general manager of LEIDULF LYNGSTAD AS?

Leidulf Arne Lyngstad is registered as general manager of LEIDULF LYNGSTAD AS.

Where is LEIDULF LYNGSTAD AS based?

LEIDULF LYNGSTAD AS has its business address in Molde.

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.