BIZTRAC BETA
Activities of specialist physicians, other than psychiatrists

ØYELEGE KNUT SALOMONSEN AS

Org. no. 894545992 Limited company (AS) Bodø Incorporated 2009 Active
Ownership graph ↗
Revenue 2024 NOK 4.3m
Operating profit NOK 14,000
Equity NOK 4.8m
Incorporated 2009
Share capital NOK 100,000

ØYELEGE KNUT SALOMONSEN AS is registered as a limited company in Bodø, Nordland with organisation number 894545992. The business is classified under activities of specialist physicians, other than psychiatrists (NACE 86.221). The company was incorporated in 2009. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Medisinsk og kirurgisk legevirksomhet, samt kjøp og salg av aksjer og eiendommer.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.3m in revenue and NOK 14,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.3m
Operating profit
NOK 14,000
Equity
NOK 4.8m
Est. value
NOK 3.0m

Financial health · 2024

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

Who owns ØYELEGE KNUT SALOMONSEN AS?

KNUT SALOMONSEN
ØYELEGE KNUT SALOMONSEN AS
NOK 4.3m rev. · NOK 14,000 profit

ØYELEGE KNUT SALOMONSEN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ØYELEGE KNUT SALOMONSEN AS own?

ØYELEGE KNUT SALOMONSEN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ØYELEGE KNUT SALOMONSEN AS

Who owns ØYELEGE KNUT SALOMONSEN AS?

KNUT SALOMONSEN is the largest registered owner, with 100.0%.

What is the revenue of ØYELEGE KNUT SALOMONSEN AS?

ØYELEGE KNUT SALOMONSEN AS had revenue of NOK 4.3m in 2024.

Where is ØYELEGE KNUT SALOMONSEN AS based?

ØYELEGE KNUT SALOMONSEN AS has its business address in Bodø.

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.