BIZTRAC BETA
Manufacture of furniture

SYVSOVEREN NORGE AS

Org. no. 933646351 Limited company (AS) Fredrikstad Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 2.9m
Operating profit NOK 624,000
Equity NOK 527,000
Incorporated 2024
Share capital NOK 30,000

SYVSOVEREN NORGE AS is registered as a limited company in Fredrikstad, Østfold with organisation number 933646351. The business is classified under manufacture of furniture (NACE 31.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Produksjon og salg av funksjonsmøbler til offentlige og private institusjoner som barnehager, skoler, sykehus m.m samt produksjon og salg av beslektede produkter som hører til herunder. Produksjon og salg av merkevaren Syvsoveren.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.9m in revenue and NOK 624,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.9m
Operating profit
NOK 624,000
Equity
NOK 527,000
Est. value
NOK 2.2m

Financial health · 2025

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

Who owns SYVSOVEREN NORGE AS?

WIKA HOLDING AS
SYVSOVEREN NORGE AS
NOK 2.9m rev. · NOK 624,000 profit

SYVSOVEREN NORGE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SYVSOVEREN NORGE AS

Who owns SYVSOVEREN NORGE AS?

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

What is the revenue of SYVSOVEREN NORGE AS?

SYVSOVEREN NORGE AS had revenue of NOK 2.9m in 2025.

Who is the general manager of SYVSOVEREN NORGE AS?

Dan Emil Winsvold is registered as general manager of SYVSOVEREN NORGE AS.

Where is SYVSOVEREN NORGE AS based?

SYVSOVEREN NORGE AS has its business address in Sellebakk.

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.