BIZTRAC BETA
Rental and operating of own or leased real estate

THORSON HOLDING AS

Org. no. 990343543 Limited company (AS) Etne Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −12,000
Equity NOK 516,000
Incorporated 2006
Share capital NOK 100,000

Signals

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

THORSON HOLDING AS is registered as a limited company in Etne, Vestland with organisation number 990343543. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2006. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Å eie og drifte næringsvirksomhet og deler av virksomhet, investering i aksjer og fast eiendom samt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −12,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −12,000
Equity
NOK 516,000
Est. value
NOK 471,000

Financial health · 2025

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

Who owns THORSON HOLDING AS?

ØYVIND THORSON
THORSON HOLDING AS
NOK 0 rev. · NOK −12,000 profit

THORSON HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does THORSON HOLDING AS own?

THORSON HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about THORSON HOLDING AS

Who owns THORSON HOLDING AS?

ØYVIND THORSON is the largest registered owner, with 100.0%.

What is the revenue of THORSON HOLDING AS?

THORSON HOLDING AS had revenue of NOK 0 in 2025.

Where is THORSON HOLDING AS based?

THORSON HOLDING AS has its business address in Etne.

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.