biztrac. BETA
COMPANY REGISTER PROFILE
984215150 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

SA-TO AS

Org. no. 984215150 Limited company (AS) Nærøysund Incorporated 2002 Active
Ownership graph ↗
Revenue 2025 NOK 257,000
Operating profit NOK 191,000
Equity NOK 130,000
Incorporated 2002
Share capital NOK 130,000

SA-TO AS is registered as a limited company in Nærøysund, Trøndelag with organisation number 984215150. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2002. Registered share capital is NOK 130,000, divided into 1300 shares. The company's stated purpose is: “Drive handel, forvaltning av fast eiendom og løsøre, megling innenfor relevante områder, samt ved aksjer og parter å delta i andre selskaper og virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 257,000 in revenue and NOK 191,000 in operating profit.

Former names: EMMYS SPISERI AS

Key figures · 2025

Revenue
NOK 257,000
▲ +3 %
Operating profit
NOK 191,000
▼ −4 %
Equity
NOK 130,000
▲ +0 %
Est. value
NOK 467,000

Financial health · 2025

Liquidity
1.49
Satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
32.8%
Good
Equity as a share of total capital

Who owns SA-TO AS?

SA-TO AS
NOK 257,000 rev. · NOK 191,000 profit

SA-TO AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SA-TO AS

Who owns SA-TO AS?

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

What is the revenue of SA-TO AS?

SA-TO AS had revenue of NOK 257,000 in 2025.

Who is the general manager of SA-TO AS?

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

Where is SA-TO AS based?

SA-TO 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 03.10.2026.

Report a problem

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