BIZTRAC BETA
Activities of specialist physicians, other than psychiatrists

MIDTBYEN ØYEKLINIKK AS

Org. no. 997826086 Limited company (AS) Trondheim Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 8.8m
Operating profit NOK 2.9m
Equity NOK 2.1m
Incorporated 2012
Employees 8
Share capital NOK 30,000

MIDTBYEN ØYEKLINIKK AS is registered as a limited company in Trondheim, Trøndelag with organisation number 997826086. The business is classified under activities of specialist physicians, other than psychiatrists (NACE 86.221). The company was incorporated in 2012 and has 8 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Øyelegvirksomhet og annen virksomhet som har naturlig tilknytning til denne.”. The most recent filed accounts, for the 2025 financial year, show NOK 8.8m in revenue and NOK 2.9m in operating profit.

Key figures · 2025

Revenue
NOK 8.8m
Operating profit
NOK 2.9m
Equity
NOK 2.1m
Est. value
NOK 11.1m

Financial health · 2025

Liquidity
1.17
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
36.6%
Good
Equity as a share of total capital

Who owns MIDTBYEN ØYEKLINIKK AS?

RØNNAUG BRANDSER
MIDTBYEN ØYEKLINIKK AS
NOK 8.8m rev. · NOK 2.9m profit

MIDTBYEN ØYEKLINIKK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MIDTBYEN ØYEKLINIKK AS

Who owns MIDTBYEN ØYEKLINIKK AS?

RØNNAUG BRANDSER is the largest registered owner, with 100.0%.

What is the revenue of MIDTBYEN ØYEKLINIKK AS?

MIDTBYEN ØYEKLINIKK AS had revenue of NOK 8.8m in 2025.

Who is the general manager of MIDTBYEN ØYEKLINIKK AS?

Rønnaug Brandser is registered as general manager of MIDTBYEN ØYEKLINIKK AS.

Where is MIDTBYEN ØYEKLINIKK AS based?

MIDTBYEN ØYEKLINIKK AS has its business address in Trondheim.

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.