biztrac. BETA
COMPANY REGISTER PROFILE
930765783 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Repair and maintenance of motor vehicles

S.M HOLDING AS

Org. no. 930765783 Limited company (AS) Færder Incorporated 2023 Active
Ownership graph ↗
Operating profit NOK −129,000
Equity NOK 29,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

S.M HOLDING AS is registered as a limited company in Færder, Vestfold with organisation number 930765783. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Investering i aksjer og andre selskaper, samt annet som står i forbindelse med dette.”.

Key figures · 2025

Operating profit
NOK −129,000
▼ −21 %
Equity
NOK 29,000
▲ +135 %
Est. value
NOK 842,000

Financial health · 2025

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

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

Who owns S.M HOLDING AS?

S.M HOLDING AS
· NOK −129,000 profit

S.M HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does S.M HOLDING AS own?

S.M HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Group structure

S.M HOLDING AS er morselskap for 1 datterselskap:

Frequently asked questions about S.M HOLDING AS

Who owns S.M HOLDING AS?

Stig Madsen is the largest registered owner, with 100.0%.

Who is the general manager of S.M HOLDING AS?

Stig Madsen is registered as general manager of S.M HOLDING AS.

Where is S.M HOLDING AS based?

S.M HOLDING AS has its business address in Vestskogen.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

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