BIZTRAC BETA
General medical practice activities

PRECURO AS

Org. no. 911889625 Limited company (AS) Harstad Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −46,000
Equity NOK 227,000
Incorporated 2013
Share capital NOK 49,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−46k kr).

PRECURO AS is registered as a limited company in Harstad, Troms with organisation number 911889625. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2013. Registered share capital is NOK 49,000, divided into 1973 shares. The company's stated purpose is: “Medisinsk virksomhet, salg av medisinske produkter og tjenester og annen relatert virksomhet, samt investeringer i andre selskaper med lignende formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −46,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −46,000
Equity
NOK 227,000
Est. value
NOK 351,000

Financial health · 2024

Liquidity
1.02
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
54.3%
Very good
Equity as a share of total capital

Who owns PRECURO AS?

ACURO AS
PRECURO AS
NOK 0 rev. · NOK −46,000 profit

PRECURO AS has 4 registered shareholders:

All shareholders and roles →

Which companies does PRECURO AS own?

PRECURO AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about PRECURO AS

Who owns PRECURO AS?

ACURO AS is the largest registered owner, with 78.8%.

What is the revenue of PRECURO AS?

PRECURO AS had revenue of NOK 0 in 2024.

Who is the general manager of PRECURO AS?

Marius Christensen is registered as general manager of PRECURO AS.

Where is PRECURO AS based?

PRECURO AS has its business address in Harstad.

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.