BIZTRAC BETA
Processing and preserving of poultry meat

HÅ KYLLING AS

Org. no. 918026711 Limited company (AS) Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 381.9m
Operating profit NOK 13.4m
Equity NOK 29.6m
Incorporated 2016
Employees 83
Share capital NOK 2.0m

HÅ KYLLING AS is registered as a limited company in Hå, Rogaland with organisation number 918026711. The business is classified under processing and preserving of poultry meat (NACE 10.120). The company was incorporated in 2016 and has 83 registered employees. Registered share capital is NOK 2.0m, divided into 1000 shares. The company's stated purpose is: “Skjæring av slaktede kyllinger, herunder pakking og ekspedering og det som ellers står naturlig i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 381.9m in revenue and NOK 13.4m in operating profit.

Key figures · 2024

Revenue
NOK 381.9m
Operating profit
NOK 13.4m
Equity
NOK 29.6m
Est. value
NOK 64.2m

Financial health · 2024

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

Who owns HÅ KYLLING AS?

ÅE INVEST AS
HÅ KYLLING AS
NOK 381.9m rev. · NOK 13.4m profit

HÅ KYLLING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does HÅ KYLLING AS own?

HÅ KYLLING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HÅ KYLLING AS

Who owns HÅ KYLLING AS?

ÅE INVEST AS is the largest registered owner, with 50.0%.

What is the revenue of HÅ KYLLING AS?

HÅ KYLLING AS had revenue of NOK 381.9m in 2024.

Who is the general manager of HÅ KYLLING AS?

Terje Haavardsholm is registered as general manager of HÅ KYLLING AS.

Where is HÅ KYLLING AS based?

HÅ KYLLING AS has its business address in Nærbø.

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.