BIZTRAC BETA
Sports activities n.e.c.

KROW BIDCO AS

Org. no. 930773891 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −39,000
Equity NOK −6.4m
Incorporated 2023
Share capital NOK 350,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−6,4 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−39k kr).

KROW BIDCO AS is registered as a limited company in Oslo, Oslo with organisation number 930773891. The business is classified under sports activities n.e.c. (NACE 93.190). The company was incorporated in 2023. Registered share capital is NOK 350,000, divided into 30000 shares. The company's stated purpose is: “Investering i aksjer og andre eiendeler i andre selskaper og foretak, samt all virksomhet som hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −39,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −39,000
Equity
NOK −6.4m

Financial health · 2024

Liquidity
0.69
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-5.4%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns KROW BIDCO AS?

JALLEAR HOLDINGS LTD
KROW BIDCO AS
NOK 0 rev. · NOK −39,000 profit

KROW BIDCO AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KROW BIDCO AS own?

KROW BIDCO AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KROW BIDCO AS

Who owns KROW BIDCO AS?

JALLEAR HOLDINGS LTD is the largest registered owner, with 100.0%.

What is the revenue of KROW BIDCO AS?

KROW BIDCO AS had revenue of NOK 0 in 2024.

Where is KROW BIDCO AS based?

KROW BIDCO 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.