BIZTRAC BETA
Uoppgitt

KUTOPPEN INVEST AS

Org. no. 927429918 Limited company (AS) Nærøysund Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −3,000
Equity NOK 10,000
Incorporated 2021
Share capital NOK 36,000

Signals

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

KUTOPPEN INVEST AS is registered as a limited company in Nærøysund, Trøndelag with organisation number 927429918. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 36,000, divided into 600 shares. The company's stated purpose is: “Forvaltning av eierinteresser og det som måtte stå i den forbindelse, herunder eierskap av aksjer i andre selskaper, fast eiendom og eiendeler for øvrig.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −3,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −3,000
Equity
NOK 10,000
Est. value
NOK 11,000

Financial health · 2025

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

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

Who owns KUTOPPEN INVEST AS?

KIM ULSUND
KUTOPPEN INVEST AS
NOK 0 rev. · NOK −3,000 profit

KUTOPPEN INVEST AS has 2 registered shareholders:

All shareholders and roles →

Which companies does KUTOPPEN INVEST AS own?

KUTOPPEN INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KUTOPPEN INVEST AS

Who owns KUTOPPEN INVEST AS?

KIM ULSUND is the largest registered owner, with 60.0%.

What is the revenue of KUTOPPEN INVEST AS?

KUTOPPEN INVEST AS had revenue of NOK 0 in 2025.

Where is KUTOPPEN INVEST AS based?

KUTOPPEN INVEST AS has its business address in Rørvik.

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.