BIZTRAC BETA
Activities of psychologists and psychotherapists, except medical doctors

PSYKOLOG TROND HAUG AS

Org. no. 885180442 Limited company (AS) Stjørdal Incorporated 2002 Active
Ownership graph ↗
Revenue 2024 NOK 1.4m
Operating profit NOK 485,000
Equity NOK 788,000
Incorporated 2002
Share capital NOK 100,000

PSYKOLOG TROND HAUG AS is registered as a limited company in Stjørdal, Trøndelag with organisation number 885180442. The business is classified under activities of psychologists and psychotherapists, except medical doctors (NACE 86.930). The company was incorporated in 2002. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Psykologitjenester, konsulenttjenester inne fagområdet, samt å kunne delta i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.4m in revenue and NOK 485,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.4m
Operating profit
NOK 485,000
Equity
NOK 788,000
Est. value
NOK 2.2m

Financial health · 2024

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

Who owns PSYKOLOG TROND HAUG AS?

TROND HAUG
PSYKOLOG TROND HAUG AS
NOK 1.4m rev. · NOK 485,000 profit

PSYKOLOG TROND HAUG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PSYKOLOG TROND HAUG AS

Who owns PSYKOLOG TROND HAUG AS?

TROND HAUG is the largest registered owner, with 100.0%.

What is the revenue of PSYKOLOG TROND HAUG AS?

PSYKOLOG TROND HAUG AS had revenue of NOK 1.4m in 2024.

Who is the general manager of PSYKOLOG TROND HAUG AS?

Alex Armann Haug Bulling is registered as general manager of PSYKOLOG TROND HAUG AS.

Where is PSYKOLOG TROND HAUG AS based?

PSYKOLOG TROND HAUG AS has its business address in Stjørdal.

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.