BIZTRAC BETA
Rental and operating of own or leased real estate

LERVIG EIENDOM AS

Org. no. 812587722 Limited company (AS) Stavanger Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 244,000
Operating profit NOK 76,000
Equity NOK −924,000
Incorporated 2013
Share capital NOK 830,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−924k kr).

LERVIG EIENDOM AS is registered as a limited company in Stavanger, Rogaland with organisation number 812587722. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2013. Registered share capital is NOK 830,000, divided into 8300 shares. The company's stated purpose is: “Eie og drifte eiendommer, kjøp og salg av aksjer eller andre verdipapirer og hva herved står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 244,000 in revenue and NOK 76,000 in operating profit.

Key figures · 2025

Revenue
NOK 244,000
Operating profit
NOK 76,000
Equity
NOK −924,000
Est. value
NOK 519,000

Financial health · 2025

Liquidity
47.35
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-17.4%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns LERVIG EIENDOM AS?

HUNDVÅG INVESTERING AS
LERVIG EIENDOM AS
NOK 244,000 rev. · NOK 76,000 profit

LERVIG EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LERVIG EIENDOM AS

Who owns LERVIG EIENDOM AS?

HUNDVÅG INVESTERING AS is the largest registered owner, with 50.0%.

What is the revenue of LERVIG EIENDOM AS?

LERVIG EIENDOM AS had revenue of NOK 244,000 in 2025.

Where is LERVIG EIENDOM AS based?

LERVIG EIENDOM AS has its business address in Stavanger.

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.