BIZTRAC BETA
Graphic design and visual communication activities

KOMMUNIKASJONSHUSET INVOLVE! AS

Org. no. 930500615 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −20,000
Equity NOK 5.9m
Incorporated 2022
Share capital NOK 3.0m

Signals

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

KOMMUNIKASJONSHUSET INVOLVE! AS is registered as a limited company in Oslo, Oslo with organisation number 930500615. The business is classified under graphic design and visual communication activities (NACE 74.120). The company was incorporated in 2022. Registered share capital is NOK 3.0m, divided into 10000 shares. The company's stated purpose is: “Eie aksjer og andeler i andre selskaper og dertil tilhørende aktivitet som holdingselskap.”.

Key figures · 2024

Operating profit
NOK −20,000
Equity
NOK 5.9m
Est. value
NOK 9.6m

Financial health · 2024

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

Who owns KOMMUNIKASJONSHUSET INVOLVE! AS?

INVOLVE! HOLDING AS
KOMMUNIKASJONSHUSET INVOLVE! AS
· NOK −20,000 profit

KOMMUNIKASJONSHUSET INVOLVE! AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KOMMUNIKASJONSHUSET INVOLVE! AS own?

KOMMUNIKASJONSHUSET INVOLVE! AS holds stakes in 7 companies:

See the full ownership structure →

Frequently asked questions about KOMMUNIKASJONSHUSET INVOLVE! AS

Who owns KOMMUNIKASJONSHUSET INVOLVE! AS?

INVOLVE! HOLDING AS is the largest registered owner, with 100.0%.

Who is the general manager of KOMMUNIKASJONSHUSET INVOLVE! AS?

Karl Johan Bjerge is registered as general manager of KOMMUNIKASJONSHUSET INVOLVE! AS.

Where is KOMMUNIKASJONSHUSET INVOLVE! AS based?

KOMMUNIKASJONSHUSET INVOLVE! AS has its business address in Oslo.

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.