BIZTRAC BETA
Wholesale of household, office and shop furniture, carpets and lighting equipment

KOSDESIGN HOLDING AS

Org. no. 925892211 Limited company (AS) Ulstein Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −13,000
Equity NOK 21,000
Incorporated 2020
Share capital NOK 60,000

Signals

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

KOSDESIGN HOLDING AS is registered as a limited company in Ulstein, Møre og Romsdal with organisation number 925892211. The business is classified under wholesale of household, office and shop furniture, carpets and lighting equipment (NACE 46.470). The company was incorporated in 2020. Registered share capital is NOK 60,000, divided into 2000 shares. The company's stated purpose is: “Investere i andre selskap, verdipapirer og fast eiendom samt konsulentvirksomhet.”.

Key figures · 2025

Operating profit
NOK −13,000
Equity
NOK 21,000
Est. value
NOK 26,000

Financial health · 2024

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

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

Who owns KOSDESIGN HOLDING AS?

ROY ARE STORNES
KOSDESIGN HOLDING AS
· NOK −13,000 profit

KOSDESIGN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KOSDESIGN HOLDING AS own?

KOSDESIGN HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about KOSDESIGN HOLDING AS

Who owns KOSDESIGN HOLDING AS?

ROY ARE STORNES is the largest registered owner, with 100.0%.

Who is the general manager of KOSDESIGN HOLDING AS?

Roy Are Stornes is registered as general manager of KOSDESIGN HOLDING AS.

Where is KOSDESIGN HOLDING AS based?

KOSDESIGN HOLDING AS has its business address in Ulsteinvik.

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.