BIZTRAC BETA
Retail sale of motor vehicle parts and accessories

OPTIMAL VARSLING AS

Org. no. 921283520 Limited company (AS) Horten Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 120,000
Operating profit NOK 17,000
Equity NOK 178,000
Incorporated 2018
Share capital NOK 58,000

OPTIMAL VARSLING AS is registered as a limited company in Horten, Vestfold with organisation number 921283520. The business is classified under retail sale of motor vehicle parts and accessories (NACE 47.820). The company was incorporated in 2018. Registered share capital is NOK 58,000, divided into 580 shares. The company's stated purpose is: “Detaljhandel med deler, rekvisita og utstyr til motorkjøretøy, og alt som herved står i forbindelse, herunder deltagelse i andre selskaper med lignende formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 120,000 in revenue and NOK 17,000 in operating profit.

Key figures · 2025

Revenue
NOK 120,000
Operating profit
NOK 17,000
Equity
NOK 178,000
Est. value
NOK 150,000

Financial health · 2025

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

Who owns OPTIMAL VARSLING AS?

NXTINSIGHT AS
OPTIMAL VARSLING AS
NOK 120,000 rev. · NOK 17,000 profit

OPTIMAL VARSLING AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about OPTIMAL VARSLING AS

Who owns OPTIMAL VARSLING AS?

NXTINSIGHT AS is the largest registered owner, with 26.0%.

What is the revenue of OPTIMAL VARSLING AS?

OPTIMAL VARSLING AS had revenue of NOK 120,000 in 2025.

Who is the general manager of OPTIMAL VARSLING AS?

Richard Løw is registered as general manager of OPTIMAL VARSLING AS.

Where is OPTIMAL VARSLING AS based?

OPTIMAL VARSLING AS has its business address in Nykirke.

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.