BIZTRAC BETA
Computer programming activities

VARSKO AS

Org. no. 931506927 Limited company (AS) Indre Østfold Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 125,000
Operating profit NOK −38,000
Equity NOK 53,000
Incorporated 2023
Share capital NOK 43,000

Signals

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

VARSKO AS is registered as a limited company in Indre Østfold, Østfold with organisation number 931506927. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2023. Registered share capital is NOK 43,000, divided into 42850 shares. The company's stated purpose is: “Selge tjenester og varer innen alarmsystemer og annet som naturlig sammenfaller med dette, samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 125,000 in revenue and NOK −38,000 in operating profit.

Key figures · 2025

Revenue
NOK 125,000
Operating profit
NOK −38,000
Equity
NOK 53,000
Est. value
NOK 235,000

Financial health · 2025

Liquidity
0.94
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
10.3%
Weak
Equity as a share of total capital

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

Who owns VARSKO AS?

MORTEN ØVERBYE
VARSKO AS
NOK 125,000 rev. · NOK −38,000 profit

VARSKO AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about VARSKO AS

Who owns VARSKO AS?

MORTEN ØVERBYE is the largest registered owner, with 70.0%.

What is the revenue of VARSKO AS?

VARSKO AS had revenue of NOK 125,000 in 2025.

Who is the general manager of VARSKO AS?

Morten Øverbye is registered as general manager of VARSKO AS.

Where is VARSKO AS based?

VARSKO AS has its business address in Tomter.

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.