BIZTRAC BETA
Retail sale of watches and jewellery

GULLSMED LIV LERDAHL A/S

Org. no. 947452606 Limited company (AS) Ullensaker Incorporated 1988 Active
Ownership graph ↗
Revenue 2024 NOK 10.7m
Operating profit NOK −112,000
Equity NOK 3.4m
Incorporated 1988
Employees 10
Share capital NOK 500,000

Signals

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

GULLSMED LIV LERDAHL A/S is registered as a limited company in Ullensaker, Akershus with organisation number 947452606. The business is classified under retail sale of watches and jewellery (NACE 47.770). The company was incorporated in 1988 and has 10 registered employees. Registered share capital is NOK 500,000, divided into 50 shares. The company's stated purpose is: “Handel, service og produksjon.”. The most recent filed accounts, for the 2024 financial year, show NOK 10.7m in revenue and NOK −112,000 in operating profit.

Key figures · 2024

Revenue
NOK 10.7m
Operating profit
NOK −112,000
Equity
NOK 3.4m
Est. value
NOK 4.5m

Financial health · 2024

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

Who owns GULLSMED LIV LERDAHL A/S?

LIV LERDAHL
GULLSMED LIV LERDAHL A/S
NOK 10.7m rev. · NOK −112,000 profit

GULLSMED LIV LERDAHL A/S has 1 registered shareholder:

All shareholders and roles →

Which companies does GULLSMED LIV LERDAHL A/S own?

GULLSMED LIV LERDAHL A/S holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about GULLSMED LIV LERDAHL A/S

Who owns GULLSMED LIV LERDAHL A/S?

LIV LERDAHL is the largest registered owner, with 100.0%.

What is the revenue of GULLSMED LIV LERDAHL A/S?

GULLSMED LIV LERDAHL A/S had revenue of NOK 10.7m in 2024.

Where is GULLSMED LIV LERDAHL A/S based?

GULLSMED LIV LERDAHL A/S has its business address in Jessheim.

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.