biztrac. BETA
COMPANY REGISTER PROFILE
981868846 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Site preparation

VIGGO ERIKSEN AS

Org. no. 981868846 Limited company (AS) Hammerfest Incorporated 1999 Active
Ownership graph ↗
Revenue 2025 NOK 145.2m
Operating profit NOK 19.7m
Equity NOK 29.8m
Incorporated 1999
Employees 55
Share capital NOK 30,000

VIGGO ERIKSEN AS is registered as a limited company in Hammerfest, Finnmark with organisation number 981868846. The business is classified under site preparation (NACE 43.120). The company was incorporated in 1999 and has 55 registered employees. Registered share capital is NOK 30,000, divided into 2000 shares. The company's stated purpose is: “Anleggsvirksomhet, samt det som naturlig hører inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 145.2m in revenue and NOK 19.7m in operating profit.

Key figures · 2025

Revenue
NOK 145.2m
▲ +53 %
Operating profit
NOK 19.7m
▲ +107 %
Equity
NOK 29.8m
▲ +16 %
Est. value
NOK 59.3m

Financial health · 2025

Liquidity
1.51
Good
Current assets ÷ current liabilities
Profitability
34.7%
Very good
Return on total assets
Solidity
42.9%
Very good
Equity as a share of total capital

Who owns VIGGO ERIKSEN AS?

VIGGO ERIKSEN AS
NOK 145.2m rev. · NOK 19.7m profit

VIGGO ERIKSEN AS has 1 registered shareholder:

All shareholders and roles →

Group structure

VIGGO ERIKSEN AS er morselskap for 2 datterselskaper:

Frequently asked questions about VIGGO ERIKSEN AS

Who owns VIGGO ERIKSEN AS?

VIGGO ERIKSEN INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of VIGGO ERIKSEN AS?

VIGGO ERIKSEN AS had revenue of NOK 145.2m in 2025.

Who is the general manager of VIGGO ERIKSEN AS?

Viggo Eriksen is registered as general manager of VIGGO ERIKSEN AS.

Where is VIGGO ERIKSEN AS based?

VIGGO ERIKSEN AS has its business address in Rypefjord.

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

Report a problem

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