BIZTRAC BETA
Restaurant activities

PETERHEAD AS

Org. no. 983534805 Limited company (AS) Risør Incorporated 2001 Active
Ownership graph ↗
Revenue 2024 NOK 10.7m
Operating profit NOK −439,000
Equity NOK 1.2m
Incorporated 2001
Employees 21
Share capital NOK 185,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−439k kr).

PETERHEAD AS is registered as a limited company in Risør, Agder with organisation number 983534805. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2001 and has 21 registered employees. Registered share capital is NOK 185,000, divided into 154 shares. The company's stated purpose is: “Selskapets formål er restaurantdrift og hva hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 10.7m in revenue and NOK −439,000 in operating profit.

Key figures · 2024

Revenue
NOK 10.7m
Operating profit
NOK −439,000
Equity
NOK 1.2m
Est. value
NOK 8.0m

Financial health · 2024

Liquidity
0.57
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
36.1%
Good
Equity as a share of total capital

Who owns PETERHEAD AS?

FANTHOLMEN HOLDING AS
PETERHEAD AS
NOK 10.7m rev. · NOK −439,000 profit

PETERHEAD AS has 1 registered shareholder:

All shareholders and roles →

Which companies does PETERHEAD AS own?

PETERHEAD AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about PETERHEAD AS

Who owns PETERHEAD AS?

FANTHOLMEN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of PETERHEAD AS?

PETERHEAD AS had revenue of NOK 10.7m in 2024.

Who is the general manager of PETERHEAD AS?

Hans Roar Waaler is registered as general manager of PETERHEAD AS.

Where is PETERHEAD AS based?

PETERHEAD AS has its business address in Risør.

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.