biztrac. BETA
COMPANY REGISTER PROFILE
936256295 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Hairdressing and barber activities

VINKEL FRISØR AS

Org. no. 936256295 Limited company (AS) Drammen Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −16,000
Equity NOK 14,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−16k kr).

VINKEL FRISØR AS is registered as a limited company in Drammen, Buskerud with organisation number 936256295. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Drift av frisørsalong og naturlig tilknyttet virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −16,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −16,000
Equity
NOK 14,000
Est. value
NOK 19,000

Financial health · 2025

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

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

Who owns VINKEL FRISØR AS?

VINKEL FRISØR AS
NOK 0 rev. · NOK −16,000 profit

VINKEL FRISØR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VINKEL FRISØR AS

Who owns VINKEL FRISØR AS?

Lida Mehr is the largest registered owner, with 100.0%.

What is the revenue of VINKEL FRISØR AS?

VINKEL FRISØR AS had revenue of NOK 0 in 2025.

Who is the general manager of VINKEL FRISØR AS?

Lida Mehr is registered as general manager of VINKEL FRISØR AS.

Where is VINKEL FRISØR AS based?

VINKEL FRISØR 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.