BIZTRAC BETA
Other health services

IL VEILEDNING OG TERAPI AS

Org. no. 930283142 Limited company (AS) Stjørdal Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 172,000
Operating profit NOK 21,000
Equity NOK 7,000
Incorporated 2022
Share capital NOK 30,000

IL VEILEDNING OG TERAPI AS is registered as a limited company in Stjørdal, Trøndelag with organisation number 930283142. The business is classified under other health services (NACE 86.993). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 10 shares. The company's stated purpose is: “Veiledning og terapitjenester. Konsultasjonstjenester.”. The most recent filed accounts, for the 2024 financial year, show NOK 172,000 in revenue and NOK 21,000 in operating profit.

Key figures · 2024

Revenue
NOK 172,000
Operating profit
NOK 21,000
Equity
NOK 7,000
Est. value
NOK 102,000

Financial health · 2024

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

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

Who owns IL VEILEDNING OG TERAPI AS?

INGVIL ØIESTAD LØVIK
IL VEILEDNING OG TERAPI AS
NOK 172,000 rev. · NOK 21,000 profit

IL VEILEDNING OG TERAPI AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about IL VEILEDNING OG TERAPI AS

Who owns IL VEILEDNING OG TERAPI AS?

INGVIL ØIESTAD LØVIK is the largest registered owner, with 50.0%.

What is the revenue of IL VEILEDNING OG TERAPI AS?

IL VEILEDNING OG TERAPI AS had revenue of NOK 172,000 in 2024.

Who is the general manager of IL VEILEDNING OG TERAPI AS?

Ingvil Øiestad Løvik is registered as general manager of IL VEILEDNING OG TERAPI AS.

Where is IL VEILEDNING OG TERAPI AS based?

IL VEILEDNING OG TERAPI AS has its business address in Hell.

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.