BIZTRAC BETA
Other technical consultancy

INTCON AS

Org. no. 930828696 Limited company (AS) Askøy Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 4.3m
Operating profit NOK 69,000
Equity NOK −586,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−586k kr).

INTCON AS is registered as a limited company in Askøy, Vestland with organisation number 930828696. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge tjenester og varer innen energistyring, byggautomasjon og tavler og annet som naturlig sammenfaller med dette, samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.3m in revenue and NOK 69,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.3m
Operating profit
NOK 69,000
Equity
NOK −586,000
Est. value
NOK 354,000

Financial health · 2025

Liquidity
0.77
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-103.8%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns INTCON AS?

ANDREAS HAFSTAD HELLEM
INTCON AS
NOK 4.3m rev. · NOK 69,000 profit

INTCON AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about INTCON AS

Who owns INTCON AS?

ANDREAS HAFSTAD HELLEM is the largest registered owner, with 20.0%.

What is the revenue of INTCON AS?

INTCON AS had revenue of NOK 4.3m in 2025.

Who is the general manager of INTCON AS?

Kim Endre Danielsen Nordnes is registered as general manager of INTCON AS.

Where is INTCON AS based?

INTCON AS has its business address in Strusshamn.

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.