BIZTRAC BETA
Hairdressing and barber activities

CUT'N GO HAMAR AS

Org. no. 923015248 Limited company (AS) Hamar Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 3.3m
Operating profit NOK −125,000
Equity NOK 41,000
Incorporated 2019
Employees 6
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−125k kr).

CUT'N GO HAMAR AS is registered as a limited company in Hamar, Innlandet with organisation number 923015248. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2019 and has 6 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Hårpleie og annen skjønnhetspleie.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.3m in revenue and NOK −125,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.3m
Operating profit
NOK −125,000
Equity
NOK 41,000
Est. value
NOK 2.3m

Financial health · 2024

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

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

Who owns CUT'N GO HAMAR AS?

VERDIER GRUPPEN AS
CUT'N GO HAMAR AS
NOK 3.3m rev. · NOK −125,000 profit

CUT'N GO HAMAR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about CUT'N GO HAMAR AS

Who owns CUT'N GO HAMAR AS?

VERDIER GRUPPEN AS is the largest registered owner, with 100.0%.

What is the revenue of CUT'N GO HAMAR AS?

CUT'N GO HAMAR AS had revenue of NOK 3.3m in 2024.

Who is the general manager of CUT'N GO HAMAR AS?

Glenn-Erik Kolloen is registered as general manager of CUT'N GO HAMAR AS.

Where is CUT'N GO HAMAR AS based?

CUT'N GO HAMAR AS has its business address in Hamar.

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.