BIZTRAC BETA
Wholesale of other machinery and equipment

SA-TO HOLDING AS

Org. no. 979906706 Limited company (AS) Nærøysund Incorporated 1998 Active
Ownership graph ↗
Operating profit NOK −695,000
Equity NOK 11.1m
Incorporated 1998
Share capital NOK 115,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−695k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

SA-TO HOLDING AS is registered as a limited company in Nærøysund, Trøndelag with organisation number 979906706. The business is classified under wholesale of other machinery and equipment (NACE 46.640). The company was incorporated in 1998. Registered share capital is NOK 115,000, divided into 1150425 shares. The company's stated purpose is: “Ved aksjer og parter å delta i andre selskaper og virksomheter.”.

Key figures · 2024

Operating profit
NOK −695,000
Equity
NOK 11.1m
Est. value
NOK 20.6m

Financial health · 2024

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

Who owns SA-TO HOLDING AS?

SANDVOLLEN INVEST AS
SA-TO HOLDING AS
· NOK −695,000 profit

SA-TO HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does SA-TO HOLDING AS own?

SA-TO HOLDING AS holds stakes in 5 companies:

See the full ownership structure →

Group structure

SA-TO HOLDING AS er morselskap for 1 datterselskap:

Frequently asked questions about SA-TO HOLDING AS

Who owns SA-TO HOLDING AS?

SANDVOLLEN INVEST AS is the largest registered owner, with 64.6%.

Who is the general manager of SA-TO HOLDING AS?

Ole Andreas Holm is registered as general manager of SA-TO HOLDING AS.

Where is SA-TO HOLDING AS based?

SA-TO HOLDING AS has its business address in Kolvereid.

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.