BIZTRAC BETA
Activities of employment placement agencies

CAPUS BERGEN AS

Org. no. 918672710 Limited company (AS) Bergen Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 3.1m
Operating profit NOK 257,000
Equity NOK 334,000
Incorporated 2017
Share capital NOK 30,000

CAPUS BERGEN AS is registered as a limited company in Bergen, Vestland with organisation number 918672710. The business is classified under activities of employment placement agencies (NACE 78.100). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Rekruttering av ledere, styremedlemmer og spesialister. Rådgiving, opplæring og utvikling av virksomheter, styrer, ledelse, personal og organisasjoner. Kurs og seminarer og personlig utvikling. Deltagelse i andre selskap med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.1m in revenue and NOK 257,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.1m
Operating profit
NOK 257,000
Equity
NOK 334,000
Est. value
NOK 1.3m

Financial health · 2025

Liquidity
1.60
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
37.5%
Good
Equity as a share of total capital

Who owns CAPUS BERGEN AS?

HR GRUPPEN CAPUS AS
CAPUS BERGEN AS
NOK 3.1m rev. · NOK 257,000 profit

CAPUS BERGEN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about CAPUS BERGEN AS

Who owns CAPUS BERGEN AS?

HR GRUPPEN CAPUS AS is the largest registered owner, with 51.0%.

What is the revenue of CAPUS BERGEN AS?

CAPUS BERGEN AS had revenue of NOK 3.1m in 2025.

Who is the general manager of CAPUS BERGEN AS?

Per Jorem is registered as general manager of CAPUS BERGEN AS.

Where is CAPUS BERGEN AS based?

CAPUS BERGEN AS has its business address in Bergen.

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.