biztrac. BETA
COMPANY REGISTER PROFILE
912400719 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Retail sale of watches and jewellery

L GULLHAGEN AS

Org. no. 912400719 Limited company (AS) Gjøvik Incorporated 1979 Active
Ownership graph ↗
Revenue 2025 NOK 10.1m
Operating profit NOK 1.3m
Equity NOK 3.1m
Incorporated 1979
Employees 7
Share capital NOK 200,000

L GULLHAGEN AS is registered as a limited company in Gjøvik, Innlandet with organisation number 912400719. The business is classified under retail sale of watches and jewellery (NACE 47.770). The company was incorporated in 1979 and has 7 registered employees. Registered share capital is NOK 200,000. The company's stated purpose is: “Tilvirke og omsette gullsmedvarer som gjeldende lover og bransjemessig sedvane tilsier samt til- virke og omsette andre varer som står i for- bindelse dermed.”. The most recent filed accounts, for the 2025 financial year, show NOK 10.1m in revenue and NOK 1.3m in operating profit.

Key figures · 2025

Revenue
NOK 10.1m
▲ +8 %
Operating profit
NOK 1.3m
▲ +548 %
Equity
NOK 3.1m
▲ +47 %
Est. value
NOK 4.7m

Financial health · 2025

Liquidity
3.08
Very good
Current assets ÷ current liabilities
Profitability
28.5%
Very good
Return on total assets
Solidity
64.2%
Very good
Equity as a share of total capital

Who owns L GULLHAGEN AS?

L GULLHAGEN AS
NOK 10.1m rev. · NOK 1.3m profit

L GULLHAGEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about L GULLHAGEN AS

Who owns L GULLHAGEN AS?

Anne Slaaen Rogne is the largest registered owner, with 100.0%.

What is the revenue of L GULLHAGEN AS?

L GULLHAGEN AS had revenue of NOK 10.1m in 2025.

Who is the general manager of L GULLHAGEN AS?

Anne Slaaen Rogne is registered as general manager of L GULLHAGEN AS.

Where is L GULLHAGEN AS based?

L GULLHAGEN 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.