BIZTRAC BETA
Other processing and preserving of fruit and vegetables

NORREK DYPFRYS AS

Org. no. 910228609 Limited company (AS) Larvik Incorporated 1977 Active
Ownership graph ↗
Revenue 2024 NOK 453.5m
Operating profit NOK 43.2m
Equity NOK 147.5m
Incorporated 1977
Employees 87
Share capital NOK 11.6m

NORREK DYPFRYS AS is registered as a limited company in Larvik, Vestfold with organisation number 910228609. The business is classified under other processing and preserving of fruit and vegetables (NACE 10.390). The company was incorporated in 1977 and has 87 registered employees. Registered share capital is NOK 11.6m, divided into 10000 shares. The company's stated purpose is: “Produksjon, blanding og nedfrysing av grønnsaker, bær og frukt, samt det som står i forbindelse med dette, herunder deltagelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 453.5m in revenue and NOK 43.2m in operating profit.

Key figures · 2024

Revenue
NOK 453.5m
Operating profit
NOK 43.2m
Equity
NOK 147.5m
Est. value
NOK 247.1m

Financial health · 2024

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

Who owns NORREK DYPFRYS AS?

T. MANVIK HOLDING AS
NORREK DYPFRYS AS
NOK 453.5m rev. · NOK 43.2m profit

NORREK DYPFRYS AS has 6 registered shareholders:

All shareholders and roles →

Frequently asked questions about NORREK DYPFRYS AS

Who owns NORREK DYPFRYS AS?

T. MANVIK HOLDING AS is the largest registered owner, with 40.0%.

What is the revenue of NORREK DYPFRYS AS?

NORREK DYPFRYS AS had revenue of NOK 453.5m in 2024.

Who is the general manager of NORREK DYPFRYS AS?

Janne Stenehjem is registered as general manager of NORREK DYPFRYS AS.

Where is NORREK DYPFRYS AS based?

NORREK DYPFRYS AS has its business address in Larvik.

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.