BIZTRAC BETA
COMPANY REGISTER PROFILE
980404285 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 02.09.2026
Site preparation

WICKSTRØM AS

Org. no. 980404285 Limited company (AS) Vadsø Incorporated 1998 Active
Ownership graph ↗
Revenue 2025 NOK 17.4m
Operating profit NOK 3.3m
Equity NOK 12.7m
Incorporated 1998
Employees 6
Share capital NOK 100,000

WICKSTRØM AS is registered as a limited company in Vadsø, Finnmark with organisation number 980404285. The business is classified under site preparation (NACE 43.120). The company was incorporated in 1998 and has 6 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Maskin- og anleggsvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 17.4m in revenue and NOK 3.3m in operating profit.

Former names: VALTER WICKSTRØM & SØNN AS

Key figures · 2025

Revenue
NOK 17.4m
▲ +19 %
Operating profit
NOK 3.3m
▲ +7 %
Equity
NOK 12.7m
▲ +26 %
Est. value
NOK 16.5m

Financial health · 2025

Liquidity
4.01
Very good
Current assets ÷ current liabilities
Profitability
22.1%
Very good
Return on total assets
Solidity
78.7%
Very good
Equity as a share of total capital

Who owns WICKSTRØM AS?

WICKSTRØM AS
NOK 17.4m rev. · NOK 3.3m profit

WICKSTRØM AS has 2 registered shareholders:

All shareholders and roles →

Which companies does WICKSTRØM AS own?

WICKSTRØM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about WICKSTRØM AS

Who owns WICKSTRØM AS?

AUDUN VALTER WICKSTRØM is the largest registered owner, with 95.0%.

What is the revenue of WICKSTRØM AS?

WICKSTRØM AS had revenue of NOK 17.4m in 2025.

Who is the general manager of WICKSTRØM AS?

Audun Valter Wickstrøm is registered as general manager of WICKSTRØM AS.

Where is WICKSTRØM AS based?

WICKSTRØM AS has its business address in Vestre Jakobselv.

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.