BIZTRAC BETA
Retail sale of textiles

STRIKKEMANI AS

Org. no. 922737398 Limited company (AS) Sandnes Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 4.5m
Operating profit NOK −268,000
Equity NOK 125,000
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−268k kr).

STRIKKEMANI AS is registered as a limited company in Sandnes, Rogaland with organisation number 922737398. The business is classified under retail sale of textiles (NACE 47.510). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen strikking og håndarbeid og annet som naturlig sammenfaller med dette, samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.5m in revenue and NOK −268,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.5m
Operating profit
NOK −268,000
Equity
NOK 125,000
Est. value
NOK 1.5m

Financial health · 2024

Liquidity
0.38
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
7.9%
Weak
Equity as a share of total capital

Who owns STRIKKEMANI AS?

INGUNN HOLKESTAD BERGQUIST
STRIKKEMANI AS
NOK 4.5m rev. · NOK −268,000 profit

STRIKKEMANI AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about STRIKKEMANI AS

Who owns STRIKKEMANI AS?

INGUNN HOLKESTAD BERGQUIST is the largest registered owner, with 51.0%.

What is the revenue of STRIKKEMANI AS?

STRIKKEMANI AS had revenue of NOK 4.5m in 2024.

Who is the general manager of STRIKKEMANI AS?

Ingunn Holkestad Bergquist is registered as general manager of STRIKKEMANI AS.

Where is STRIKKEMANI AS based?

STRIKKEMANI AS has its business address in Sandnes.

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.