BIZTRAC BETA
Rental and operating of own or leased real estate

LGV HOLDING AS

Org. no. 817661912 Limited company (AS) Moss Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 2.2m
Operating profit NOK 597,000
Equity NOK 78.4m
Incorporated 2016
Share capital NOK 609,000

LGV HOLDING AS is registered as a limited company in Moss, Østfold with organisation number 817661912. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2016. Registered share capital is NOK 609,000, divided into 500 shares. The company's stated purpose is: “Investering i aksjer, andre virksomheter og fast eiendom samt alt som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.2m in revenue and NOK 597,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.2m
Operating profit
NOK 597,000
Equity
NOK 78.4m
Est. value
NOK 55.1m

Financial health · 2024

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

Who owns LGV HOLDING AS?

JØGVAN DANIEL JOENSEN
LGV HOLDING AS
NOK 2.2m rev. · NOK 597,000 profit

LGV HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LGV HOLDING AS own?

LGV HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about LGV HOLDING AS

Who owns LGV HOLDING AS?

JØGVAN DANIEL JOENSEN is the largest registered owner, with 100.0%.

What is the revenue of LGV HOLDING AS?

LGV HOLDING AS had revenue of NOK 2.2m in 2024.

Who is the general manager of LGV HOLDING AS?

Jøgvan Daniel Joensen is registered as general manager of LGV HOLDING AS.

Where is LGV HOLDING AS based?

LGV HOLDING AS has its business address in Moss.

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.