BIZTRAC BETA
Activities of specialist physicians, other than psychiatrists

KLINIKK S DRIFT AS

Org. no. 932934469 Limited company (AS) Bodø Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 6.2m
Operating profit NOK 202,000
Equity NOK 132,000
Incorporated 2024
Employees 8
Share capital NOK 30,000

KLINIKK S DRIFT AS is registered as a limited company in Bodø, Nordland with organisation number 932934469. The business is classified under activities of specialist physicians, other than psychiatrists (NACE 86.221). The company was incorporated in 2024 and has 8 registered employees. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Drift av øyenlegeklinikk, eie og utleie av utstyr til øyenlegevirksomhet, samt alt som naturlig kan knyttes til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.2m in revenue and NOK 202,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.2m
Operating profit
NOK 202,000
Equity
NOK 132,000
Est. value
NOK 681,000

Financial health · 2024

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

Who owns KLINIKK S DRIFT AS?

ØYELEGE CHRISTIAN E. SKAU AS
KLINIKK S DRIFT AS
NOK 6.2m rev. · NOK 202,000 profit

KLINIKK S DRIFT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KLINIKK S DRIFT AS

Who owns KLINIKK S DRIFT AS?

ØYELEGE CHRISTIAN E. SKAU AS is the largest registered owner, with 50.0%.

What is the revenue of KLINIKK S DRIFT AS?

KLINIKK S DRIFT AS had revenue of NOK 6.2m in 2025.

Who is the general manager of KLINIKK S DRIFT AS?

Katrin Tjærandsen is registered as general manager of KLINIKK S DRIFT AS.

Where is KLINIKK S DRIFT AS based?

KLINIKK S DRIFT 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.