BIZTRAC BETA
Non-specialised retail sale of predominately food, beverages or tobacco

LANDHANDLERIET GURSKEN AS

Org. no. 926646605 Limited company (AS) Sande Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 18.1m
Operating profit NOK 845,000
Equity NOK 1.7m
Incorporated 2021
Employees 8
Share capital NOK 30,000

LANDHANDLERIET GURSKEN AS is registered as a limited company in Sande, Møre og Romsdal with organisation number 926646605. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2021 and has 8 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Dagligvare.”. The most recent filed accounts, for the 2024 financial year, show NOK 18.1m in revenue and NOK 845,000 in operating profit.

Key figures · 2024

Revenue
NOK 18.1m
Operating profit
NOK 845,000
Equity
NOK 1.7m
Est. value
NOK 4.2m

Financial health · 2024

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

Who owns LANDHANDLERIET GURSKEN AS?

HENRIETTE SÆTRE HAUGE
LANDHANDLERIET GURSKEN AS
NOK 18.1m rev. · NOK 845,000 profit

LANDHANDLERIET GURSKEN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LANDHANDLERIET GURSKEN AS

Who owns LANDHANDLERIET GURSKEN AS?

HENRIETTE SÆTRE HAUGE is the largest registered owner, with 70.0%.

What is the revenue of LANDHANDLERIET GURSKEN AS?

LANDHANDLERIET GURSKEN AS had revenue of NOK 18.1m in 2024.

Who is the general manager of LANDHANDLERIET GURSKEN AS?

Henriette Sætre Hauge is registered as general manager of LANDHANDLERIET GURSKEN AS.

Where is LANDHANDLERIET GURSKEN AS based?

LANDHANDLERIET GURSKEN AS has its business address in Gursken.

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.