BIZTRAC BETA
General medical practice activities

KLINIKK.NO AS

Org. no. 923865403 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −21,000
Equity NOK −965,000
Incorporated 2019
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−965k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−21k kr).

KLINIKK.NO AS is registered as a limited company in Oslo, Oslo with organisation number 923865403. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2019. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Allmenn legetjeneste, utvikling og salg av helserelatert teknologi og alt som naturlig er forbundet med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −21,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −21,000
Equity
NOK −965,000

Financial health · 2025

Liquidity
79.20
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-2707.0%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns KLINIKK.NO AS?

FISK INVEST AS
KLINIKK.NO AS
NOK 0 rev. · NOK −21,000 profit

KLINIKK.NO AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about KLINIKK.NO AS

Who owns KLINIKK.NO AS?

FISK INVEST AS is the largest registered owner, with 61.7%.

What is the revenue of KLINIKK.NO AS?

KLINIKK.NO AS had revenue of NOK 0 in 2025.

Who is the general manager of KLINIKK.NO AS?

Stian Fintland Skaug is registered as general manager of KLINIKK.NO AS.

Where is KLINIKK.NO AS based?

KLINIKK.NO AS has its business address in Oslo.

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.