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

KA-CHING INVEST AS

Org. no. 916957874 Limited company (AS) Bergen Incorporated 2016 Active
Ownership graph ↗
Operating profit NOK 10,000
Equity NOK 3.2m
Incorporated 2016
Share capital NOK 30,000

KA-CHING INVEST AS is registered as a limited company in Bergen, Vestland with organisation number 916957874. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Levere tjenester innen investeringsvirksomhet og konsulentvirksomhet og andre tjenester/produkter som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”.

Key figures · 2025

Operating profit
NOK 10,000
Equity
NOK 3.2m
Est. value
NOK 1.8m

Financial health · 2025

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

Who owns KA-CHING INVEST AS?

MARIT LOSNEDAL
KA-CHING INVEST AS
· NOK 10,000 profit

KA-CHING INVEST AS has 2 registered shareholders:

All shareholders and roles →

Which companies does KA-CHING INVEST AS own?

KA-CHING INVEST AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about KA-CHING INVEST AS

Who owns KA-CHING INVEST AS?

MARIT LOSNEDAL is the largest registered owner, with 60.0%.

Who is the general manager of KA-CHING INVEST AS?

Marit Losnedal is registered as general manager of KA-CHING INVEST AS.

Where is KA-CHING INVEST AS based?

KA-CHING INVEST AS has its business address in Rådal.

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.