BIZTRAC BETA
Performing arts activities in music

KARGRO AS

Org. no. 999587976 Limited company (AS) Haugesund Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 97,000
Operating profit NOK 9,000
Equity NOK 179,000
Incorporated 2013
Share capital NOK 30,000

KARGRO AS is registered as a limited company in Haugesund, Rogaland with organisation number 999587976. The business is classified under performing arts activities in music (NACE 90.201). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Utøve, arrangere og komponere musikk, samt annet som er naturlig knyttet til virksomheten. Undervisning i musikk, intrumentalopplæring, samt annen undervisning som faller naturlig innunder dette. Utleie av musikkintrumenter og -utstyr, samt annet som er naturlig knyttet til virksomheten.”. The most recent filed accounts, for the 2024 financial year, show NOK 97,000 in revenue and NOK 9,000 in operating profit.

Key figures · 2024

Revenue
NOK 97,000
Operating profit
NOK 9,000
Equity
NOK 179,000
Est. value
NOK 140,000

Financial health · 2024

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

Who owns KARGRO AS?

KARL CHRISTIAN GRØNHAUG
KARGRO AS
NOK 97,000 rev. · NOK 9,000 profit

KARGRO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KARGRO AS

Who owns KARGRO AS?

KARL CHRISTIAN GRØNHAUG is the largest registered owner, with 100.0%.

What is the revenue of KARGRO AS?

KARGRO AS had revenue of NOK 97,000 in 2024.

Who is the general manager of KARGRO AS?

Karl Christian Grønhaug is registered as general manager of KARGRO AS.

Where is KARGRO AS based?

KARGRO AS has its business address in Haugesund.

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.