BIZTRAC BETA
Retail sale of textiles

BERNINA SØM OG STRIKK AS

Org. no. 976047826 Limited company (AS) Skien Incorporated 1996 Active
Ownership graph ↗
Revenue 2025 NOK 2.6m
Operating profit NOK −245,000
Equity NOK 808,000
Incorporated 1996
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−245k kr).

BERNINA SØM OG STRIKK AS is registered as a limited company in Skien, Telemark with organisation number 976047826. The business is classified under retail sale of textiles (NACE 47.510). The company was incorporated in 1996. Registered share capital is NOK 100,000, divided into 200 shares. The company's stated purpose is: “Selge symaskiner, sytilbehør og garn. Dessuten har selskapet egen systue.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.6m in revenue and NOK −245,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.6m
Operating profit
NOK −245,000
Equity
NOK 808,000
Est. value
NOK 1.2m

Financial health · 2025

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

Who owns BERNINA SØM OG STRIKK AS?

ANNE EIKLID GRAN
BERNINA SØM OG STRIKK AS
NOK 2.6m rev. · NOK −245,000 profit

BERNINA SØM OG STRIKK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BERNINA SØM OG STRIKK AS

Who owns BERNINA SØM OG STRIKK AS?

ANNE EIKLID GRAN is the largest registered owner, with 100.0%.

What is the revenue of BERNINA SØM OG STRIKK AS?

BERNINA SØM OG STRIKK AS had revenue of NOK 2.6m in 2025.

Who is the general manager of BERNINA SØM OG STRIKK AS?

Anne Eiklid Gran is registered as general manager of BERNINA SØM OG STRIKK AS.

Where is BERNINA SØM OG STRIKK AS based?

BERNINA SØM OG STRIKK AS has its business address in Skien.

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.