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

STUDIO HM FRISØR AS

Org. no. 979959095 Limited company (AS) Porsgrunn Incorporated 1998 Active
Revenue 2025 NOK 2.6m
Operating profit NOK 169,000
Equity NOK 421,000
Incorporated 1998
Share capital NOK 100,000

STUDIO HM FRISØR AS is registered as a limited company in Porsgrunn, Telemark with organisation number 979959095. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 1998. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Frisørsalong og det som naturlig hører herunder, samt deltagelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.6m in revenue and NOK 169,000 in operating profit.

Former names: WENCHES HÅRSALONG AS

Key figures · 2025

Revenue
NOK 2.6m
▲ +3 %
Operating profit
NOK 169,000
▲ +171 %
Equity
NOK 421,000
▲ +46 %
Est. value
NOK 721,000

Financial health · 2025

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

Who owns STUDIO HM FRISØR AS?

STUDIO HM FRISØR AS
NOK 2.6m rev. · NOK 169,000 profit

STUDIO HM FRISØR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STUDIO HM FRISØR AS

Who owns STUDIO HM FRISØR AS?

Heidi Terese Moen is the largest registered owner, with 100.0%.

What is the revenue of STUDIO HM FRISØR AS?

STUDIO HM FRISØR AS had revenue of NOK 2.6m in 2025.

Who is the general manager of STUDIO HM FRISØR AS?

Heidi Terese Moen is registered as general manager of STUDIO HM FRISØR AS.

Where is STUDIO HM FRISØR AS based?

STUDIO HM FRISØR 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.