BIZTRAC BETA
Repair and maintenance of machinery

KOUT HOLDING AS

Org. no. 930598844 Limited company (AS) Tana Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −12,000
Equity NOK 55,000
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−12k kr).

KOUT HOLDING AS is registered as a limited company in Tana, Finnmark with organisation number 930598844. The business is classified under repair and maintenance of machinery (NACE 33.120). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Kjøp, besittelse og salg av aksjer i andre selskaper samt andre verdipapirer, og annen virksomhet som hører naturlig sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −12,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −12,000
Equity
NOK 55,000
Est. value
NOK 65,000

Financial health · 2024

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

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

Who owns KOUT HOLDING AS?

MATHIAS KOLLSTRØM
KOUT HOLDING AS
NOK 0 rev. · NOK −12,000 profit

KOUT HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does KOUT HOLDING AS own?

KOUT HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KOUT HOLDING AS

Who owns KOUT HOLDING AS?

MATHIAS KOLLSTRØM is the largest registered owner, with 50.0%.

What is the revenue of KOUT HOLDING AS?

KOUT HOLDING AS had revenue of NOK 0 in 2024.

Where is KOUT HOLDING AS based?

KOUT HOLDING AS has its business address in Tana.

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.