BIZTRAC BETA
Retail sale of cultural and recreational goods n.e.c.

KUNSTARK AS

Org. no. 927219204 Limited company (AS) Stord Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 540,000
Operating profit NOK −51,000
Equity NOK 126,000
Incorporated 2021
Share capital NOK 30,000

Signals

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

KUNSTARK AS is registered as a limited company in Stord, Vestland with organisation number 927219204. The business is classified under retail sale of cultural and recreational goods n.e.c. (NACE 47.690). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Distribusjon og salg av kunstverk. Utvikling og salg av digital kunst, NFT. Kunstproduksjon, trykking og produksjon av annen visuell kunst. Samt annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 540,000 in revenue and NOK −51,000 in operating profit.

Key figures · 2024

Revenue
NOK 540,000
Operating profit
NOK −51,000
Equity
NOK 126,000
Est. value
NOK 235,000

Financial health · 2024

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

Who owns KUNSTARK AS?

MARTIN DYRSETH
KUNSTARK AS
NOK 540,000 rev. · NOK −51,000 profit

KUNSTARK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KUNSTARK AS

Who owns KUNSTARK AS?

MARTIN DYRSETH is the largest registered owner, with 100.0%.

What is the revenue of KUNSTARK AS?

KUNSTARK AS had revenue of NOK 540,000 in 2024.

Who is the general manager of KUNSTARK AS?

Martin Dyrseth is registered as general manager of KUNSTARK AS.

Where is KUNSTARK AS based?

KUNSTARK AS has its business address in Stord.

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.