biztrac. BETA
COMPANY REGISTER PROFILE
923544941 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Wholesale of textiles

SIDSERK AS

Org. no. 923544941 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 4.6m
Operating profit NOK 150,000
Equity NOK 482,000
Incorporated 2019
Employees 6
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-05-31 Adresseendring registrert 2026-05-31.

SIDSERK AS is registered as a limited company in Oslo, Oslo with organisation number 923544941. The business is classified under wholesale of textiles (NACE 46.410). The company was incorporated in 2019 and has 6 registered employees. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Produksjon og salg, engros og detalj av husflids- og utstyr og tekstiler.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.6m in revenue and NOK 150,000 in operating profit.

Former names: NORGES BUNADSHÅNDVERKERE AS

Key figures · 2025

Revenue
NOK 4.6m
▲ +25 %
Operating profit
NOK 150,000
▼ −33 %
Equity
NOK 482,000
▲ +31 %
Est. value
NOK 853,000

Financial health · 2025

Liquidity
1.73
Good
Current assets ÷ current liabilities
Profitability
15.0%
Very good
Return on total assets
Solidity
43.1%
Very good
Equity as a share of total capital

Who owns SIDSERK AS?

SIDSERK AS
NOK 4.6m rev. · NOK 150,000 profit

SIDSERK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SIDSERK AS

Who owns SIDSERK AS?

Siri Sveen Haaland is the largest registered owner, with 100.0%.

What is the revenue of SIDSERK AS?

SIDSERK AS had revenue of NOK 4.6m in 2025.

Who is the general manager of SIDSERK AS?

Siri Sveen Haaland is registered as general manager of SIDSERK AS.

Where is SIDSERK AS based?

SIDSERK AS has its business address in Oslo.

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.