BIZTRAC BETA
Hairdressing and barber activities

NEXUS FRISØR AS

Org. no. 918510753 Limited company (AS) Tønsberg Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −102,000
Equity NOK −74,000
Incorporated 2017
Share capital NOK 30,000

Signals

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

NEXUS FRISØR AS is registered as a limited company in Tønsberg, Vestfold with organisation number 918510753. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Frisering og annen skjønnhetspleie.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −102,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −102,000
Equity
NOK −74,000

Financial health · 2024

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

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

Who owns NEXUS FRISØR AS?

JORUNN MARIT VALEBJØRG ØRPEN
NEXUS FRISØR AS
NOK 0 rev. · NOK −102,000 profit

NEXUS FRISØR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NEXUS FRISØR AS

Who owns NEXUS FRISØR AS?

JORUNN MARIT VALEBJØRG ØRPEN is the largest registered owner, with 100.0%.

What is the revenue of NEXUS FRISØR AS?

NEXUS FRISØR AS had revenue of NOK 0 in 2024.

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

Jorunn Marit Valebjørg Ørpen is registered as general manager of NEXUS FRISØR AS.

Where is NEXUS FRISØR AS based?

NEXUS FRISØR AS has its business address in Tønsberg.

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.