BIZTRAC BETA
Industrial product and fashion design activities

TE CONNECTIVITY NORGE AS

Org. no. 942897375 Limited company (AS) Bærum Incorporated 1987 Active
Ownership graph ↗
Revenue 2024 NOK 91.1m
Operating profit NOK 56.1m
Equity NOK 63.2m
Incorporated 1987
Employees 6
Share capital NOK 2.4m

TE CONNECTIVITY NORGE AS is registered as a limited company in Bærum, Akershus with organisation number 942897375. The business is classified under industrial product and fashion design activities (NACE 74.110). The company was incorporated in 1987 and has 6 registered employees. Registered share capital is NOK 2.4m, divided into 235 shares. The company's stated purpose is: “Produksjon, handel og agenturvirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 91.1m in revenue and NOK 56.1m in operating profit.

Key figures · 2024

Revenue
NOK 91.1m
Operating profit
NOK 56.1m
Equity
NOK 63.2m
Est. value
NOK 213.5m

Financial health · 2024

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

Who owns TE CONNECTIVITY NORGE AS?

TYCO ELECTRONICS SCHWEIZ HOLDING
TE CONNECTIVITY NORGE AS
NOK 91.1m rev. · NOK 56.1m profit

TE CONNECTIVITY NORGE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TE CONNECTIVITY NORGE AS

Who owns TE CONNECTIVITY NORGE AS?

TYCO ELECTRONICS SCHWEIZ HOLDING is the largest registered owner, with 100.0%.

What is the revenue of TE CONNECTIVITY NORGE AS?

TE CONNECTIVITY NORGE AS had revenue of NOK 91.1m in 2024.

Who is the general manager of TE CONNECTIVITY NORGE AS?

Malin Maria Tränk is registered as general manager of TE CONNECTIVITY NORGE AS.

Where is TE CONNECTIVITY NORGE AS based?

TE CONNECTIVITY NORGE AS has its business address in Fornebu.

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.