BIZTRAC BETA
Production of meat and poultry meat products

HOLE KJØTT AS

Org. no. 933485730 Limited company (AS) Ålesund Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 20.2m
Operating profit NOK 1.5m
Equity NOK 740,000
Incorporated 2024
Employees 13
Share capital NOK 100,000

HOLE KJØTT AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 933485730. The business is classified under production of meat and poultry meat products (NACE 10.130). The company was incorporated in 2024 and has 13 registered employees. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Foredling og omsetning av kjøtt, ferdigmat og delikatesser.”. The most recent filed accounts, for the 2025 financial year, show NOK 20.2m in revenue and NOK 1.5m in operating profit.

Key figures · 2025

Revenue
NOK 20.2m
Operating profit
NOK 1.5m
Equity
NOK 740,000
Est. value
NOK 6.0m

Financial health · 2025

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

Who owns HOLE KJØTT AS?

ODLA HOLDING AS
HOLE KJØTT AS
NOK 20.2m rev. · NOK 1.5m profit

HOLE KJØTT AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HOLE KJØTT AS own?

HOLE KJØTT AS holds a stake in 1 company:

See the full ownership structure →

Group structure

HOLE KJØTT AS er morselskap for 1 datterselskap:

Frequently asked questions about HOLE KJØTT AS

Who owns HOLE KJØTT AS?

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

What is the revenue of HOLE KJØTT AS?

HOLE KJØTT AS had revenue of NOK 20.2m in 2025.

Who is the general manager of HOLE KJØTT AS?

Oddbjørn Hole is registered as general manager of HOLE KJØTT AS.

Where is HOLE KJØTT AS based?

HOLE KJØTT AS has its business address in Ålesund.

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.