BIZTRAC BETA
Business and other management consultancy activities

LYNGNESET INVEST AS

Org. no. 918322574 Limited company (AS) Sveio Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −4.1m
Equity NOK 939.9m
Incorporated 2016
Share capital NOK 150,000

Signals

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

LYNGNESET INVEST AS is registered as a limited company in Sveio, Vestland with organisation number 918322574. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2016. Registered share capital is NOK 150,000, divided into 30000 shares. The company's stated purpose is: “konsulent- og investeringsvirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −4.1m in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −4.1m
Equity
NOK 939.9m
Est. value
NOK 1.1bn

Financial health · 2024

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

Who owns LYNGNESET INVEST AS?

BREIVET AS
LYNGNESET INVEST AS
NOK 0 rev. · NOK −4.1m profit

LYNGNESET INVEST AS has 7 registered shareholders:

All shareholders and roles →

Which companies does LYNGNESET INVEST AS own?

LYNGNESET INVEST AS holds stakes in 29 companies:

See the full ownership structure →

Group structure

LYNGNESET INVEST AS er morselskap for 1 datterselskap:

Frequently asked questions about LYNGNESET INVEST AS

Who owns LYNGNESET INVEST AS?

BREIVET AS is the largest registered owner, with 25.0%.

What is the revenue of LYNGNESET INVEST AS?

LYNGNESET INVEST AS had revenue of NOK 0 in 2024.

Where is LYNGNESET INVEST AS based?

LYNGNESET INVEST AS has its business address in Sveio.

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.