BIZTRAC BETA
Business and other management consultancy activities

KAPAMARA INVEST AS

Org. no. 917750696 Limited company (AS) Hamar Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 230,000
Operating profit NOK −75,000
Equity NOK 4.6m
Incorporated 2016
Share capital NOK 40,000

Signals

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

KAPAMARA INVEST AS is registered as a limited company in Hamar, Innlandet with organisation number 917750696. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2016. Registered share capital is NOK 40,000, divided into 1 shares. The company's stated purpose is: “Konsulenttjenester innen finansiell strategi, samt investere i andre selskap og eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 230,000 in revenue and NOK −75,000 in operating profit.

Key figures · 2025

Revenue
NOK 230,000
Operating profit
NOK −75,000
Equity
NOK 4.6m
Est. value
NOK 2.5m

Financial health · 2025

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

Who owns KAPAMARA INVEST AS?

VEGARD SÆTEN
KAPAMARA INVEST AS
NOK 230,000 rev. · NOK −75,000 profit

KAPAMARA INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KAPAMARA INVEST AS own?

KAPAMARA INVEST AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about KAPAMARA INVEST AS

Who owns KAPAMARA INVEST AS?

VEGARD SÆTEN is the largest registered owner, with 100.0%.

What is the revenue of KAPAMARA INVEST AS?

KAPAMARA INVEST AS had revenue of NOK 230,000 in 2025.

Where is KAPAMARA INVEST AS based?

KAPAMARA INVEST AS has its business address in Hamar.

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.