BIZTRAC BETA
Hairdressing and barber activities

OLD GRUMPY BARBER AS

Org. no. 934639405 Limited company (AS) Hamar Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 1.6m
Operating profit NOK 513,000
Equity NOK 442,000
Incorporated 2024
Share capital NOK 30,000

OLD GRUMPY BARBER AS is registered as a limited company in Hamar, Innlandet with organisation number 934639405. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Drift av barber og frisørsalong, salg av produkter med tilknytning til dette, foruten forvaltning av selskapets kapital og ressurser i form av investeringer i eiendom, verdipapirer og andre finansielle instrumenter.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.6m in revenue and NOK 513,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.6m
Operating profit
NOK 513,000
Equity
NOK 442,000
Est. value
NOK 1.7m

Financial health · 2025

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

Who owns OLD GRUMPY BARBER AS?

THOR ÅGE OLSBY
OLD GRUMPY BARBER AS
NOK 1.6m rev. · NOK 513,000 profit

OLD GRUMPY BARBER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OLD GRUMPY BARBER AS

Who owns OLD GRUMPY BARBER AS?

THOR ÅGE OLSBY is the largest registered owner, with 100.0%.

What is the revenue of OLD GRUMPY BARBER AS?

OLD GRUMPY BARBER AS had revenue of NOK 1.6m in 2024.

Who is the general manager of OLD GRUMPY BARBER AS?

Thor Åge Olsby is registered as general manager of OLD GRUMPY BARBER AS.

Where is OLD GRUMPY BARBER AS based?

OLD GRUMPY BARBER 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.