BIZTRAC BETA
Uoppgitt

TONSAN HOLDING AS

Org. no. 934178130 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −2,000
Equity NOK 451,000
Incorporated 2024
Share capital NOK 40,000

Signals

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

TONSAN HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 934178130. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 40,000, divided into 40000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −2,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −2,000
Equity
NOK 451,000
Est. value
NOK 325,000

Financial health · 2025

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

Who owns TONSAN HOLDING AS?

TONE SANDØY
TONSAN HOLDING AS
NOK 0 rev. · NOK −2,000 profit

TONSAN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TONSAN HOLDING AS own?

TONSAN HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about TONSAN HOLDING AS

Who owns TONSAN HOLDING AS?

TONE SANDØY is the largest registered owner, with 100.0%.

What is the revenue of TONSAN HOLDING AS?

TONSAN HOLDING AS had revenue of NOK 0 in 2025.

Where is TONSAN HOLDING AS based?

TONSAN HOLDING AS has its business address in Oslo.

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.