BIZTRAC BETA
Buying and selling of own real estate

CURA HOLDING AS

Org. no. 916309716 Limited company (AS) Skien Incorporated 2015 Active
Ownership graph ↗
Operating profit NOK −82,000
Equity NOK 114,000
Incorporated 2015
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−82k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

CURA HOLDING AS is registered as a limited company in Skien, Telemark with organisation number 916309716. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Salg, kjøp og utleie av eiendom, foredragsvirksomhet, veiledervirksomhet, konsulentvirksomhet, barnehagevirksomhet, barnevernsvirksomhet omsorgsvirksomhet og relaterte tjenester til dette.”.

Key figures · 2024

Operating profit
NOK −82,000
Equity
NOK 114,000
Est. value
NOK 104,000

Financial health · 2024

Liquidity
90.17
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
29.9%
Good
Equity as a share of total capital

Who owns CURA HOLDING AS?

TORFINN STAVE
CURA HOLDING AS
· NOK −82,000 profit

CURA HOLDING AS has 4 registered shareholders:

All shareholders and roles →

Which companies does CURA HOLDING AS own?

CURA HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about CURA HOLDING AS

Who owns CURA HOLDING AS?

TORFINN STAVE is the largest registered owner, with 25.0%.

Who is the general manager of CURA HOLDING AS?

Torfinn Stave is registered as general manager of CURA HOLDING AS.

Where is CURA HOLDING AS based?

CURA HOLDING AS has its business address in Skien.

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.