BIZTRAC BETA
Manufacture of jewellery and related articles

TOM JØRGENSEN DESIGN AS

Org. no. 997110013 Limited company (AS) Øygarden Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 2.2m
Operating profit NOK 372,000
Equity NOK 1.5m
Incorporated 2011
Share capital NOK 100,000

Signals

1 flags
  • Nylig endring 2026-07-09 Adresseendring registrert 2026-07-09.

TOM JØRGENSEN DESIGN AS is registered as a limited company in Øygarden, Vestland with organisation number 997110013. The business is classified under manufacture of jewellery and related articles (NACE 32.120). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Design og produksjon av egne smykker/ kolleksjoner for videresalg.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.2m in revenue and NOK 372,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.2m
Operating profit
NOK 372,000
Equity
NOK 1.5m
Est. value
NOK 2.1m

Financial health · 2024

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

Who owns TOM JØRGENSEN DESIGN AS?

TOM JØRGENSEN
TOM JØRGENSEN DESIGN AS
NOK 2.2m rev. · NOK 372,000 profit

TOM JØRGENSEN DESIGN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TOM JØRGENSEN DESIGN AS

Who owns TOM JØRGENSEN DESIGN AS?

TOM JØRGENSEN is the largest registered owner, with 100.0%.

What is the revenue of TOM JØRGENSEN DESIGN AS?

TOM JØRGENSEN DESIGN AS had revenue of NOK 2.2m in 2024.

Who is the general manager of TOM JØRGENSEN DESIGN AS?

Tom Jørgensen is registered as general manager of TOM JØRGENSEN DESIGN AS.

Where is TOM JØRGENSEN DESIGN AS based?

TOM JØRGENSEN DESIGN AS has its business address in Straume.

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.