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

LEGEDRARYEE AS

Org. no. 935460905 Limited company (AS) Kragerø Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 2.5m
Operating profit NOK 2.5m
Equity NOK 2.0m
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-08-27 Adresseendring registrert 2026-08-27.

LEGEDRARYEE AS is registered as a limited company in Kragerø, Telemark with organisation number 935460905. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Legetjenester og andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.5m in revenue and NOK 2.5m in operating profit.

Key figures · 2025

Revenue
NOK 2.5m
Operating profit
NOK 2.5m
Equity
NOK 2.0m
Est. value
NOK 9.9m

Financial health · 2025

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

Who owns LEGEDRARYEE AS?

LEGEDRARYEE AS
NOK 2.5m rev. · NOK 2.5m profit

LEGEDRARYEE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LEGEDRARYEE AS

Who owns LEGEDRARYEE AS?

Ellen Isabella Viktoria Aryee is the largest registered owner, with 100.0%.

What is the revenue of LEGEDRARYEE AS?

LEGEDRARYEE AS had revenue of NOK 2.5m in 2025.

Where is LEGEDRARYEE AS based?

LEGEDRARYEE AS has its business address in Kragerø.

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.