BIZTRAC BETA
Rental and leasing of construction and civil engineering machinery and equipment

LV EIENDOM AS

Org. no. 934802586 Limited company (AS) Kristiansand Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 160,000
Operating profit NOK 77,000
Equity NOK 17,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-04-20 Adresseendring registrert 2026-04-20.

LV EIENDOM AS is registered as a limited company in Kristiansand, Agder with organisation number 934802586. The business is classified under rental and leasing of construction and civil engineering machinery and equipment (NACE 77.320). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Drift av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 160,000 in revenue and NOK 77,000 in operating profit.

Key figures · 2025

Revenue
NOK 160,000
Operating profit
NOK 77,000
Equity
NOK 17,000
Est. value
NOK 220,000

Financial health · 2025

Liquidity
0.02
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
0.9%
Weak
Equity as a share of total capital

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

Who owns LV EIENDOM AS?

B VINGERHAGEN AS
LV EIENDOM AS
NOK 160,000 rev. · NOK 77,000 profit

LV EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LV EIENDOM AS

Who owns LV EIENDOM AS?

B VINGERHAGEN AS is the largest registered owner, with 50.0%.

What is the revenue of LV EIENDOM AS?

LV EIENDOM AS had revenue of NOK 160,000 in 2025.

Who is the general manager of LV EIENDOM AS?

Benjamin Vingerhagen is registered as general manager of LV EIENDOM AS.

Where is LV EIENDOM AS based?

LV EIENDOM AS has its business address in Kristiansand S.

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.