BIZTRAC BETA
General medical practice activities

LEGE RONALDO REYES AS

Org. no. 931859307 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 46,000
Operating profit NOK 27,000
Equity NOK 53,000
Incorporated 2023
Share capital NOK 30,000

LEGE RONALDO REYES AS is registered as a limited company in Oslo, Oslo with organisation number 931859307. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Tilby helsetjenester, konsulenttjenester, investeringer i aksjer, eiendom og hva herved står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 46,000 in revenue and NOK 27,000 in operating profit.

Key figures · 2024

Revenue
NOK 46,000
Operating profit
NOK 27,000
Equity
NOK 53,000
Est. value
NOK 120,000

Financial health · 2024

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

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

Who owns LEGE RONALDO REYES AS?

RONALDO VALUZ REYES
LEGE RONALDO REYES AS
NOK 46,000 rev. · NOK 27,000 profit

LEGE RONALDO REYES AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LEGE RONALDO REYES AS

Who owns LEGE RONALDO REYES AS?

RONALDO VALUZ REYES is the largest registered owner, with 100.0%.

What is the revenue of LEGE RONALDO REYES AS?

LEGE RONALDO REYES AS had revenue of NOK 46,000 in 2024.

Who is the general manager of LEGE RONALDO REYES AS?

Ronaldo Valuz Reyes is registered as general manager of LEGE RONALDO REYES AS.

Where is LEGE RONALDO REYES AS based?

LEGE RONALDO REYES AS has its business address in Oslo.

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.