BIZTRAC BETA
COMPANY REGISTER PROFILE
979226942 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Hairdressing and barber activities

STANGE FRISØR AS

Org. no. 979226942 Limited company (AS) Stange Incorporated 1997 Active
Ownership graph ↗
Revenue 2025 NOK 317,000
Operating profit NOK 62,000
Equity NOK 81,000
Incorporated 1997
Share capital NOK 30,000

STANGE FRISØR AS is registered as a limited company in Stange, Innlandet with organisation number 979226942. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 1997. Registered share capital is NOK 30,000, divided into 500 shares. The company's stated purpose is: “Drive frisørvirksomhet samt utleie av lokaler og driftsmidler og annet som naturlig hører til.”. The most recent filed accounts, for the 2025 financial year, show NOK 317,000 in revenue and NOK 62,000 in operating profit.

Key figures · 2025

Revenue
NOK 317,000
Operating profit
NOK 62,000
Equity
NOK 81,000
Est. value
NOK 246,000

Financial health · 2025

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

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

Who owns STANGE FRISØR AS?

GINE HAGEN NYLAND
STANGE FRISØR AS
NOK 317,000 rev. · NOK 62,000 profit

STANGE FRISØR AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about STANGE FRISØR AS

Who owns STANGE FRISØR AS?

GINE HAGEN NYLAND is the largest registered owner, with 50.0%.

What is the revenue of STANGE FRISØR AS?

STANGE FRISØR AS had revenue of NOK 317,000 in 2025.

Who is the general manager of STANGE FRISØR AS?

Kamilla Stenseth is registered as general manager of STANGE FRISØR AS.

Where is STANGE FRISØR AS based?

STANGE FRISØR AS has its business address in Stange.

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.