BIZTRAC BETA
General medical practice activities

TROLLÅSEN LEGESENTER AS

Org. no. 922025134 Limited company (AS) Nordre Follo Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 5.0m
Operating profit NOK 24,000
Equity NOK 151,000
Incorporated 2018
Employees 6
Share capital NOK 30,000

TROLLÅSEN LEGESENTER AS is registered as a limited company in Nordre Follo, Akershus with organisation number 922025134. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2018 and has 6 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Helsetjeneste, informasjon og undervisning, salg, investering og utleie, samt deltakelse i annen virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.0m in revenue and NOK 24,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.0m
Operating profit
NOK 24,000
Equity
NOK 151,000
Est. value
NOK 204,000

Financial health · 2025

Liquidity
1.16
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
22.3%
Good
Equity as a share of total capital

Who owns TROLLÅSEN LEGESENTER AS?

INGER MARIE VEIBY
TROLLÅSEN LEGESENTER AS
NOK 5.0m rev. · NOK 24,000 profit

TROLLÅSEN LEGESENTER AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about TROLLÅSEN LEGESENTER AS

Who owns TROLLÅSEN LEGESENTER AS?

INGER MARIE VEIBY is the largest registered owner, with 20.0%.

What is the revenue of TROLLÅSEN LEGESENTER AS?

TROLLÅSEN LEGESENTER AS had revenue of NOK 5.0m in 2025.

Who is the general manager of TROLLÅSEN LEGESENTER AS?

Sivert Eggesvik is registered as general manager of TROLLÅSEN LEGESENTER AS.

Where is TROLLÅSEN LEGESENTER AS based?

TROLLÅSEN LEGESENTER AS has its business address in Trollåsen.

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.