BIZTRAC BETA
Uoppgitt

KIMUSAN INVEST AS

Org. no. 827985422 Limited company (AS) Vestby Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −7,000
Equity NOK −16,000
Incorporated 2021
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−16k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−7k kr).

KIMUSAN INVEST AS is registered as a limited company in Vestby, Akershus with organisation number 827985422. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Forvaltning av eierinteresser og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −7,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −7,000
Equity
NOK −16,000

Financial health · 2025

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

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

Who owns KIMUSAN INVEST AS?

Kim Baumann Larsen
KIMUSAN INVEST AS
NOK 0 rev. · NOK −7,000 profit

KIMUSAN INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KIMUSAN INVEST AS own?

KIMUSAN INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KIMUSAN INVEST AS

Who owns KIMUSAN INVEST AS?

Kim Baumann Larsen is the largest registered owner, with 100.0%.

What is the revenue of KIMUSAN INVEST AS?

KIMUSAN INVEST AS had revenue of NOK 0 in 2025.

Where is KIMUSAN INVEST AS based?

KIMUSAN INVEST AS has its business address in Son.

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.