BIZTRAC BETA
General medical practice activities

LEGE ALEXANDER NYSTEDT AS

Org. no. 915452051 Limited company (AS) Arendal Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 3.3m
Operating profit NOK 2.1m
Equity NOK 32,000
Incorporated 2015
Share capital NOK 30,000

LEGE ALEXANDER NYSTEDT AS is registered as a limited company in Arendal, Agder with organisation number 915452051. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Allmenn legetjeneste og alt som hører naturlig i denne forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.3m in revenue and NOK 2.1m in operating profit.

Key figures · 2025

Revenue
NOK 3.3m
Operating profit
NOK 2.1m
Equity
NOK 32,000
Est. value
NOK 6.6m

Financial health · 2025

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

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

Who owns LEGE ALEXANDER NYSTEDT AS?

ALEXANDER NYSTEDT
LEGE ALEXANDER NYSTEDT AS
NOK 3.3m rev. · NOK 2.1m profit

LEGE ALEXANDER NYSTEDT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LEGE ALEXANDER NYSTEDT AS

Who owns LEGE ALEXANDER NYSTEDT AS?

ALEXANDER NYSTEDT is the largest registered owner, with 100.0%.

What is the revenue of LEGE ALEXANDER NYSTEDT AS?

LEGE ALEXANDER NYSTEDT AS had revenue of NOK 3.3m in 2025.

Who is the general manager of LEGE ALEXANDER NYSTEDT AS?

Alexander Nystedt is registered as general manager of LEGE ALEXANDER NYSTEDT AS.

Where is LEGE ALEXANDER NYSTEDT AS based?

LEGE ALEXANDER NYSTEDT AS has its business address in Arendal.

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.