biztrac. BETA
COMPANY REGISTER PROFILE
993891932 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Activities of specialist physicians, other than psychiatrists

OCULOMOTORIUS AS

Org. no. 993891932 Limited company (AS) Bergen Incorporated 2009 Active
Revenue 2025 NOK 8.4m
Operating profit NOK 2.8m
Equity NOK 14.2m
Incorporated 2009
Share capital NOK 100,000

OCULOMOTORIUS AS is registered as a limited company in Bergen, Vestland with organisation number 993891932. 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: “Øyelegepraksis samt hva som naturlig står i forbindelse herved, herunder deltagelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 8.4m in revenue and NOK 2.8m in operating profit.

Key figures · 2025

Revenue
NOK 8.4m
▲ +4 %
Operating profit
NOK 2.8m
▼ −10 %
Equity
NOK 14.2m
▲ +31 %
Est. value
NOK 21.4m

Financial health · 2025

Liquidity
5.16
Very good
Current assets ÷ current liabilities
Profitability
33.5%
Very good
Return on total assets
Solidity
83.6%
Very good
Equity as a share of total capital

Who owns OCULOMOTORIUS AS?

OCULOMOTORIUS AS
NOK 8.4m rev. · NOK 2.8m profit

OCULOMOTORIUS AS has 1 registered shareholder:

All shareholders and roles →

Which companies does OCULOMOTORIUS AS own?

OCULOMOTORIUS AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about OCULOMOTORIUS AS

Who owns OCULOMOTORIUS AS?

Christian Haakon Bjune is the largest registered owner, with 100.0%.

What is the revenue of OCULOMOTORIUS AS?

OCULOMOTORIUS AS had revenue of NOK 8.4m in 2025.

Where is OCULOMOTORIUS AS based?

OCULOMOTORIUS AS has its business address in Bergen.

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.