BIZTRAC BETA
Other health services

KORPEVEIEN LEGEKLINIKK AS

Org. no. 825893822 Limited company (AS) Drammen Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 3.2m
Operating profit NOK 587,000
Equity NOK 2.0m
Incorporated 2020
Share capital NOK 30,000

KORPEVEIEN LEGEKLINIKK AS is registered as a limited company in Drammen, Buskerud with organisation number 825893822. The business is classified under other health services (NACE 86.993). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Helsetjenester inkludert estetiske behandlinger, og andre produkter/tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.2m in revenue and NOK 587,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.2m
Operating profit
NOK 587,000
Equity
NOK 2.0m
Est. value
NOK 3.9m

Financial health · 2025

Liquidity
4.78
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
85.0%
Very good
Equity as a share of total capital

Who owns KORPEVEIEN LEGEKLINIKK AS?

MONICA MARIE BRAATEN
KORPEVEIEN LEGEKLINIKK AS
NOK 3.2m rev. · NOK 587,000 profit

KORPEVEIEN LEGEKLINIKK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KORPEVEIEN LEGEKLINIKK AS

Who owns KORPEVEIEN LEGEKLINIKK AS?

MONICA MARIE BRAATEN is the largest registered owner, with 100.0%.

What is the revenue of KORPEVEIEN LEGEKLINIKK AS?

KORPEVEIEN LEGEKLINIKK AS had revenue of NOK 3.2m in 2025.

Who is the general manager of KORPEVEIEN LEGEKLINIKK AS?

Monica Marie Braaten is registered as general manager of KORPEVEIEN LEGEKLINIKK AS.

Where is KORPEVEIEN LEGEKLINIKK AS based?

KORPEVEIEN LEGEKLINIKK AS has its business address in Mjøndalen.

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.