BIZTRAC BETA
COMPANY REGISTER PROFILE
816138302 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Other captive investment companies

EXACTPAY CAPITAL MANAGEMENT AS

Org. no. 816138302 Limited company (AS) Trondheim Incorporated 2015 Active
Ownership graph ↗
Operating profit NOK −966,000
Equity NOK −759,000
Incorporated 2015
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−759k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−966k kr).

EXACTPAY CAPITAL MANAGEMENT AS is registered as a limited company in Trondheim, Trøndelag with organisation number 816138302. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 300000 shares. The company's stated purpose is: “Eie aksjer, samt investeringer i virksomheter av enhver art.”.

Key figures · 2024

Operating profit
NOK −966,000
Equity
NOK −759,000

Financial health · 2024

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

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

Who owns EXACTPAY CAPITAL MANAGEMENT AS?

FRODE REINSBAKK
EXACTPAY CAPITAL MANAGEMENT AS
· NOK −966,000 profit

EXACTPAY CAPITAL MANAGEMENT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EXACTPAY CAPITAL MANAGEMENT AS

Who owns EXACTPAY CAPITAL MANAGEMENT AS?

FRODE REINSBAKK is the largest registered owner, with 100.0%.

Who is the general manager of EXACTPAY CAPITAL MANAGEMENT AS?

Frode Reinsbakk is registered as general manager of EXACTPAY CAPITAL MANAGEMENT AS.

Where is EXACTPAY CAPITAL MANAGEMENT AS based?

EXACTPAY CAPITAL MANAGEMENT AS has its business address in Trondheim.

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.