BIZTRAC BETA
Industrial product and fashion design activities

ICBRG AS

Org. no. 932084775 Limited company (AS) Kongsberg Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 500,000
Operating profit NOK −1.7m
Equity NOK 2.9m
Incorporated 2023
Share capital NOK 35,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,7 mill kr).

ICBRG AS is registered as a limited company in Kongsberg, Buskerud with organisation number 932084775. The business is classified under industrial product and fashion design activities (NACE 74.110). The company was incorporated in 2023. Registered share capital is NOK 35,000, divided into 1160277 shares. The company's stated purpose is: “Utvikling og salg av teknologiprodukter for elbil og andre batteridrevne transportmidler.”. The most recent filed accounts, for the 2024 financial year, show NOK 500,000 in revenue and NOK −1.7m in operating profit.

Key figures · 2024

Revenue
NOK 500,000
Operating profit
NOK −1.7m
Equity
NOK 2.9m
Est. value
NOK 1.9m

Financial health · 2024

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

Who owns ICBRG AS?

REVILL CAPITAL MANAGEMENT AS
ICBRG AS
NOK 500,000 rev. · NOK −1.7m profit

ICBRG AS has 20+ registered shareholders:

All shareholders and roles →

Which companies does ICBRG AS own?

ICBRG AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about ICBRG AS

Who owns ICBRG AS?

REVILL CAPITAL MANAGEMENT AS is the largest registered owner, with 48.3%.

What is the revenue of ICBRG AS?

ICBRG AS had revenue of NOK 500,000 in 2024.

Who is the general manager of ICBRG AS?

Morten Revill is registered as general manager of ICBRG AS.

Where is ICBRG AS based?

ICBRG AS has its business address in Kongsberg.

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.