BIZTRAC BETA
Other non-specialised retail sale

EIKER LAVPRIS AS

Org. no. 982169844 Limited company (AS) Øvre Eiker Incorporated 2000 Active
Ownership graph ↗
Revenue 2025 NOK 39.9m
Operating profit NOK −618,000
Equity NOK 1.1m
Incorporated 2000
Employees 13
Share capital NOK 370,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−618k kr).

EIKER LAVPRIS AS is registered as a limited company in Øvre Eiker, Buskerud with organisation number 982169844. The business is classified under other non-specialised retail sale (NACE 47.120). The company was incorporated in 2000 and has 13 registered employees. Registered share capital is NOK 370,000, divided into 370 shares. The company's stated purpose is: “Handel, samt hva dermed står i forbindelse, herunder deltakelse i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 39.9m in revenue and NOK −618,000 in operating profit.

Key figures · 2025

Revenue
NOK 39.9m
Operating profit
NOK −618,000
Equity
NOK 1.1m
Est. value
NOK 13.1m

Financial health · 2024

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

Who owns EIKER LAVPRIS AS?

KETIL ELVEKROK HANSEN
EIKER LAVPRIS AS
NOK 39.9m rev. · NOK −618,000 profit

EIKER LAVPRIS AS has 3 registered shareholders:

All shareholders and roles →

Which companies does EIKER LAVPRIS AS own?

EIKER LAVPRIS AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about EIKER LAVPRIS AS

Who owns EIKER LAVPRIS AS?

KETIL ELVEKROK HANSEN is the largest registered owner, with 62.7%.

What is the revenue of EIKER LAVPRIS AS?

EIKER LAVPRIS AS had revenue of NOK 39.9m in 2025.

Where is EIKER LAVPRIS AS based?

EIKER LAVPRIS AS has its business address in Hokksund.

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.