biztrac. BETA
COMPANY REGISTER PROFILE
929344928 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Dental practice care activities

STEVIK KLØVE AS

Org. no. 929344928 Limited company (AS) Trondheim Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −3,000
Equity NOK 615,000
Incorporated 2022
Share capital NOK 30,000

Signals

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

STEVIK KLØVE AS is registered as a limited company in Trondheim, Trøndelag with organisation number 929344928. The business is classified under dental practice care activities (NACE 86.230). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Eie andre virksomheter, investere i andre selskaper og kjøp, salg og utleie av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −3,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −3,000
▲ +56 %
Equity
NOK 615,000
▲ +47 %
Est. value
NOK 4.9m

Financial health · 2025

Liquidity
333.30
Very good
Current assets ÷ current liabilities
Profitability
96.0%
Very good
Return on total assets
Solidity
99.7%
Very good
Equity as a share of total capital

Who owns STEVIK KLØVE AS?

STEVIK KLØVE AS
NOK 0 rev. · NOK −3,000 profit

STEVIK KLØVE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does STEVIK KLØVE AS own?

STEVIK KLØVE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about STEVIK KLØVE AS

Who owns STEVIK KLØVE AS?

Steinar Stevik Kløve is the largest registered owner, with 100.0%.

What is the revenue of STEVIK KLØVE AS?

STEVIK KLØVE AS had revenue of NOK 0 in 2025.

Where is STEVIK KLØVE AS based?

STEVIK KLØVE AS has its business address in Tiller.

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.