BIZTRAC BETA
Photographic activities

S A TOLLÅS AS

Org. no. 916798687 Limited company (AS) Ålesund Incorporated 1974 Active
Ownership graph ↗
Revenue 2024 NOK 165,000
Operating profit NOK −189,000
Equity NOK 279,000
Incorporated 1974
Share capital NOK 212,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−189k kr).

S A TOLLÅS AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 916798687. The business is classified under photographic activities (NACE 74.200). The company was incorporated in 1974. Registered share capital is NOK 212,000, divided into 212 shares. The company's stated purpose is: “Reklame- og fotografitjenester, natur- og landskapsfotografering, investering i aksjer og andre verdipapirer, utleie av bobiler, samt oppdrett og avl av akvariefisk for salg.”. The most recent filed accounts, for the 2024 financial year, show NOK 165,000 in revenue and NOK −189,000 in operating profit.

Key figures · 2024

Revenue
NOK 165,000
Operating profit
NOK −189,000
Equity
NOK 279,000
Est. value
NOK 454,000

Financial health · 2024

Liquidity
-0.79
Not 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 S A TOLLÅS AS?

SVEIN-ARE TOLLÅS
S A TOLLÅS AS
NOK 165,000 rev. · NOK −189,000 profit

S A TOLLÅS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about S A TOLLÅS AS

Who owns S A TOLLÅS AS?

SVEIN-ARE TOLLÅS is the largest registered owner, with 100.0%.

What is the revenue of S A TOLLÅS AS?

S A TOLLÅS AS had revenue of NOK 165,000 in 2024.

Who is the general manager of S A TOLLÅS AS?

Svein-Are Tollås is registered as general manager of S A TOLLÅS AS.

Where is S A TOLLÅS AS based?

S A TOLLÅS AS has its business address in Ålesund.

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.