BIZTRAC BETA
Retail sale of watches and jewellery

KNARVIK KLOKKER OG SMYKKER AS

Org. no. 847568542 Limited company (AS) Alver Incorporated 1988 Active
Ownership graph ↗
Revenue 2024 NOK 8.1m
Operating profit NOK −240,000
Equity NOK 1.6m
Incorporated 1988
Employees 11
Share capital NOK 150,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−240k kr).

KNARVIK KLOKKER OG SMYKKER AS is registered as a limited company in Alver, Vestland with organisation number 847568542. The business is classified under retail sale of watches and jewellery (NACE 47.770). The company was incorporated in 1988 and has 11 registered employees. Registered share capital is NOK 150,000, divided into 150 shares. The company's stated purpose is: “Detaljvirksomhet med i hovedsak salg av klokker, smykker og relaterte varer.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.1m in revenue and NOK −240,000 in operating profit.

Key figures · 2024

Revenue
NOK 8.1m
Operating profit
NOK −240,000
Equity
NOK 1.6m
Est. value
NOK 3.4m

Financial health · 2024

Liquidity
1.39
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
35.6%
Good
Equity as a share of total capital

Who owns KNARVIK KLOKKER OG SMYKKER AS?

BJØRKLUND RETAIL AS
KNARVIK KLOKKER OG SMYKKER AS
NOK 8.1m rev. · NOK −240,000 profit

KNARVIK KLOKKER OG SMYKKER AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KNARVIK KLOKKER OG SMYKKER AS

Who owns KNARVIK KLOKKER OG SMYKKER AS?

BJØRKLUND RETAIL AS is the largest registered owner, with 66.7%.

What is the revenue of KNARVIK KLOKKER OG SMYKKER AS?

KNARVIK KLOKKER OG SMYKKER AS had revenue of NOK 8.1m in 2024.

Where is KNARVIK KLOKKER OG SMYKKER AS based?

KNARVIK KLOKKER OG SMYKKER AS has its business address in Isdalstø.

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.