BIZTRAC BETA
Activities of specialist physicians, other than psychiatrists

ØYELEGE PER KLYVE AS

Org. no. 989628674 Limited company (AS) Asker Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK −457,000
Operating profit NOK −833,000
Equity NOK 17.8m
Incorporated 2006
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−833k kr).

ØYELEGE PER KLYVE AS is registered as a limited company in Asker, Akershus with organisation number 989628674. The business is classified under activities of specialist physicians, other than psychiatrists (NACE 86.221). The company was incorporated in 2006. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Spesialisert øyelege tjeneste.”. The most recent filed accounts, for the 2025 financial year, show NOK −457,000 in revenue and NOK −833,000 in operating profit.

Key figures · 2025

Revenue
NOK −457,000
Operating profit
NOK −833,000
Equity
NOK 17.8m
Est. value
NOK 53.7m

Financial health · 2025

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

Who owns ØYELEGE PER KLYVE AS?

PER KLYVE
ØYELEGE PER KLYVE AS
NOK −457,000 rev. · NOK −833,000 profit

ØYELEGE PER KLYVE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ØYELEGE PER KLYVE AS

Who owns ØYELEGE PER KLYVE AS?

PER KLYVE is the largest registered owner, with 100.0%.

What is the revenue of ØYELEGE PER KLYVE AS?

ØYELEGE PER KLYVE AS had revenue of NOK −457,000 in 2025.

Who is the general manager of ØYELEGE PER KLYVE AS?

Per Klyve is registered as general manager of ØYELEGE PER KLYVE AS.

Where is ØYELEGE PER KLYVE AS based?

ØYELEGE PER KLYVE AS has its business address in Hvalstad.

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.