BIZTRAC BETA
Manufacture of soft drinks and bottled waters

PETPACK DRIKKER AS

Org. no. 918278338 Limited company (AS) Aurskog-Høland Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 181.6m
Operating profit NOK 24.6m
Equity NOK 50.9m
Incorporated 2016
Employees 38
Share capital NOK 2.0m

PETPACK DRIKKER AS is registered as a limited company in Aurskog-Høland, Akershus with organisation number 918278338. The business is classified under manufacture of soft drinks and bottled waters (NACE 11.070). The company was incorporated in 2016 and has 38 registered employees. Registered share capital is NOK 2.0m, divided into 2021334 shares. The company's stated purpose is: “Produksjon, salg og distribusjon, eventuelt eksport, av naturlig og søtet mineralvann, samt alt hva derved står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 181.6m in revenue and NOK 24.6m in operating profit.

Key figures · 2024

Revenue
NOK 181.6m
Operating profit
NOK 24.6m
Equity
NOK 50.9m
Est. value
NOK 112.9m

Financial health · 2024

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

Who owns PETPACK DRIKKER AS?

TELEMARK KILDEVANN HOLDING AS
PETPACK DRIKKER AS
NOK 181.6m rev. · NOK 24.6m profit

PETPACK DRIKKER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PETPACK DRIKKER AS

Who owns PETPACK DRIKKER AS?

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

What is the revenue of PETPACK DRIKKER AS?

PETPACK DRIKKER AS had revenue of NOK 181.6m in 2024.

Who is the general manager of PETPACK DRIKKER AS?

Lars Bjørn Bunæs is registered as general manager of PETPACK DRIKKER AS.

Where is PETPACK DRIKKER AS based?

PETPACK DRIKKER AS has its business address in Aurskog.

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.