BIZTRAC BETA
Development of building projects

LERVIK EIENDOM HOLDING AS

Org. no. 998768411 Limited company (AS) Haugesund Incorporated 2012 Active
Ownership graph ↗
Operating profit NOK −38,000
Equity NOK 753,000
Incorporated 2012
Share capital NOK 50,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−38k kr).
  • Nylig endring 2026-05-06 Aksjekapital registrert 2026-05-06.

LERVIK EIENDOM HOLDING AS is registered as a limited company in Haugesund, Rogaland with organisation number 998768411. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2012. Registered share capital is NOK 50,000, divided into 50 shares. The company's stated purpose is: “Investering i og utvikling av fast eiendom. samt det som naturlig står i forbindelse med dette.”.

Key figures · 2024

Operating profit
NOK −38,000
Equity
NOK 753,000
Est. value
NOK 593,000

Financial health · 2024

Liquidity
0.29
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
32.6%
Good
Equity as a share of total capital

Who owns LERVIK EIENDOM HOLDING AS?

KNUT STIAN LERVIK
LERVIK EIENDOM HOLDING AS
· NOK −38,000 profit

LERVIK EIENDOM HOLDING AS has 4 registered shareholders:

All shareholders and roles →

Which companies does LERVIK EIENDOM HOLDING AS own?

LERVIK EIENDOM HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LERVIK EIENDOM HOLDING AS

Who owns LERVIK EIENDOM HOLDING AS?

KNUT STIAN LERVIK is the largest registered owner, with 25.0%.

Who is the general manager of LERVIK EIENDOM HOLDING AS?

Knut Stian Lervik is registered as general manager of LERVIK EIENDOM HOLDING AS.

Where is LERVIK EIENDOM HOLDING AS based?

LERVIK EIENDOM HOLDING AS has its business address in Haugesund.

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.