BIZTRAC BETA
Computer programming activities

INDICON AS

Org. no. 920220169 Limited company (AS) Bergen Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −23,000
Equity NOK 1.8m
Incorporated 2017
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−23k kr).

INDICON AS is registered as a limited company in Bergen, Vestland with organisation number 920220169. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Å utvikle IT-løsninger og drive konsulentvirksomhet, samt investeringsvirksomhet herunder å eie aksjer i andre selskaper samt alt som naturlig hører med.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −23,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −23,000
Equity
NOK 1.8m
Est. value
NOK 3.3m

Financial health · 2024

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

Who owns INDICON AS?

HILDE ULVIK HORDNES
INDICON AS
NOK 0 rev. · NOK −23,000 profit

INDICON AS has 1 registered shareholder:

All shareholders and roles →

Which companies does INDICON AS own?

INDICON AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about INDICON AS

Who owns INDICON AS?

HILDE ULVIK HORDNES is the largest registered owner, with 100.0%.

What is the revenue of INDICON AS?

INDICON AS had revenue of NOK 0 in 2024.

Who is the general manager of INDICON AS?

Hilde Ulvik Hordnes is registered as general manager of INDICON AS.

Where is INDICON AS based?

INDICON AS has its business address in Bergen.

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.