BIZTRAC BETA
Industrial product and fashion design activities

DESIPRO AS

Org. no. 914754402 Limited company (AS) Lillestrøm Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 356,000
Operating profit NOK −35,000
Equity NOK −394,000
Incorporated 2014
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−394k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−35k kr).

DESIPRO AS is registered as a limited company in Lillestrøm, Akershus with organisation number 914754402. The business is classified under industrial product and fashion design activities (NACE 74.110). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Produksjon og salg av design i små serier.”. The most recent filed accounts, for the 2025 financial year, show NOK 356,000 in revenue and NOK −35,000 in operating profit.

Key figures · 2025

Revenue
NOK 356,000
Operating profit
NOK −35,000
Equity
NOK −394,000

Financial health · 2024

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

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

Who owns DESIPRO AS?

Ola Severin Skytteren
DESIPRO AS
NOK 356,000 rev. · NOK −35,000 profit

DESIPRO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DESIPRO AS

Who owns DESIPRO AS?

Ola Severin Skytteren is the largest registered owner, with 100.0%.

What is the revenue of DESIPRO AS?

DESIPRO AS had revenue of NOK 356,000 in 2025.

Who is the general manager of DESIPRO AS?

Ola Severin Skytteren is registered as general manager of DESIPRO AS.

Where is DESIPRO AS based?

DESIPRO AS has its business address in Fetsund.

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.