BIZTRAC BETA
Other technical consultancy

IBCON AS

Org. no. 921432437 Limited company (AS) Bærum Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 221,000
Operating profit NOK −328,000
Equity NOK 2.6m
Incorporated 2018
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−328k kr).

IBCON AS is registered as a limited company in Bærum, Akershus with organisation number 921432437. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Drive konsulent virksomhet innen logistikk, energi og generell ledelse. Samt å forvalte de verdier som genereres igjennom daglig virksomhet som investering i næringsvirksomhet, herunder aksjer og andeler, samt deltagelse i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 221,000 in revenue and NOK −328,000 in operating profit.

Key figures · 2025

Revenue
NOK 221,000
Operating profit
NOK −328,000
Equity
NOK 2.6m
Est. value
NOK 1.5m

Financial health · 2025

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

Who owns IBCON AS?

IRIS BENTE FRØYBU
IBCON AS
NOK 221,000 rev. · NOK −328,000 profit

IBCON AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about IBCON AS

Who owns IBCON AS?

IRIS BENTE FRØYBU is the largest registered owner, with 49.7%.

What is the revenue of IBCON AS?

IBCON AS had revenue of NOK 221,000 in 2025.

Who is the general manager of IBCON AS?

Iris Bente Frøybu is registered as general manager of IBCON AS.

Where is IBCON AS based?

IBCON AS has its business address in Kolsås.

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.