BIZTRAC BETA
COMPANY REGISTER PROFILE
928663175 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

VIPER INVESTMENT AS

Org. no. 928663175 Limited company (AS) Skien Incorporated 2021 Active
Ownership graph ↗
Operating profit NOK 14,000
Equity NOK 292,000
Incorporated 2021
Share capital NOK 150,000

VIPER INVESTMENT AS is registered as a limited company in Skien, Telemark with organisation number 928663175. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 150,000, divided into 150 shares. The company's stated purpose is: “Investering i verdipapirer.”.

Key figures · 2025

Operating profit
NOK 14,000
Equity
NOK 292,000
Est. value
NOK 219,000

Financial health · 2025

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

Who owns VIPER INVESTMENT AS?

VIPER INVESTMENT AS
· NOK 14,000 profit

VIPER INVESTMENT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about VIPER INVESTMENT AS

Who owns VIPER INVESTMENT AS?

EMSY INVEST AS is the largest registered owner, with 50.0%.

Who is the general manager of VIPER INVESTMENT AS?

Emil Syversen is registered as general manager of VIPER INVESTMENT AS.

Where is VIPER INVESTMENT AS based?

VIPER INVESTMENT AS has its business address in Skien.

Property

Business address Vindalskroken 16, 3728 Skien
Cadastral unit 4003-217/562/0/0
Building Enebolig · 1 unit

2 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.