BIZTRAC BETA
Activities of collection agencies and credit bureaus

ROPO AS

Org. no. 913876725 Limited company (AS) Sandefjord Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 44.3m
Operating profit NOK −19.8m
Equity NOK 10.1m
Incorporated 2014
Employees 47
Share capital NOK 410,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−19,8 mill kr).
  • Nylig endring 2026-07-14 Aksjekapital registrert 2026-07-14.

ROPO AS is registered as a limited company in Sandefjord, Vestfold with organisation number 913876725. The business is classified under activities of collection agencies and credit bureaus (NACE 82.910). The company was incorporated in 2014 and has 47 registered employees. Registered share capital is NOK 410,000, divided into 342000 shares. The company's stated purpose is: “Fordringsadministrasjon og inkasso samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 44.3m in revenue and NOK −19.8m in operating profit.

Key figures · 2024

Revenue
NOK 44.3m
Operating profit
NOK −19.8m
Equity
NOK 10.1m
Est. value
NOK 29.9m

Financial health · 2024

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

Who owns ROPO AS?

ROPO HOLDING NORWAY AS
ROPO AS
NOK 44.3m rev. · NOK −19.8m profit

ROPO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ROPO AS

Who owns ROPO AS?

ROPO HOLDING NORWAY AS is the largest registered owner, with 100.0%.

What is the revenue of ROPO AS?

ROPO AS had revenue of NOK 44.3m in 2024.

Who is the general manager of ROPO AS?

Trung Minh Tran is registered as general manager of ROPO AS.

Where is ROPO AS based?

ROPO AS has its business address in Sandefjord.

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.