BIZTRAC BETA
Wholesale of other intermediate products

TETRA PAK NORGE AS

Org. no. 914797853 Limited company (AS) Bærum Incorporated 1958 Active
Ownership graph ↗
Revenue 2024 NOK 505.5m
Operating profit NOK 8.1m
Equity NOK 16.0m
Incorporated 1958
Employees 19
Share capital NOK 5.6m

TETRA PAK NORGE AS is registered as a limited company in Bærum, Akershus with organisation number 914797853. The business is classified under wholesale of other intermediate products (NACE 46.860). The company was incorporated in 1958 and has 19 registered employees. Registered share capital is NOK 5.6m. The company's stated purpose is: “HAndel og hva dermed står i forbindelse, herunder deltagelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 505.5m in revenue and NOK 8.1m in operating profit.

Key figures · 2024

Revenue
NOK 505.5m
Operating profit
NOK 8.1m
Equity
NOK 16.0m
Est. value
NOK 39.6m

Financial health · 2024

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

Who owns TETRA PAK NORGE AS?

TETRA LAVAL INTERNATIONAL S.A
TETRA PAK NORGE AS
NOK 505.5m rev. · NOK 8.1m profit

TETRA PAK NORGE AS has 1 registered shareholder:

All shareholders and roles →

Group structure

TETRA PAK NORGE AS er morselskap for 1 datterselskap:

Frequently asked questions about TETRA PAK NORGE AS

Who owns TETRA PAK NORGE AS?

TETRA LAVAL INTERNATIONAL S.A is the largest registered owner, with 100.0%.

What is the revenue of TETRA PAK NORGE AS?

TETRA PAK NORGE AS had revenue of NOK 505.5m in 2024.

Who is the general manager of TETRA PAK NORGE AS?

Katrin Helen Margareta Andersson is registered as general manager of TETRA PAK NORGE AS.

Where is TETRA PAK NORGE AS based?

TETRA PAK NORGE AS has its business address in Lysaker.

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.