BIZTRAC BETA
Manufacture of outerwear

SØMSALONGEN AS

Org. no. 922036772 Limited company (AS) Holmestrand Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 69,000
Operating profit NOK −45,000
Equity NOK 15,000
Incorporated 2018
Share capital NOK 30,000

Signals

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

SØMSALONGEN AS is registered as a limited company in Holmestrand, Vestfold with organisation number 922036772. The business is classified under manufacture of outerwear (NACE 14.210). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Søm og brodering av bunad poser, søm av hjemme tekstiler, klær, reparasjoner, kjøp/salg av klær.”. The most recent filed accounts, for the 2024 financial year, show NOK 69,000 in revenue and NOK −45,000 in operating profit.

Key figures · 2024

Revenue
NOK 69,000
Operating profit
NOK −45,000
Equity
NOK 15,000
Est. value
NOK 45,000

Financial health · 2024

Liquidity
1.02
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
14.2%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns SØMSALONGEN AS?

INGRID BJØRKLI KARLSEN
SØMSALONGEN AS
NOK 69,000 rev. · NOK −45,000 profit

SØMSALONGEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SØMSALONGEN AS

Who owns SØMSALONGEN AS?

INGRID BJØRKLI KARLSEN is the largest registered owner, with 100.0%.

What is the revenue of SØMSALONGEN AS?

SØMSALONGEN AS had revenue of NOK 69,000 in 2024.

Who is the general manager of SØMSALONGEN AS?

Ingrid Bjørkli Karlsen is registered as general manager of SØMSALONGEN AS.

Where is SØMSALONGEN AS based?

SØMSALONGEN AS has its business address in Sande I Vestfold.

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.