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

AFRO CUTZ AS

Org. no. 835407802 Limited company (AS) Porsgrunn Incorporated 2025 Active
Revenue 2025 NOK 142,000
Operating profit NOK −156,000
Equity NOK −91,000
Incorporated 2025
Share capital NOK 30,000

Signals

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

AFRO CUTZ AS is registered as a limited company in Porsgrunn, Telemark with organisation number 835407802. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Å drive virksomhet innen frisørfaget og deltagelse i andre lignende selskaper i samme bransje.”. The most recent filed accounts, for the 2025 financial year, show NOK 142,000 in revenue and NOK −156,000 in operating profit.

Former names: LETT FRISØR AS

Key figures · 2025

Revenue
NOK 142,000
Operating profit
NOK −156,000
Equity
NOK −91,000

Financial health · 2025

Liquidity
2.06
Very good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
43.5%
Weak
Equity as a share of total capital

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

Who owns AFRO CUTZ AS?

AFRO CUTZ AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about AFRO CUTZ AS

Who owns AFRO CUTZ AS?

Matusala Solomon Tewelde is the largest registered owner, with 34.0%.

What is the revenue of AFRO CUTZ AS?

AFRO CUTZ AS had revenue of NOK 142,000 in 2025.

Who is the general manager of AFRO CUTZ AS?

Matusala Solomon Tewelde is registered as general manager of AFRO CUTZ AS.

Where is AFRO CUTZ AS based?

AFRO CUTZ AS has its business address in Porsgrunn.

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.