BIZTRAC BETA
Non-specialised retail sale of predominately food, beverages or tobacco

S.M. Trading A/S

Org. no. 946834580 Limited company (AS) Osterøy Incorporated 1988 Active
Ownership graph ↗
Revenue 2025 NOK 761,000
Operating profit NOK −62,000
Equity NOK 665,000
Incorporated 1988
Share capital NOK 150,000

Signals

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

S.M. Trading A/S is registered as a limited company in Osterøy, Vestland with organisation number 946834580. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 1988. Registered share capital is NOK 150,000, divided into 150 shares. The company's stated purpose is: “Handel og distribusjonsservice.”. The most recent filed accounts, for the 2025 financial year, show NOK 761,000 in revenue and NOK −62,000 in operating profit.

Key figures · 2025

Revenue
NOK 761,000
Operating profit
NOK −62,000
Equity
NOK 665,000
Est. value
NOK 563,000

Financial health · 2025

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

Who owns S.M. Trading A/S?

SIGNHILD VEVLE
S.M. Trading A/S
NOK 761,000 rev. · NOK −62,000 profit

S.M. Trading A/S has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about S.M. Trading A/S

Who owns S.M. Trading A/S?

SIGNHILD VEVLE is the largest registered owner, with 100.0%.

What is the revenue of S.M. Trading A/S?

S.M. Trading A/S had revenue of NOK 761,000 in 2025.

Who is the general manager of S.M. Trading A/S?

Signhild Vevle is registered as general manager of S.M. Trading A/S.

Where is S.M. Trading A/S based?

S.M. Trading A/S has its business address in Valestrandsfossen.

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.