BIZTRAC BETA
General medical practice activities

RUNE AASBØ LYSTAD AS

Org. no. 918752439 Limited company (AS) Risør Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 4.8m
Operating profit NOK 2.5m
Equity NOK 31,000
Incorporated 2017
Share capital NOK 30,000

RUNE AASBØ LYSTAD AS is registered as a limited company in Risør, Agder with organisation number 918752439. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Allmennlegepraksis og annen legevirksomhet, samt annet som natulig faller inn under dette, herunder å delta og eie aksjer og andeler i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.8m in revenue and NOK 2.5m in operating profit.

Key figures · 2025

Revenue
NOK 4.8m
Operating profit
NOK 2.5m
Equity
NOK 31,000
Est. value
NOK 8.2m

Financial health · 2025

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

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

Who owns RUNE AASBØ LYSTAD AS?

RUNE AASBØ LYSTAD
RUNE AASBØ LYSTAD AS
NOK 4.8m rev. · NOK 2.5m profit

RUNE AASBØ LYSTAD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RUNE AASBØ LYSTAD AS

Who owns RUNE AASBØ LYSTAD AS?

RUNE AASBØ LYSTAD is the largest registered owner, with 100.0%.

What is the revenue of RUNE AASBØ LYSTAD AS?

RUNE AASBØ LYSTAD AS had revenue of NOK 4.8m in 2025.

Who is the general manager of RUNE AASBØ LYSTAD AS?

Rune Aasbø Lystad is registered as general manager of RUNE AASBØ LYSTAD AS.

Where is RUNE AASBØ LYSTAD AS based?

RUNE AASBØ LYSTAD AS has its business address in Risør.

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.