BIZTRAC BETA
Silviculture and other forestry activities

VISIG VIRKE AS

Org. no. 931539795 Limited company (AS) Bergen Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 24,000
Operating profit NOK 3,000
Equity NOK 26,000
Incorporated 2023
Share capital NOK 30,000

VISIG VIRKE AS is registered as a limited company in Bergen, Vestland with organisation number 931539795. The business is classified under silviculture and other forestry activities (NACE 02.100). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Utførelse av mindre håndtverksjobber, skogsarbeid, hagearbeid og generelle småjobber.”. The most recent filed accounts, for the 2024 financial year, show NOK 24,000 in revenue and NOK 3,000 in operating profit.

Key figures · 2024

Revenue
NOK 24,000
Operating profit
NOK 3,000
Equity
NOK 26,000
Est. value
NOK 25,000

Financial health · 2024

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

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

Who owns VISIG VIRKE AS?

VISIG HOLDING AS
VISIG VIRKE AS
NOK 24,000 rev. · NOK 3,000 profit

VISIG VIRKE AS has 1 registered shareholder:

All shareholders and roles →

Group structure

VISIG VIRKE AS er morselskap for 1 datterselskap:

Frequently asked questions about VISIG VIRKE AS

Who owns VISIG VIRKE AS?

VISIG HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of VISIG VIRKE AS?

VISIG VIRKE AS had revenue of NOK 24,000 in 2024.

Who is the general manager of VISIG VIRKE AS?

Anders Henneli Ingebrigtsen is registered as general manager of VISIG VIRKE AS.

Where is VISIG VIRKE AS based?

VISIG VIRKE AS has its business address in Bergen.

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.