BIZTRAC BETA
All other professional, scientific and technical activities n.e.c.

INCONTROL AS

Org. no. 986086013 Limited company (AS) Bergen Incorporated 2003 Active
Ownership graph ↗
Revenue 2024 NOK 6.9m
Operating profit NOK 2.1m
Equity NOK 3.6m
Incorporated 2003
Share capital NOK 504,000

INCONTROL AS is registered as a limited company in Bergen, Vestland with organisation number 986086013. The business is classified under all other professional, scientific and technical activities n.e.c. (NACE 74.990). The company was incorporated in 2003. Registered share capital is NOK 504,000, divided into 17700 shares. The company's stated purpose is: “Selskapets formål er å drive forretningsvirksomhet rettet hovedsakelig mot instrumentering og automasjon innen energisektoren både i innland og utland. I tillegg skal selskapet kunne drive utleievirksomhet og annen virksomhet med økonomisk formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.9m in revenue and NOK 2.1m in operating profit.

Key figures · 2024

Revenue
NOK 6.9m
Operating profit
NOK 2.1m
Equity
NOK 3.6m
Est. value
NOK 9.3m

Financial health · 2024

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

Who owns INCONTROL AS?

CALIN IOAN RADU
INCONTROL AS
NOK 6.9m rev. · NOK 2.1m profit

INCONTROL AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about INCONTROL AS

Who owns INCONTROL AS?

CALIN IOAN RADU is the largest registered owner, with 51.0%.

What is the revenue of INCONTROL AS?

INCONTROL AS had revenue of NOK 6.9m in 2024.

Who is the general manager of INCONTROL AS?

Calin Ioan Radu is registered as general manager of INCONTROL AS.

Where is INCONTROL AS based?

INCONTROL AS has its business address in Kokstad.

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.