BIZTRAC BETA
Manufacture of outerwear

SØM & MER AS

Org. no. 918942939 Limited company (AS) Oslo Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 48,000
Operating profit NOK 29,000
Equity NOK −398,000
Incorporated 2017
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−398k kr).

SØM & MER AS is registered as a limited company in Oslo, Oslo with organisation number 918942939. The business is classified under manufacture of outerwear (NACE 14.210). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Skal være nærområdets foretrukne valg for søm og omsøm,samt alt som høres naturlig til dette. Produksjon til teater,scene og film i hele landet.”. The most recent filed accounts, for the 2025 financial year, show NOK 48,000 in revenue and NOK 29,000 in operating profit.

Key figures · 2025

Revenue
NOK 48,000
Operating profit
NOK 29,000
Equity
NOK −398,000
Est. value
NOK 159,000

Financial health · 2024

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

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

Who owns SØM & MER AS?

MARIA DOLORES TORRES
SØM & MER AS
NOK 48,000 rev. · NOK 29,000 profit

SØM & MER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SØM & MER AS

Who owns SØM & MER AS?

MARIA DOLORES TORRES is the largest registered owner, with 100.0%.

What is the revenue of SØM & MER AS?

SØM & MER AS had revenue of NOK 48,000 in 2025.

Who is the general manager of SØM & MER AS?

Maria Dolores Torres is registered as general manager of SØM & MER AS.

Where is SØM & MER AS based?

SØM & MER 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 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.