BIZTRAC BETA
Wholesale of clothing and footwear

PROFIL DESIGN NORGE AS

Org. no. 967333700 Limited company (AS) Asker Incorporated 1993 Active
Ownership graph ↗
Revenue 2024 NOK 22.4m
Operating profit NOK 1.2m
Equity NOK 1.8m
Incorporated 1993
Employees 5
Share capital NOK 302,000

PROFIL DESIGN NORGE AS is registered as a limited company in Asker, Akershus with organisation number 967333700. The business is classified under wholesale of clothing and footwear (NACE 46.420). The company was incorporated in 1993 and has 5 registered employees. Registered share capital is NOK 302,000, divided into 302 shares. The company's stated purpose is: “Produksjon-, handel-, agentur-, konsulent- virksomhet, deltagelse i andre selskaper og annen forretningsvirksomhet forøvrig med økonomisk formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 22.4m in revenue and NOK 1.2m in operating profit.

Key figures · 2024

Revenue
NOK 22.4m
Operating profit
NOK 1.2m
Equity
NOK 1.8m
Est. value
NOK 5.7m

Financial health · 2025

Liquidity
1.38
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
27.4%
Good
Equity as a share of total capital

Who owns PROFIL DESIGN NORGE AS?

GEIR SYLEN
PROFIL DESIGN NORGE AS
NOK 22.4m rev. · NOK 1.2m profit

PROFIL DESIGN NORGE AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about PROFIL DESIGN NORGE AS

Who owns PROFIL DESIGN NORGE AS?

GEIR SYLEN is the largest registered owner, with 25.2%.

What is the revenue of PROFIL DESIGN NORGE AS?

PROFIL DESIGN NORGE AS had revenue of NOK 22.4m in 2024.

Who is the general manager of PROFIL DESIGN NORGE AS?

Stig Skjølås is registered as general manager of PROFIL DESIGN NORGE AS.

Where is PROFIL DESIGN NORGE AS based?

PROFIL DESIGN NORGE AS has its business address in Hvalstad.

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.