BIZTRAC BETA
Restaurant activities

HANKØSUND RESTAURANT AS

Org. no. 813470462 Limited company (AS) Fredrikstad Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 5.8m
Operating profit NOK −5,000
Equity NOK 534,000
Incorporated 2014
Employees 9
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−5k kr).

HANKØSUND RESTAURANT AS is registered as a limited company in Fredrikstad, Østfold with organisation number 813470462. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2014 and has 9 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Restaurantdrift og catering.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.8m in revenue and NOK −5,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.8m
Operating profit
NOK −5,000
Equity
NOK 534,000
Est. value
NOK 4.3m

Financial health · 2025

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

Who owns HANKØSUND RESTAURANT AS?

HANKØSUND HOLDING AS
HANKØSUND RESTAURANT AS
NOK 5.8m rev. · NOK −5,000 profit

HANKØSUND RESTAURANT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HANKØSUND RESTAURANT AS

Who owns HANKØSUND RESTAURANT AS?

HANKØSUND HOLDING AS is the largest registered owner, with 90.0%.

What is the revenue of HANKØSUND RESTAURANT AS?

HANKØSUND RESTAURANT AS had revenue of NOK 5.8m in 2025.

Who is the general manager of HANKØSUND RESTAURANT AS?

Christian Unterweger is registered as general manager of HANKØSUND RESTAURANT AS.

Where is HANKØSUND RESTAURANT AS based?

HANKØSUND RESTAURANT AS has its business address in Gressvik.

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.