BIZTRAC BETA
COMPANY REGISTER PROFILE
930980455 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

TOSO AS

Org. no. 930980455 Limited company (AS) Sokndal Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −78,000
Equity NOK 23.4m
Incorporated 2022
Share capital NOK 1.3m

Signals

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

TOSO AS is registered as a limited company in Sokndal, Rogaland with organisation number 930980455. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 1.3m, divided into 1 shares. The company's stated purpose is: “Investering i eiendom, aksjer og andre verdipapirer.”.

Key figures · 2025

Operating profit
NOK −78,000
Equity
NOK 23.4m
Est. value
NOK 28.1m

Financial health · 2025

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

Who owns TOSO AS?

TOSO AS
· NOK −78,000 profit

TOSO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TOSO AS

Who owns TOSO AS?

TORALF HÆREM NYHEIM is the largest registered owner, with 100.0%.

Who is the general manager of TOSO AS?

Toralf Hærem Nyheim is registered as general manager of TOSO AS.

Where is TOSO AS based?

TOSO AS has its business address in Hauge I Dalane.

Property

Business address Gamleveien 24, 4380 Hauge I Dalane
Cadastral unit 1111-56/255/0/0
Building Annen forretningsbygning · 4 units

8 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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

Report a problem

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