BIZTRAC BETA
Industrial product and fashion design activities

EIDESIGN AS

Org. no. 918428712 Limited company (AS) Rauma Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 511,000
Operating profit NOK 39,000
Equity NOK 80,000
Incorporated 2017
Share capital NOK 30,000

EIDESIGN AS is registered as a limited company in Rauma, Møre og Romsdal with organisation number 918428712. The business is classified under industrial product and fashion design activities (NACE 74.110). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Tilby og forestå produktutvikling, teknisk problemløsing, industridesign, 3D-modellering med rendering og simulering, prototyping, modellbygging, produksjonsunderlag, illustrasjoner og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 511,000 in revenue and NOK 39,000 in operating profit.

Key figures · 2025

Revenue
NOK 511,000
Operating profit
NOK 39,000
Equity
NOK 80,000
Est. value
NOK 245,000

Financial health · 2025

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

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

Who owns EIDESIGN AS?

ØYSTEIN EIDET
EIDESIGN AS
NOK 511,000 rev. · NOK 39,000 profit

EIDESIGN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EIDESIGN AS

Who owns EIDESIGN AS?

ØYSTEIN EIDET is the largest registered owner, with 100.0%.

What is the revenue of EIDESIGN AS?

EIDESIGN AS had revenue of NOK 511,000 in 2025.

Who is the general manager of EIDESIGN AS?

Øystein Eidet is registered as general manager of EIDESIGN AS.

Where is EIDESIGN AS based?

EIDESIGN AS has its business address in Åndalsnes.

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.