BIZTRAC BETA
Hairdressing and barber activities

VIBEKES HÅRPLEIE AS

Org. no. 919982454 Limited company (AS) Holmestrand Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 929,000
Operating profit NOK 41,000
Equity NOK 527,000
Incorporated 2017
Share capital NOK 50,000

Signals

1 flags
  • Nylig endring 2026-07-29 Adresseendring registrert 2026-07-29.

VIBEKES HÅRPLEIE AS is registered as a limited company in Holmestrand, Vestfold with organisation number 919982454. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2017. Registered share capital is NOK 50,000, divided into 100 shares. The company's stated purpose is: “Frisørtjenester og salg av produkter som naturlig tilhører dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 929,000 in revenue and NOK 41,000 in operating profit.

Key figures · 2025

Revenue
NOK 929,000
Operating profit
NOK 41,000
Equity
NOK 527,000
Est. value
NOK 480,000

Financial health · 2025

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

Who owns VIBEKES HÅRPLEIE AS?

VIBEKE WASSENGEN ANDERSEN
VIBEKES HÅRPLEIE AS
NOK 929,000 rev. · NOK 41,000 profit

VIBEKES HÅRPLEIE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VIBEKES HÅRPLEIE AS

Who owns VIBEKES HÅRPLEIE AS?

VIBEKE WASSENGEN ANDERSEN is the largest registered owner, with 100.0%.

What is the revenue of VIBEKES HÅRPLEIE AS?

VIBEKES HÅRPLEIE AS had revenue of NOK 929,000 in 2025.

Who is the general manager of VIBEKES HÅRPLEIE AS?

Vibeke Wassengen Andersen is registered as general manager of VIBEKES HÅRPLEIE AS.

Where is VIBEKES HÅRPLEIE AS based?

VIBEKES HÅRPLEIE AS has its business address in Hof.

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.