BIZTRAC BETA
Industrial product and fashion design activities

JUVATIND AS

Org. no. 927270951 Limited company (AS) Ålesund Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 870,000
Operating profit NOK −385,000
Equity NOK −464,000
Incorporated 2021
Share capital NOK 60,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−464k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−385k kr).

JUVATIND AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 927270951. The business is classified under industrial product and fashion design activities (NACE 74.110). The company was incorporated in 2021. Registered share capital is NOK 60,000, divided into 6000 shares. The company's stated purpose is: “Industridesign, produktdesign og annen teknisk designvirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 870,000 in revenue and NOK −385,000 in operating profit.

Key figures · 2024

Revenue
NOK 870,000
Operating profit
NOK −385,000
Equity
NOK −464,000

Financial health · 2024

Liquidity
3.14
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-19.3%
Weak
Equity as a share of total capital

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

Who owns JUVATIND AS?

IKR HOLDING AS
JUVATIND AS
NOK 870,000 rev. · NOK −385,000 profit

JUVATIND AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about JUVATIND AS

Who owns JUVATIND AS?

IKR HOLDING AS is the largest registered owner, with 25.0%.

What is the revenue of JUVATIND AS?

JUVATIND AS had revenue of NOK 870,000 in 2024.

Who is the general manager of JUVATIND AS?

Alexander Asprem is registered as general manager of JUVATIND AS.

Where is JUVATIND AS based?

JUVATIND AS has its business address in Ålesund.

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.