BIZTRAC BETA
Hairdressing and barber activities

BARBERSHOP OASEN AS

Org. no. 919497041 Limited company (AS) Haugesund Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 2.2m
Operating profit NOK 213,000
Equity NOK 502,000
Incorporated 2017
Share capital NOK 30,000

BARBERSHOP OASEN AS is registered as a limited company in Haugesund, Rogaland with organisation number 919497041. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Barberer samt frisør og andre behandlingstjenester innen faget, samt kjøp og salg av produkter der tilhørende, samt hva hermed står i forbindelse, herunder å delta i andre foretak som driver tilsvarende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.2m in revenue and NOK 213,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.2m
Operating profit
NOK 213,000
Equity
NOK 502,000
Est. value
NOK 1.1m

Financial health · 2024

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

Who owns BARBERSHOP OASEN AS?

SINISA MARJANOVIC
BARBERSHOP OASEN AS
NOK 2.2m rev. · NOK 213,000 profit

BARBERSHOP OASEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BARBERSHOP OASEN AS

Who owns BARBERSHOP OASEN AS?

SINISA MARJANOVIC is the largest registered owner, with 100.0%.

What is the revenue of BARBERSHOP OASEN AS?

BARBERSHOP OASEN AS had revenue of NOK 2.2m in 2024.

Who is the general manager of BARBERSHOP OASEN AS?

Sinisa Marjanovic is registered as general manager of BARBERSHOP OASEN AS.

Where is BARBERSHOP OASEN AS based?

BARBERSHOP OASEN AS has its business address in Haugesund.

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.