BIZTRAC BETA
Retail sale of watches and jewellery

GULL-KROKEN AS

Org. no. 928408051 Limited company (AS) Hustadvika Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 1.5m
Operating profit NOK 336,000
Equity NOK 633,000
Incorporated 2021
Share capital NOK 100,000

GULL-KROKEN AS is registered as a limited company in Hustadvika, Møre og Romsdal with organisation number 928408051. The business is classified under retail sale of watches and jewellery (NACE 47.770). The company was incorporated in 2021. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Salg, produksjon, handel og agenturvirksomhet av gull-, sølvvarer og tekstil/tilverkning bl. norske bunader og tilbehør, samt deltagelse i andre selskaper og det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.5m in revenue and NOK 336,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.5m
Operating profit
NOK 336,000
Equity
NOK 633,000
Est. value
NOK 1.4m

Financial health · 2025

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

Who owns GULL-KROKEN AS?

INGER LISE GRØNBECH HAGERUP
GULL-KROKEN AS
NOK 1.5m rev. · NOK 336,000 profit

GULL-KROKEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GULL-KROKEN AS

Who owns GULL-KROKEN AS?

INGER LISE GRØNBECH HAGERUP is the largest registered owner, with 100.0%.

What is the revenue of GULL-KROKEN AS?

GULL-KROKEN AS had revenue of NOK 1.5m in 2025.

Who is the general manager of GULL-KROKEN AS?

Inger Lise Grønbech Hagerup is registered as general manager of GULL-KROKEN AS.

Where is GULL-KROKEN AS based?

GULL-KROKEN AS has its business address in Malmefjorden.

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.