BIZTRAC BETA
Hairdressing and barber activities

KLIPP MEG AS

Org. no. 928634612 Limited company (AS) Drammen Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 1.8m
Operating profit NOK 15,000
Equity NOK −49,000
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−49k kr).

KLIPP MEG AS is registered as a limited company in Drammen, Buskerud with organisation number 928634612. 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 300 shares. The company's stated purpose is: “Frisør og skjønnhetspleie/velvære.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.8m in revenue and NOK 15,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.8m
Operating profit
NOK 15,000
Equity
NOK −49,000
Est. value
NOK 114,000

Financial health · 2024

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

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

Who owns KLIPP MEG AS?

ADRIANA ANNA KUPISZ
KLIPP MEG AS
NOK 1.8m rev. · NOK 15,000 profit

KLIPP MEG AS has 4 registered shareholders:

All shareholders and roles →

Which companies does KLIPP MEG AS own?

KLIPP MEG AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KLIPP MEG AS

Who owns KLIPP MEG AS?

ADRIANA ANNA KUPISZ is the largest registered owner, with 35.0%.

What is the revenue of KLIPP MEG AS?

KLIPP MEG AS had revenue of NOK 1.8m in 2024.

Who is the general manager of KLIPP MEG AS?

Lise-Mette Pettersen is registered as general manager of KLIPP MEG AS.

Where is KLIPP MEG AS based?

KLIPP MEG AS has its business address in Drammen.

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.