BIZTRAC BETA
Preventive health care activities

SVEN WIIK AS

Org. no. 996822303 Limited company (AS) Kristiansand Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK 53,000
Equity NOK 155,000
Incorporated 2011
Share capital NOK 30,000

SVEN WIIK AS is registered as a limited company in Kristiansand, Agder with organisation number 996822303. The business is classified under preventive health care activities (NACE 86.992). The company was incorporated in 2011. Registered share capital is NOK 30,000, divided into 100000 shares. The company's stated purpose is: “Undervisning og rådgivning innen regelverk innen håndtering av farlig gods/farlig avfall og annet som naturlig faller inn under dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK 53,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
Operating profit
NOK 53,000
Equity
NOK 155,000
Est. value
NOK 339,000

Financial health · 2025

Liquidity
1.40
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
28.5%
Good
Equity as a share of total capital

Who owns SVEN WIIK AS?

SVEN VIDAR WIIK
SVEN WIIK AS
NOK 1.1m rev. · NOK 53,000 profit

SVEN WIIK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SVEN WIIK AS

Who owns SVEN WIIK AS?

SVEN VIDAR WIIK is the largest registered owner, with 100.0%.

What is the revenue of SVEN WIIK AS?

SVEN WIIK AS had revenue of NOK 1.1m in 2025.

Who is the general manager of SVEN WIIK AS?

Sven Vidar Wiik is registered as general manager of SVEN WIIK AS.

Where is SVEN WIIK AS based?

SVEN WIIK AS has its business address in Hamresanden.

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.