BIZTRAC BETA
Other education activities

STRESSPROFESSORENE AS

Org. no. 920381782 Limited company (AS) Bergen Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 25,000
Operating profit NOK −55,000
Equity NOK 69,000
Incorporated 2018
Share capital NOK 30,000

Signals

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

STRESSPROFESSORENE AS is registered as a limited company in Bergen, Vestland with organisation number 920381782. The business is classified under other education activities (NACE 85.597). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Undervisning, veiledning, pedagogisk-psykologisk rådgivning, bedriftsrådgivning, kurs, foredrag, terapi og behandling og andre produkter/tjenester som naturlig hører til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 25,000 in revenue and NOK −55,000 in operating profit.

Key figures · 2025

Revenue
NOK 25,000
Operating profit
NOK −55,000
Equity
NOK 69,000
Est. value
NOK 57,000

Financial health · 2025

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

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

Who owns STRESSPROFESSORENE AS?

HEGE RANDI ERIKSEN
STRESSPROFESSORENE AS
NOK 25,000 rev. · NOK −55,000 profit

STRESSPROFESSORENE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about STRESSPROFESSORENE AS

Who owns STRESSPROFESSORENE AS?

HEGE RANDI ERIKSEN is the largest registered owner, with 66.7%.

What is the revenue of STRESSPROFESSORENE AS?

STRESSPROFESSORENE AS had revenue of NOK 25,000 in 2025.

Where is STRESSPROFESSORENE AS based?

STRESSPROFESSORENE AS has its business address in Søreidgrend.

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.