BIZTRAC BETA
Manufacture of other fabricated metal products n.e.c.

INVISIBLE CONNECTIONS AS

Org. no. 992435194 Limited company (AS) Rauma Incorporated 2008 Active
Ownership graph ↗
Revenue 2025 NOK 42.5m
Operating profit NOK 215,000
Equity NOK 16.7m
Incorporated 2008
Employees 13
Share capital NOK 2.5m

INVISIBLE CONNECTIONS AS is registered as a limited company in Rauma, Møre og Romsdal with organisation number 992435194. The business is classified under manufacture of other fabricated metal products n.e.c. (NACE 25.990). The company was incorporated in 2008 and has 13 registered employees. Registered share capital is NOK 2.5m, divided into 2500 shares. The company's stated purpose is: “Å drive mekanisk verksted, herunder produksjon og salg av maskiner og utstyr, samt alt som står i forbindelse med dette, herunder deltakelse i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 42.5m in revenue and NOK 215,000 in operating profit.

Key figures · 2025

Revenue
NOK 42.5m
Operating profit
NOK 215,000
Equity
NOK 16.7m
Est. value
NOK 11.4m

Financial health · 2025

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

Who owns INVISIBLE CONNECTIONS AS?

SVEIN BERG HOLDING AS
INVISIBLE CONNECTIONS AS
NOK 42.5m rev. · NOK 215,000 profit

INVISIBLE CONNECTIONS AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about INVISIBLE CONNECTIONS AS

Who owns INVISIBLE CONNECTIONS AS?

SVEIN BERG HOLDING AS is the largest registered owner, with 65.0%.

What is the revenue of INVISIBLE CONNECTIONS AS?

INVISIBLE CONNECTIONS AS had revenue of NOK 42.5m in 2025.

Where is INVISIBLE CONNECTIONS AS based?

INVISIBLE CONNECTIONS AS has its business address in Åndalsnes.

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.