BIZTRAC BETA
Rental and operating of own or leased real estate

R. LYNGVÆR EIENDOM AS

Org. no. 818625952 Limited company (AS) Frøya Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 2.5m
Operating profit NOK 840,000
Equity NOK 1.1m
Incorporated 2017
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

R. LYNGVÆR EIENDOM AS is registered as a limited company in Frøya, Trøndelag with organisation number 818625952. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “utleie og forvaltning av eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.5m in revenue and NOK 840,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.5m
Operating profit
NOK 840,000
Equity
NOK 1.1m
Est. value
NOK 1.7m

Financial health · 2024

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

Who owns R. LYNGVÆR EIENDOM AS?

LYNGVÆR HOLDING AS
R. LYNGVÆR EIENDOM AS
NOK 2.5m rev. · NOK 840,000 profit

R. LYNGVÆR EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about R. LYNGVÆR EIENDOM AS

Who owns R. LYNGVÆR EIENDOM AS?

LYNGVÆR HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of R. LYNGVÆR EIENDOM AS?

R. LYNGVÆR EIENDOM AS had revenue of NOK 2.5m in 2024.

Who is the general manager of R. LYNGVÆR EIENDOM AS?

Roger Lyngvær is registered as general manager of R. LYNGVÆR EIENDOM AS.

Where is R. LYNGVÆR EIENDOM AS based?

R. LYNGVÆR EIENDOM AS has its business address in Dyrvik.

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.