BIZTRAC BETA
Retail sale of watches and jewellery

GULLSMED K O LIBERG AS

Org. no. 913871731 Limited company (AS) Hamar Incorporated 1975 Active
Ownership graph ↗
Revenue 2025 NOK 8.2m
Operating profit NOK 705,000
Equity NOK 2.5m
Incorporated 1975
Employees 6
Share capital NOK 200,000

GULLSMED K O LIBERG AS is registered as a limited company in Hamar, Innlandet with organisation number 913871731. The business is classified under retail sale of watches and jewellery (NACE 47.770). The company was incorporated in 1975 and has 6 registered employees. Registered share capital is NOK 200,000. The company's stated purpose is: “Drive omsetning og verksted, og hva dermed står i forbindelse, samt ved aksjetegning eller på annen måte å gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2025 financial year, show NOK 8.2m in revenue and NOK 705,000 in operating profit.

Key figures · 2025

Revenue
NOK 8.2m
Operating profit
NOK 705,000
Equity
NOK 2.5m
Est. value
NOK 3.9m

Financial health · 2025

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

Who owns GULLSMED K O LIBERG AS?

KLAUS OVE LIBERG
GULLSMED K O LIBERG AS
NOK 8.2m rev. · NOK 705,000 profit

GULLSMED K O LIBERG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GULLSMED K O LIBERG AS

Who owns GULLSMED K O LIBERG AS?

KLAUS OVE LIBERG is the largest registered owner, with 100.0%.

What is the revenue of GULLSMED K O LIBERG AS?

GULLSMED K O LIBERG AS had revenue of NOK 8.2m in 2025.

Who is the general manager of GULLSMED K O LIBERG AS?

Klaus Ove Liberg is registered as general manager of GULLSMED K O LIBERG AS.

Where is GULLSMED K O LIBERG AS based?

GULLSMED K O LIBERG AS has its business address in Hamar.

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.