biztrac. BETA
COMPANY REGISTER PROFILE
931710192 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

NIRAKAR AS

Org. no. 931710192 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Operating profit NOK −2,000
Equity NOK 44,000
Incorporated 2023
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−2k kr).
  • Nylig endring 2026-04-23 Adresseendring registrert 2026-04-23.

NIRAKAR AS is registered as a limited company in Oslo, Oslo with organisation number 931710192. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. 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 −2,000
▲ +45 %
Equity
NOK 44,000
▲ +2 %
Est. value
NOK 52,000

Financial health · 2025

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

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

Who owns NIRAKAR AS?

NIRAKAR AS
· NOK −2,000 profit

NIRAKAR AS has 1 registered shareholder:

All shareholders and roles →

Which companies does NIRAKAR AS own?

NIRAKAR AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about NIRAKAR AS

Who owns NIRAKAR AS?

Biplav Karna is the largest registered owner, with 100.0%.

Who is the general manager of NIRAKAR AS?

Biplav Karna is registered as general manager of NIRAKAR AS.

Where is NIRAKAR AS based?

NIRAKAR 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.