BIZTRAC BETA
Intermediation service activities for business support service activities n.e.c.

BJOKO HOLDING AS

Org. no. 825291822 Limited company (AS) Trondheim Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −12,000
Equity NOK 516,000
Incorporated 2020
Share capital NOK 30,000

Signals

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

BJOKO HOLDING AS is registered as a limited company in Trondheim, Trøndelag with organisation number 825291822. The business is classified under intermediation service activities for business support service activities n.e.c. (NACE 82.400). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Deltakelse økonomisk eller på annen måte delta i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −12,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −12,000
Equity
NOK 516,000
Est. value
NOK 2.5m

Financial health · 2025

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

Who owns BJOKO HOLDING AS?

BJØRN JONNY KOTTUM
BJOKO HOLDING AS
NOK 0 rev. · NOK −12,000 profit

BJOKO HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BJOKO HOLDING AS own?

BJOKO HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BJOKO HOLDING AS

Who owns BJOKO HOLDING AS?

BJØRN JONNY KOTTUM is the largest registered owner, with 100.0%.

What is the revenue of BJOKO HOLDING AS?

BJOKO HOLDING AS had revenue of NOK 0 in 2025.

Where is BJOKO HOLDING AS based?

BJOKO HOLDING AS has its business address in Heimdal.

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.