BIZTRAC BETA
Restaurant activities

EGON HAUGESUND AS

Org. no. 958721692 Limited company (AS) Haugesund Incorporated 1990 Active
Ownership graph ↗
Revenue 2024 NOK 36.0m
Operating profit NOK 5.2m
Equity NOK 2.0m
Incorporated 1990
Employees 34
Share capital NOK 100,000

EGON HAUGESUND AS is registered as a limited company in Haugesund, Rogaland with organisation number 958721692. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 1990 and has 34 registered employees. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Serveringsvirksomhet samt annen virksomhet som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 36.0m in revenue and NOK 5.2m in operating profit.

Key figures · 2024

Revenue
NOK 36.0m
Operating profit
NOK 5.2m
Equity
NOK 2.0m
Est. value
NOK 20.5m

Financial health · 2024

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

Who owns EGON HAUGESUND AS?

NORREIN HOLDING AS
EGON HAUGESUND AS
NOK 36.0m rev. · NOK 5.2m profit

EGON HAUGESUND AS has 3 registered shareholders:

All shareholders and roles →

Which companies does EGON HAUGESUND AS own?

EGON HAUGESUND AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about EGON HAUGESUND AS

Who owns EGON HAUGESUND AS?

NORREIN HOLDING AS is the largest registered owner, with 38.0%.

What is the revenue of EGON HAUGESUND AS?

EGON HAUGESUND AS had revenue of NOK 36.0m in 2024.

Who is the general manager of EGON HAUGESUND AS?

Roy Ivan Tørresdal is registered as general manager of EGON HAUGESUND AS.

Where is EGON HAUGESUND AS based?

EGON HAUGESUND AS has its business address in Haugesund.

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.