BIZTRAC BETA
Other health services

DRIV KLINIKKEN AS

Org. no. 927370514 Limited company (AS) Nes Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 942,000
Operating profit NOK −177,000
Equity NOK −668,000
Incorporated 2021
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−668k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−177k kr).

DRIV KLINIKKEN AS is registered as a limited company in Nes, Akershus with organisation number 927370514. The business is classified under other health services (NACE 86.993). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Salg av helserettede tjenester samt yte service til andre virksomheter som driver helserettet virksomhet. I tillegg hva styret finner interessant for selskapet.”. The most recent filed accounts, for the 2024 financial year, show NOK 942,000 in revenue and NOK −177,000 in operating profit.

Key figures · 2024

Revenue
NOK 942,000
Operating profit
NOK −177,000
Equity
NOK −668,000

Financial health · 2024

Liquidity
0.18
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-149.0%
Weak
Equity as a share of total capital

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

Who owns DRIV KLINIKKEN AS?

ENGERSBORG AS
DRIV KLINIKKEN AS
NOK 942,000 rev. · NOK −177,000 profit

DRIV KLINIKKEN AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about DRIV KLINIKKEN AS

Who owns DRIV KLINIKKEN AS?

ENGERSBORG AS is the largest registered owner, with 50.0%.

What is the revenue of DRIV KLINIKKEN AS?

DRIV KLINIKKEN AS had revenue of NOK 942,000 in 2024.

Where is DRIV KLINIKKEN AS based?

DRIV KLINIKKEN AS has its business address in Årnes.

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.