BIZTRAC BETA
Computer consultancy and computer facilities management activities

VISO AS

Org. no. 899021312 Limited company (AS) Asker Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 385,000
Operating profit NOK 44,000
Equity NOK 49,000
Incorporated 2012
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-06-24 Adresseendring registrert 2026-06-24.

VISO AS is registered as a limited company in Asker, Akershus with organisation number 899021312. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Rådgivning, konsulentbistand, undervisning og andre produkter og tjenester som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2025 financial year, show NOK 385,000 in revenue and NOK 44,000 in operating profit.

Key figures · 2025

Revenue
NOK 385,000
Operating profit
NOK 44,000
Equity
NOK 49,000
Est. value
NOK 284,000

Financial health · 2025

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

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

Who owns VISO AS?

TROND ARE HANSEN
VISO AS
NOK 385,000 rev. · NOK 44,000 profit

VISO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VISO AS

Who owns VISO AS?

TROND ARE HANSEN is the largest registered owner, with 100.0%.

What is the revenue of VISO AS?

VISO AS had revenue of NOK 385,000 in 2025.

Where is VISO AS based?

VISO AS has its business address in Nesbru.

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.