BIZTRAC BETA
OCBK AS is registered as “Bankrupt” with the Brønnøysund Register Centre.
Computer programming activities

OCBK AS

Org. no. 932444054 Limited company (AS) Oslo Incorporated 2023 Bankrupt
Ownership graph ↗
Revenue 2024 NOK 653,000
Operating profit NOK −54,000
Equity NOK −35,000
Incorporated 2023
Share capital NOK 30,000

Signals

4 flags
  • Konkurs Selskapet er registrert konkurs i Enhetsregisteret.
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−35k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−54k kr).
  • Nylig endring 2026-08-08 Konkurs registrert 2026-08-08.

OCBK AS is registered as a limited company in Oslo, Oslo with organisation number 932444054. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Salg av tjenester innen visuell kommunikasjon.”. The most recent filed accounts, for the 2024 financial year, show NOK 653,000 in revenue and NOK −54,000 in operating profit.

Key figures · 2024

Revenue
NOK 653,000
Operating profit
NOK −54,000
Equity
NOK −35,000

Financial health · 2024

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

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

Who owns OCBK AS?

OLE-CHRISTIAN BERGHEIM KJELSTAD
OCBK AS
NOK 653,000 rev. · NOK −54,000 profit

OCBK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OCBK AS

Who owns OCBK AS?

OLE-CHRISTIAN BERGHEIM KJELSTAD is the largest registered owner, with 100.0%.

What is the revenue of OCBK AS?

OCBK AS had revenue of NOK 653,000 in 2024.

Where is OCBK AS based?

OCBK 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.