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

STUDIO BEVE AS

Org. no. 932941619 Limited company (AS) Trondheim Incorporated 2023 Active
Revenue 2025 NOK 655,000
Operating profit NOK −26,000
Equity NOK −89,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

STUDIO BEVE AS is registered as a limited company in Trondheim, Trøndelag with organisation number 932941619. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Skjønnhetspleie, barber.”. The most recent filed accounts, for the 2025 financial year, show NOK 655,000 in revenue and NOK −26,000 in operating profit.

Key figures · 2025

Revenue
NOK 655,000
▼ −4 %
Operating profit
NOK −26,000
▼ −712 %
Equity
NOK −89,000
▼ −52 %

Financial health · 2025

Liquidity
0.51
Weak
Current assets ÷ current liabilities
Profitability
-19.1%
Not satisfactory
Return on total assets
Solidity
-57.9%
Weak
Equity as a share of total capital

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

Who owns STUDIO BEVE AS?

STUDIO BEVE AS
NOK 655,000 rev. · NOK −26,000 profit

STUDIO BEVE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STUDIO BEVE AS

Who owns STUDIO BEVE AS?

Evelin Bence is the largest registered owner, with 100.0%.

What is the revenue of STUDIO BEVE AS?

STUDIO BEVE AS had revenue of NOK 655,000 in 2025.

Who is the general manager of STUDIO BEVE AS?

Evelin Bence is registered as general manager of STUDIO BEVE AS.

Where is STUDIO BEVE AS based?

STUDIO BEVE AS has its business address in Trondheim.

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.