BIZTRAC BETA
Retail sale of watches and jewellery

BJØRKLUND GUNERIUS AS

Org. no. 832660892 Limited company (AS) Oslo Incorporated 1983 Active
Ownership graph ↗
Revenue 2024 NOK 6.3m
Operating profit NOK 354,000
Equity NOK 2.2m
Incorporated 1983
Employees 5
Share capital NOK 701,000

BJØRKLUND GUNERIUS AS is registered as a limited company in Oslo, Oslo with organisation number 832660892. The business is classified under retail sale of watches and jewellery (NACE 47.770). The company was incorporated in 1983 and has 5 registered employees. Registered share capital is NOK 701,000, divided into 50100 shares. The company's stated purpose is: “Forretning innen ur og smykker detalj og hva som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.3m in revenue and NOK 354,000 in operating profit.

Key figures · 2024

Revenue
NOK 6.3m
Operating profit
NOK 354,000
Equity
NOK 2.2m
Est. value
NOK 2.6m

Financial health · 2024

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

Who owns BJØRKLUND GUNERIUS AS?

HBS 1969 AS
BJØRKLUND GUNERIUS AS
NOK 6.3m rev. · NOK 354,000 profit

BJØRKLUND GUNERIUS AS has 5 registered shareholders:

All shareholders and roles →

Which companies does BJØRKLUND GUNERIUS AS own?

BJØRKLUND GUNERIUS AS holds a stake in 1 company:

See the full ownership structure →

Group structure

BJØRKLUND GUNERIUS AS er morselskap for 2 datterselskaper:

Frequently asked questions about BJØRKLUND GUNERIUS AS

Who owns BJØRKLUND GUNERIUS AS?

HBS 1969 AS is the largest registered owner, with 51.1%.

What is the revenue of BJØRKLUND GUNERIUS AS?

BJØRKLUND GUNERIUS AS had revenue of NOK 6.3m in 2024.

Where is BJØRKLUND GUNERIUS AS based?

BJØRKLUND GUNERIUS AS has its business address in Oslo.

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.