BIZTRAC BETA
Traditional, complementary and alternative medicine activities

OPTIMAL BEVEGELSE AS

Org. no. 998439752 Limited company (AS) Klepp Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK 89,000
Equity NOK 136,000
Incorporated 2012
Share capital NOK 80,000

OPTIMAL BEVEGELSE AS is registered as a limited company in Klepp, Rogaland with organisation number 998439752. The business is classified under traditional, complementary and alternative medicine activities (NACE 86.960). The company was incorporated in 2012. Registered share capital is NOK 80,000, divided into 160 shares. The company's stated purpose is: “Fremstilling/salg av naprapatbehandling og andre produkter som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK 89,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
Operating profit
NOK 89,000
Equity
NOK 136,000
Est. value
NOK 504,000

Financial health · 2025

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

Who owns OPTIMAL BEVEGELSE AS?

LISE KARINE HOFSTAD STENSLET
OPTIMAL BEVEGELSE AS
NOK 1.1m rev. · NOK 89,000 profit

OPTIMAL BEVEGELSE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OPTIMAL BEVEGELSE AS

Who owns OPTIMAL BEVEGELSE AS?

LISE KARINE HOFSTAD STENSLET is the largest registered owner, with 100.0%.

What is the revenue of OPTIMAL BEVEGELSE AS?

OPTIMAL BEVEGELSE AS had revenue of NOK 1.1m in 2025.

Who is the general manager of OPTIMAL BEVEGELSE AS?

Lise Karine Hofstad Stenslet is registered as general manager of OPTIMAL BEVEGELSE AS.

Where is OPTIMAL BEVEGELSE AS based?

OPTIMAL BEVEGELSE AS has its business address in Kleppe.

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.