BIZTRAC BETA
Retail sale of watches and jewellery

ALADDIN GJØVIK AS

Org. no. 935864941 Limited company (AS) Gjøvik Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 4.9m
Operating profit NOK 1.2m
Equity NOK 945,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

ALADDIN GJØVIK AS is registered as a limited company in Gjøvik, Innlandet with organisation number 935864941. The business is classified under retail sale of watches and jewellery (NACE 47.770). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Kjøp og salg av gull- og sølvgjenstander, mynter, sedler, klokker og andre brukte gjenstander.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.9m in revenue and NOK 1.2m in operating profit.

Key figures · 2025

Revenue
NOK 4.9m
Operating profit
NOK 1.2m
Equity
NOK 945,000
Est. value
NOK 4.3m

Financial health · 2025

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

Who owns ALADDIN GJØVIK AS?

ALADDIN HAMAR AS
ALADDIN GJØVIK AS
NOK 4.9m rev. · NOK 1.2m profit

ALADDIN GJØVIK AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ALADDIN GJØVIK AS

Who owns ALADDIN GJØVIK AS?

ALADDIN HAMAR AS is the largest registered owner, with 80.0%.

What is the revenue of ALADDIN GJØVIK AS?

ALADDIN GJØVIK AS had revenue of NOK 4.9m in 2025.

Who is the general manager of ALADDIN GJØVIK AS?

Kjell Kristoffer Røhne is registered as general manager of ALADDIN GJØVIK AS.

Where is ALADDIN GJØVIK AS based?

ALADDIN GJØVIK AS has its business address in Gjøvik.

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.