biztrac. BETA
COMPANY REGISTER PROFILE
931752502 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

LYNGENGÅRDEN EIENDOM AS

Org. no. 931752502 Limited company (AS) Vefsn Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 1.2m
Operating profit NOK 547,000
Equity NOK 1.1m
Incorporated 2023
Share capital NOK 30,000

LYNGENGÅRDEN EIENDOM AS is registered as a limited company in Vefsn, Nordland with organisation number 931752502. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Erverve, eie samt drive utleie av fast eiendom, og virksomhet som hermed står i forbindelse, herunder deltakelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK 547,000 in operating profit.

Former names: NFH 230615 AS

Key figures · 2025

Revenue
NOK 1.2m
▲ +2 %
Operating profit
NOK 547,000
▼ −19 %
Equity
NOK 1.1m
▲ +10 %
Est. value
NOK 1.6m

Financial health · 2025

Liquidity
22.38
Very good
Current assets ÷ current liabilities
Profitability
5.1%
Weak
Return on total assets
Solidity
8.8%
Weak
Equity as a share of total capital

Who owns LYNGENGÅRDEN EIENDOM AS?

LYNGENGÅRDEN EIENDOM AS
NOK 1.2m rev. · NOK 547,000 profit

LYNGENGÅRDEN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LYNGENGÅRDEN EIENDOM AS

Who owns LYNGENGÅRDEN EIENDOM AS?

HELGELAND HOTELLINVEST AS is the largest registered owner, with 100.0%.

What is the revenue of LYNGENGÅRDEN EIENDOM AS?

LYNGENGÅRDEN EIENDOM AS had revenue of NOK 1.2m in 2025.

Where is LYNGENGÅRDEN EIENDOM AS based?

LYNGENGÅRDEN EIENDOM AS has its business address in Mosjøen.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.