BIZTRAC BETA
General medical practice activities

LEGE LAILA RØISE AS

Org. no. 916631634 Limited company (AS) Kongsberg Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 4.0m
Operating profit NOK 1.1m
Equity NOK 2.3m
Incorporated 2016
Share capital NOK 30,000

LEGE LAILA RØISE AS is registered as a limited company in Kongsberg, Buskerud with organisation number 916631634. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Allmennlegevirksomhet, herunder å delta i andre selskap med liknende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.0m in revenue and NOK 1.1m in operating profit.

Key figures · 2025

Revenue
NOK 4.0m
Operating profit
NOK 1.1m
Equity
NOK 2.3m
Est. value
NOK 5.3m

Financial health · 2024

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

Who owns LEGE LAILA RØISE AS?

LAILA RØISE
LEGE LAILA RØISE AS
NOK 4.0m rev. · NOK 1.1m profit

LEGE LAILA RØISE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LEGE LAILA RØISE AS own?

LEGE LAILA RØISE AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about LEGE LAILA RØISE AS

Who owns LEGE LAILA RØISE AS?

LAILA RØISE is the largest registered owner, with 100.0%.

What is the revenue of LEGE LAILA RØISE AS?

LEGE LAILA RØISE AS had revenue of NOK 4.0m in 2025.

Who is the general manager of LEGE LAILA RØISE AS?

Laila Røise is registered as general manager of LEGE LAILA RØISE AS.

Where is LEGE LAILA RØISE AS based?

LEGE LAILA RØISE AS has its business address in Kongsberg.

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.