BIZTRAC BETA
Non-specialised retail sale of predominately food, beverages or tobacco

KVAM LAVPRIS AS

Org. no. 988072729 Limited company (AS) Molde Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −1.3m
Equity NOK 3.8m
Incorporated 2005
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−1,3 mill kr).

KVAM LAVPRIS AS is registered as a limited company in Molde, Møre og Romsdal with organisation number 988072729. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Å drive handel med dagligvarer samt alt som står i forbindelse med dette, herunder deltakelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −1.3m in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −1.3m
Equity
NOK 3.8m
Est. value
NOK 4.7m

Financial health · 2025

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

Who owns KVAM LAVPRIS AS?

HÅKON LJØKJEL
KVAM LAVPRIS AS
NOK 0 rev. · NOK −1.3m profit

KVAM LAVPRIS AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KVAM LAVPRIS AS

Who owns KVAM LAVPRIS AS?

HÅKON LJØKJEL is the largest registered owner, with 60.0%.

What is the revenue of KVAM LAVPRIS AS?

KVAM LAVPRIS AS had revenue of NOK 0 in 2025.

Who is the general manager of KVAM LAVPRIS AS?

Håkon Ljøkjel is registered as general manager of KVAM LAVPRIS AS.

Where is KVAM LAVPRIS AS based?

KVAM LAVPRIS AS has its business address in Molde.

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.