BIZTRAC BETA
Hairdressing and barber activities

MAREN KVERNMO FRISØR AS

Org. no. 929836057 Limited company (AS) Ringerike Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 497,000
Operating profit NOK −2,000
Equity NOK −74,000
Incorporated 2022
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−74k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−2k kr).

MAREN KVERNMO FRISØR AS is registered as a limited company in Ringerike, Buskerud with organisation number 929836057. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 10 shares. The company's stated purpose is: “Frisørvirksomhet, salg av varer og annet som hører til.”. The most recent filed accounts, for the 2025 financial year, show NOK 497,000 in revenue and NOK −2,000 in operating profit.

Key figures · 2025

Revenue
NOK 497,000
Operating profit
NOK −2,000
Equity
NOK −74,000

Financial health · 2025

Liquidity
1.08
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-100.0%
Weak
Equity as a share of total capital

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

Who owns MAREN KVERNMO FRISØR AS?

MAREN KVERNMO EILERTSEN
MAREN KVERNMO FRISØR AS
NOK 497,000 rev. · NOK −2,000 profit

MAREN KVERNMO FRISØR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MAREN KVERNMO FRISØR AS

Who owns MAREN KVERNMO FRISØR AS?

MAREN KVERNMO EILERTSEN is the largest registered owner, with 100.0%.

What is the revenue of MAREN KVERNMO FRISØR AS?

MAREN KVERNMO FRISØR AS had revenue of NOK 497,000 in 2025.

Where is MAREN KVERNMO FRISØR AS based?

MAREN KVERNMO FRISØR AS has its business address in Hønefoss.

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.