BIZTRAC BETA
Activities of psychologists and psychotherapists, except medical doctors

EGGE PSYKOLOGSERVICE AS

Org. no. 929567382 Limited company (AS) Steinkjer Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 2.7m
Operating profit NOK 1.0m
Equity NOK 898,000
Incorporated 2022
Share capital NOK 30,000

EGGE PSYKOLOGSERVICE AS is registered as a limited company in Steinkjer, Trøndelag with organisation number 929567382. The business is classified under activities of psychologists and psychotherapists, except medical doctors (NACE 86.930). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Psykologtjenester. Behandling av psykiske lidelser ved samtalebehandling.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.7m in revenue and NOK 1.0m in operating profit.

Key figures · 2025

Revenue
NOK 2.7m
Operating profit
NOK 1.0m
Equity
NOK 898,000
Est. value
NOK 4.0m

Financial health · 2024

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

Who owns EGGE PSYKOLOGSERVICE AS?

ESPEN EGELAND VALSETH
EGGE PSYKOLOGSERVICE AS
NOK 2.7m rev. · NOK 1.0m profit

EGGE PSYKOLOGSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EGGE PSYKOLOGSERVICE AS

Who owns EGGE PSYKOLOGSERVICE AS?

ESPEN EGELAND VALSETH is the largest registered owner, with 100.0%.

What is the revenue of EGGE PSYKOLOGSERVICE AS?

EGGE PSYKOLOGSERVICE AS had revenue of NOK 2.7m in 2025.

Who is the general manager of EGGE PSYKOLOGSERVICE AS?

Espen Egeland Valseth is registered as general manager of EGGE PSYKOLOGSERVICE AS.

Where is EGGE PSYKOLOGSERVICE AS based?

EGGE PSYKOLOGSERVICE AS has its business address in Steinkjer.

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.