BIZTRAC BETA
Activities of employment placement agencies

CURA BEMANNING AS

Org. no. 933849899 Limited company (AS) Hole Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −9,000
Equity NOK 14,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

CURA BEMANNING AS is registered as a limited company in Hole, Buskerud with organisation number 933849899. The business is classified under activities of employment placement agencies (NACE 78.100). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Rådgivning og annen bistand i tilknytning til rekruttering og bemanningstjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −9,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −9,000
Equity
NOK 14,000
Est. value
NOK 20,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 CURA BEMANNING AS?

BØVIKEN HOLDING AB
CURA BEMANNING AS
NOK 0 rev. · NOK −9,000 profit

CURA BEMANNING AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about CURA BEMANNING AS

Who owns CURA BEMANNING AS?

BØVIKEN HOLDING AB is the largest registered owner, with 45.0%.

What is the revenue of CURA BEMANNING AS?

CURA BEMANNING AS had revenue of NOK 0 in 2025.

Who is the general manager of CURA BEMANNING AS?

Satheesh Kumar Varadharajan is registered as general manager of CURA BEMANNING AS.

Where is CURA BEMANNING AS based?

CURA BEMANNING AS has its business address in Krokkleiva.

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.