BIZTRAC BETA
Other technical consultancy

CAPALOS AS

Org. no. 917584125 Limited company (AS) Stavanger Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 702,000
Operating profit NOK −13,000
Equity NOK 6.2m
Incorporated 2016
Share capital NOK 30,000

Signals

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

CAPALOS AS is registered as a limited company in Stavanger, Rogaland with organisation number 917584125. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Salg av konsulenttjenester, kjøp, utleie og salg fast eiendom, samt aksjeinvesteringer og deltakelse i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 702,000 in revenue and NOK −13,000 in operating profit.

Key figures · 2025

Revenue
NOK 702,000
Operating profit
NOK −13,000
Equity
NOK 6.2m
Est. value
NOK 7.6m

Financial health · 2025

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

Who owns CAPALOS AS?

TOR EGIL ROLFSEN
CAPALOS AS
NOK 702,000 rev. · NOK −13,000 profit

CAPALOS AS has 1 registered shareholder:

All shareholders and roles →

Which companies does CAPALOS AS own?

CAPALOS AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about CAPALOS AS

Who owns CAPALOS AS?

TOR EGIL ROLFSEN is the largest registered owner, with 100.0%.

What is the revenue of CAPALOS AS?

CAPALOS AS had revenue of NOK 702,000 in 2025.

Who is the general manager of CAPALOS AS?

Tor Egil Rolfsen is registered as general manager of CAPALOS AS.

Where is CAPALOS AS based?

CAPALOS AS has its business address in Hafrsfjord.

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.