biztrac. BETA
COMPANY REGISTER PROFILE
931948687 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Hairdressing and barber activities

STYLISH CUTZ AS

Org. no. 931948687 Limited company (AS) Fredrikstad Incorporated 2023 Active
Revenue 2025 NOK 3.0m
Operating profit NOK −69,000
Equity NOK −375,000
Incorporated 2023
Employees 5
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−375k kr).

STYLISH CUTZ AS is registered as a limited company in Fredrikstad, Østfold with organisation number 931948687. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2023 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Frisering og annen skjønnhetspleie. Kjøp og salg av varer og tjenester i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.0m in revenue and NOK −69,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.0m
▼ −6 %
Operating profit
NOK −69,000
▲ +77 %
Equity
NOK −375,000
▼ −23 %

Financial health · 2025

Liquidity
0.43
Not satisfactory
Current assets ÷ current liabilities
Profitability
-15.4%
Not satisfactory
Return on total assets
Solidity
-133.6%
Weak
Equity as a share of total capital

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

Who owns STYLISH CUTZ AS?

STYLISH CUTZ AS
NOK 3.0m rev. · NOK −69,000 profit

STYLISH CUTZ AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STYLISH CUTZ AS

Who owns STYLISH CUTZ AS?

Aram Khurshid Othman is the largest registered owner, with 100.0%.

What is the revenue of STYLISH CUTZ AS?

STYLISH CUTZ AS had revenue of NOK 3.0m in 2025.

Where is STYLISH CUTZ AS based?

STYLISH CUTZ AS has its business address in Rolvsøy.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.