BIZTRAC BETA
Retail sale of watches and jewellery

GULLGRUVEN AS

Org. no. 929254163 Limited company (AS) Bærum Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 12.9m
Operating profit NOK 1.4m
Equity NOK 100,000
Incorporated 2022
Employees 7
Share capital NOK 100,000

Signals

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

GULLGRUVEN AS is registered as a limited company in Bærum, Akershus with organisation number 929254163. The business is classified under retail sale of watches and jewellery (NACE 47.770). The company was incorporated in 2022 and has 7 registered employees. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Salg av gull-, sølvvarer og ur og andre produkter som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 12.9m in revenue and NOK 1.4m in operating profit.

Key figures · 2024

Revenue
NOK 12.9m
Operating profit
NOK 1.4m
Equity
NOK 100,000
Est. value
NOK 4.4m

Financial health · 2025

Liquidity
1.02
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
1.6%
Not satisfactory
Equity as a share of total capital

Who owns GULLGRUVEN AS?

MININVEST AS
GULLGRUVEN AS
NOK 12.9m rev. · NOK 1.4m profit

GULLGRUVEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GULLGRUVEN AS

Who owns GULLGRUVEN AS?

MININVEST AS is the largest registered owner, with 100.0%.

What is the revenue of GULLGRUVEN AS?

GULLGRUVEN AS had revenue of NOK 12.9m in 2024.

Who is the general manager of GULLGRUVEN AS?

Aisha Shad is registered as general manager of GULLGRUVEN AS.

Where is GULLGRUVEN AS based?

GULLGRUVEN AS has its business address in Bekkestua.

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.