BIZTRAC BETA
COMPANY REGISTER PROFILE
928977773 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Refrigeration installation, heat pump installation and installation of fireplaces

PROCO SERVICES AB

Org. no. 928977773 Norwegian division of foreign business enterprise (NUF) Active
Ownership graph ↗
Revenue 2025 NOK 762,000
Operating profit NOK −212,000
Equity NOK −299,000

Signals

3 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−299k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−212k kr).
  • Nylig endring 2026-04-13 Adresseendring registrert 2026-04-13.

PROCO SERVICES AB is registered as a norwegian division of foreign business enterprise with organisation number 928977773. The business is classified under refrigeration installation, heat pump installation and installation of fireplaces (NACE 43.222). The most recent filed accounts, for the 2025 financial year, show NOK 762,000 in revenue and NOK −212,000 in operating profit.

Key figures · 2025

Revenue
NOK 762,000
Operating profit
NOK −212,000
Equity
NOK −299,000

Financial health · 2025

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

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

Who owns PROCO SERVICES AB?

No shareholders are registered for PROCO SERVICES AB in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about PROCO SERVICES AB

What is the revenue of PROCO SERVICES AB?

PROCO SERVICES AB had revenue of NOK 762,000 in 2025.

Who is the general manager of PROCO SERVICES AB?

Jørn Fjeldavlie is registered as general manager of PROCO SERVICES AB.

Where is PROCO SERVICES AB based?

PROCO SERVICES AB has its business address in Se-126 30 Hägersten.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

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