BIZTRAC BETA
Retail sale of watches and jewellery

FENESS UR & GULL LAGUNEN AS

Org. no. 984158432 Limited company (AS) Bergen Incorporated 2001 Active
Ownership graph ↗
Revenue 2024 NOK 18.0m
Operating profit NOK 3.0m
Equity NOK 2.7m
Incorporated 2001
Employees 13
Share capital NOK 300,000

FENESS UR & GULL LAGUNEN AS is registered as a limited company in Bergen, Vestland with organisation number 984158432. The business is classified under retail sale of watches and jewellery (NACE 47.770). The company was incorporated in 2001 and has 13 registered employees. Registered share capital is NOK 300,000, divided into 300 shares. The company's stated purpose is: “Handel med ur og gullvarer og alt hva dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 18.0m in revenue and NOK 3.0m in operating profit.

Key figures · 2024

Revenue
NOK 18.0m
Operating profit
NOK 3.0m
Equity
NOK 2.7m
Est. value
NOK 10.8m

Financial health · 2024

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

Who owns FENESS UR & GULL LAGUNEN AS?

FENESS UR AS
FENESS UR & GULL LAGUNEN AS
NOK 18.0m rev. · NOK 3.0m profit

FENESS UR & GULL LAGUNEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FENESS UR & GULL LAGUNEN AS

Who owns FENESS UR & GULL LAGUNEN AS?

FENESS UR AS is the largest registered owner, with 100.0%.

What is the revenue of FENESS UR & GULL LAGUNEN AS?

FENESS UR & GULL LAGUNEN AS had revenue of NOK 18.0m in 2024.

Who is the general manager of FENESS UR & GULL LAGUNEN AS?

Hilde Feness Heggernes is registered as general manager of FENESS UR & GULL LAGUNEN AS.

Where is FENESS UR & GULL LAGUNEN AS based?

FENESS UR & GULL LAGUNEN AS has its business address in Rådal.

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.