BIZTRAC BETA
Rental and operating of own or leased real estate

KVINLAUG EIENDOM AS

Org. no. 998373700 Limited company (AS) Kvinesdal Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 399,000
Operating profit NOK 278,000
Equity NOK 1.2m
Incorporated 2012
Share capital NOK 250,000

KVINLAUG EIENDOM AS is registered as a limited company in Kvinesdal, Agder with organisation number 998373700. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2012. Registered share capital is NOK 250,000, divided into 250 shares. The company's stated purpose is: “Kjøp og salg av aksjer, investering i og utleie av fast eiendom, investering i og utleie av andre driftsmidler, salg av administrasjonstjenester samt alt som hører naturlig til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 399,000 in revenue and NOK 278,000 in operating profit.

Key figures · 2025

Revenue
NOK 399,000
Operating profit
NOK 278,000
Equity
NOK 1.2m
Est. value
NOK 1.4m

Financial health · 2025

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

Who owns KVINLAUG EIENDOM AS?

JONNY KVINLAUG
KVINLAUG EIENDOM AS
NOK 399,000 rev. · NOK 278,000 profit

KVINLAUG EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KVINLAUG EIENDOM AS

Who owns KVINLAUG EIENDOM AS?

JONNY KVINLAUG is the largest registered owner, with 80.0%.

What is the revenue of KVINLAUG EIENDOM AS?

KVINLAUG EIENDOM AS had revenue of NOK 399,000 in 2025.

Who is the general manager of KVINLAUG EIENDOM AS?

Jonny Kvinlaug is registered as general manager of KVINLAUG EIENDOM AS.

Where is KVINLAUG EIENDOM AS based?

KVINLAUG EIENDOM AS has its business address in Øyestranda.

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.