BIZTRAC BETA
General medical practice activities

MOAN LEGESENTER AS

Org. no. 915430074 Limited company (AS) Levanger Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 4.5m
Operating profit NOK 18,000
Equity NOK 54,000
Incorporated 2015
Employees 8
Share capital NOK 30,000

MOAN LEGESENTER AS is registered as a limited company in Levanger, Trøndelag with organisation number 915430074. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2015 and has 8 registered employees. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Å drive allmennlegevirksomhet og hva dermed står i forbindelse, herunder ved aksjeinnskudd eller på annen måte delta i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.5m in revenue and NOK 18,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.5m
Operating profit
NOK 18,000
Equity
NOK 54,000
Est. value
NOK 117,000

Financial health · 2024

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

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

Who owns MOAN LEGESENTER AS?

TORE EGGEN
MOAN LEGESENTER AS
NOK 4.5m rev. · NOK 18,000 profit

MOAN LEGESENTER AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about MOAN LEGESENTER AS

Who owns MOAN LEGESENTER AS?

TORE EGGEN is the largest registered owner, with 25.0%.

What is the revenue of MOAN LEGESENTER AS?

MOAN LEGESENTER AS had revenue of NOK 4.5m in 2024.

Who is the general manager of MOAN LEGESENTER AS?

Tore Eggen is registered as general manager of MOAN LEGESENTER AS.

Where is MOAN LEGESENTER AS based?

MOAN LEGESENTER AS has its business address in Levanger.

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.