BIZTRAC BETA
General medical practice activities

VALENTINLYST LEGESENTER AS

Org. no. 931106961 Limited company (AS) Trondheim Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 6.3m
Operating profit NOK 385,000
Equity NOK 333,000
Incorporated 2023
Employees 7
Share capital NOK 42,000

VALENTINLYST LEGESENTER AS is registered as a limited company in Trondheim, Trøndelag with organisation number 931106961. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2023 and has 7 registered employees. Registered share capital is NOK 42,000, divided into 4200 shares. The company's stated purpose is: “Kontorfellesskap for leger i allmennpraksis.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.3m in revenue and NOK 385,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.3m
Operating profit
NOK 385,000
Equity
NOK 333,000
Est. value
NOK 2.0m

Financial health · 2025

Liquidity
0.97
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
27.1%
Good
Equity as a share of total capital

Who owns VALENTINLYST LEGESENTER AS?

KRISTIN IREN ANDERSEN
VALENTINLYST LEGESENTER AS
NOK 6.3m rev. · NOK 385,000 profit

VALENTINLYST LEGESENTER AS has 6 registered shareholders:

All shareholders and roles →

Frequently asked questions about VALENTINLYST LEGESENTER AS

Who owns VALENTINLYST LEGESENTER AS?

KRISTIN IREN ANDERSEN is the largest registered owner, with 16.7%.

What is the revenue of VALENTINLYST LEGESENTER AS?

VALENTINLYST LEGESENTER AS had revenue of NOK 6.3m in 2025.

Who is the general manager of VALENTINLYST LEGESENTER AS?

Erik Paltiel Mørch is registered as general manager of VALENTINLYST LEGESENTER AS.

Where is VALENTINLYST LEGESENTER AS based?

VALENTINLYST LEGESENTER AS has its business address in Trondheim.

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.