biztrac. BETA
COMPANY REGISTER PROFILE
971201444 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
General medical practice activities

TOPPEN LEGESENTER AS

Org. no. 971201444 Limited company (AS) Lillehammer Incorporated 1994 Active
Ownership graph ↗
Revenue 2025 NOK 5.8m
Operating profit NOK 9,000
Equity NOK 321,000
Incorporated 1994
Share capital NOK 100,000

TOPPEN LEGESENTER AS is registered as a limited company in Lillehammer, Innlandet with organisation number 971201444. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 1994. Registered share capital is NOK 100,000. The company's stated purpose is: “Selskapets formål er å organisere og administrere drift av legesenter, samt annet som står i nærhet til dette herunder eie og forvalte fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.8m in revenue and NOK 9,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.8m
▲ +7 %
Operating profit
NOK 9,000
▲ +809 %
Equity
NOK 321,000
▲ +0 %
Est. value
NOK 232,000

Financial health · 2025

Liquidity
1.06
Satisfactory
Current assets ÷ current liabilities
Profitability
0.9%
Not satisfactory
Return on total assets
Solidity
24.3%
Good
Equity as a share of total capital

Who owns TOPPEN LEGESENTER AS?

TOPPEN LEGESENTER AS has 6 registered shareholders:

All shareholders and roles →

Frequently asked questions about TOPPEN LEGESENTER AS

Who owns TOPPEN LEGESENTER AS?

Martin Lundeby is the largest registered owner, with 20.0%.

What is the revenue of TOPPEN LEGESENTER AS?

TOPPEN LEGESENTER AS had revenue of NOK 5.8m in 2025.

Who is the general manager of TOPPEN LEGESENTER AS?

Monica Knutsen is registered as general manager of TOPPEN LEGESENTER AS.

Where is TOPPEN LEGESENTER AS based?

TOPPEN LEGESENTER AS has its business address in Lillehammer.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.