BIZTRAC BETA
Uoppgitt

OJIAKU CAPITAL AS

Org. no. 936705154 Limited company (AS) Bærum Incorporated 2025 Active
Ownership graph ↗
Operating profit NOK −7,000
Equity NOK 24,000
Incorporated 2025
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−6k kr).
  • Nystiftet selskap Selskapet ble stiftet 2025-11-25.

OJIAKU CAPITAL AS is registered as a limited company in Bærum, Akershus with organisation number 936705154. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”.

Key figures · 2025

Operating profit
NOK −7,000
Equity
NOK 24,000
Est. value
NOK 28,000

Financial health · 2025

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

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

Who owns OJIAKU CAPITAL AS?

MICHAEL UCHE OJIAKU
OJIAKU CAPITAL AS
· NOK −7,000 profit

OJIAKU CAPITAL AS has 1 registered shareholder:

All shareholders and roles →

Which companies does OJIAKU CAPITAL AS own?

OJIAKU CAPITAL AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about OJIAKU CAPITAL AS

Who owns OJIAKU CAPITAL AS?

MICHAEL UCHE OJIAKU is the largest registered owner, with 100.0%.

Who is the general manager of OJIAKU CAPITAL AS?

Michael Uche Ojiaku is registered as general manager of OJIAKU CAPITAL AS.

Where is OJIAKU CAPITAL AS based?

OJIAKU CAPITAL AS has its business address in Lysaker.

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.