BIZTRAC BETA
Retail sale of watches and jewellery

GULLBORGEN AS

Org. no. 917024499 Limited company (AS) Oslo Incorporated 1954 Active
Ownership graph ↗
Revenue 2024 NOK 27.2m
Operating profit NOK −184,000
Equity NOK 15.2m
Incorporated 1954
Employees 10
Share capital NOK 800,000

Signals

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

GULLBORGEN AS is registered as a limited company in Oslo, Oslo with organisation number 917024499. The business is classified under retail sale of watches and jewellery (NACE 47.770). The company was incorporated in 1954 and has 10 registered employees. Registered share capital is NOK 800,000, divided into 200 shares. The company's stated purpose is: “Handel, agentur, produksjon og annen økonomisk virksomhet herunder å interessere seg i andre selskaper med kjøp av aksjer eller på annen måte.”. The most recent filed accounts, for the 2024 financial year, show NOK 27.2m in revenue and NOK −184,000 in operating profit.

Key figures · 2024

Revenue
NOK 27.2m
Operating profit
NOK −184,000
Equity
NOK 15.2m
Est. value
NOK 11.9m

Financial health · 2024

Liquidity
1.34
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
26.0%
Good
Equity as a share of total capital

Who owns GULLBORGEN AS?

GULLBORGEN HOLDING AS
GULLBORGEN AS
NOK 27.2m rev. · NOK −184,000 profit

GULLBORGEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GULLBORGEN AS

Who owns GULLBORGEN AS?

GULLBORGEN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of GULLBORGEN AS?

GULLBORGEN AS had revenue of NOK 27.2m in 2024.

Who is the general manager of GULLBORGEN AS?

Christina Borgen Leonthin is registered as general manager of GULLBORGEN AS.

Where is GULLBORGEN AS based?

GULLBORGEN 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.