BIZTRAC BETA
Retail sale of watches and jewellery

BJØRKLUND SANDVIKA AS

Org. no. 994879464 Limited company (AS) Bærum Incorporated 2009 Active
Ownership graph ↗
Revenue 2024 NOK 14.2m
Operating profit NOK 436,000
Equity NOK 5.3m
Incorporated 2009
Employees 16
Share capital NOK 423,000

Signals

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

BJØRKLUND SANDVIKA AS is registered as a limited company in Bærum, Akershus with organisation number 994879464. The business is classified under retail sale of watches and jewellery (NACE 47.770). The company was incorporated in 2009 and has 16 registered employees. Registered share capital is NOK 423,000, divided into 175 shares. The company's stated purpose is: “Forretning innenfor ur- og gullbransjen, med mulighet for engasjement i annen virksomhet av beslektet karakter.”. The most recent filed accounts, for the 2024 financial year, show NOK 14.2m in revenue and NOK 436,000 in operating profit.

Key figures · 2024

Revenue
NOK 14.2m
Operating profit
NOK 436,000
Equity
NOK 5.3m
Est. value
NOK 4.4m

Financial health · 2024

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

Who owns BJØRKLUND SANDVIKA AS?

BJØRKLUND RETAIL AS
BJØRKLUND SANDVIKA AS
NOK 14.2m rev. · NOK 436,000 profit

BJØRKLUND SANDVIKA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BJØRKLUND SANDVIKA AS

Who owns BJØRKLUND SANDVIKA AS?

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

What is the revenue of BJØRKLUND SANDVIKA AS?

BJØRKLUND SANDVIKA AS had revenue of NOK 14.2m in 2024.

Where is BJØRKLUND SANDVIKA AS based?

BJØRKLUND SANDVIKA AS has its business address in Sandvika.

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.