BIZTRAC BETA
Distribution of electricity

VISSI AS

Org. no. 921683057 Limited company (AS) Nordreisa Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 112.8m
Operating profit NOK 20.8m
Equity NOK 137.3m
Incorporated 2018
Employees 37
Share capital NOK 150,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

VISSI AS is registered as a limited company in Nordreisa, Troms with organisation number 921683057. The business is classified under distribution of electricity (NACE 35.140). The company was incorporated in 2018 and has 37 registered employees. Registered share capital is NOK 150,000, divided into 30000 shares. The company's stated purpose is: “Bygge, eie og drive anlegg for omforming og distribusjon av elektrisk energi, samt delta i andre selskaper innen nettvirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 112.8m in revenue and NOK 20.8m in operating profit.

Key figures · 2024

Revenue
NOK 112.8m
Operating profit
NOK 20.8m
Equity
NOK 137.3m
Est. value
NOK 137.9m

Financial health · 2024

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

Who owns VISSI AS?

YMBER AS
VISSI AS
NOK 112.8m rev. · NOK 20.8m profit

VISSI AS has 1 registered shareholder:

All shareholders and roles →

Group structure

VISSI AS er morselskap for 2 datterselskaper:

Frequently asked questions about VISSI AS

Who owns VISSI AS?

YMBER AS is the largest registered owner, with 100.0%.

What is the revenue of VISSI AS?

VISSI AS had revenue of NOK 112.8m in 2024.

Who is the general manager of VISSI AS?

Finn Paulsen is registered as general manager of VISSI AS.

Where is VISSI AS based?

VISSI AS has its business address in Sørkjosen.

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.