BIZTRAC BETA
Retail sale of household utensils, cutlery, crockery, glassware, tableware, china and pottery

WIK & WALSØE HANDEL AS

Org. no. 915797121 Limited company (AS) Fredrikstad Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 1.0m
Operating profit NOK 11,000
Equity NOK 564,000
Incorporated 2015
Share capital NOK 30,000

WIK & WALSØE HANDEL AS is registered as a limited company in Fredrikstad, Østfold with organisation number 915797121. The business is classified under retail sale of household utensils, cutlery, crockery, glassware, tableware, china and pottery (NACE 47.553). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Handel med vekt på netthandel av varer.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.0m in revenue and NOK 11,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.0m
Operating profit
NOK 11,000
Equity
NOK 564,000
Est. value
NOK 332,000

Financial health · 2024

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

Who owns WIK & WALSØE HANDEL AS?

WIWA HOLDING AS
WIK & WALSØE HANDEL AS
NOK 1.0m rev. · NOK 11,000 profit

WIK & WALSØE HANDEL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about WIK & WALSØE HANDEL AS

Who owns WIK & WALSØE HANDEL AS?

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

What is the revenue of WIK & WALSØE HANDEL AS?

WIK & WALSØE HANDEL AS had revenue of NOK 1.0m in 2024.

Who is the general manager of WIK & WALSØE HANDEL AS?

Jon Jørundland is registered as general manager of WIK & WALSØE HANDEL AS.

Where is WIK & WALSØE HANDEL AS based?

WIK & WALSØE HANDEL AS has its business address in Kråkerøy.

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.