BIZTRAC BETA
Development of building projects

KINOTUNET HOLDING AS

Org. no. 930113964 Limited company (AS) Karmøy Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −25,000
Equity NOK −40,000
Incorporated 2022
Share capital NOK 30,000

Signals

4 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−40k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−25k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-04-14 Adresseendring registrert 2026-04-14.

KINOTUNET HOLDING AS is registered as a limited company in Karmøy, Rogaland with organisation number 930113964. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i andre virksomheter, samt alt hva som hører naturlig under dette.”.

Key figures · 2024

Operating profit
NOK −25,000
Equity
NOK −40,000

Financial health · 2024

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

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

Who owns KINOTUNET HOLDING AS?

SKUDE BYGG EIENDOM AS
KINOTUNET HOLDING AS
· NOK −25,000 profit

KINOTUNET HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does KINOTUNET HOLDING AS own?

KINOTUNET HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KINOTUNET HOLDING AS

Who owns KINOTUNET HOLDING AS?

SKUDE BYGG EIENDOM AS is the largest registered owner, with 66.7%.

Where is KINOTUNET HOLDING AS based?

KINOTUNET HOLDING AS has its business address in Skudeneshavn.

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.