BIZTRAC BETA
Other captive investment companies

THINNITUS HOLDING AS

Org. no. 917583072 Limited company (AS) Bergen Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −3,000
Equity NOK 95,000
Incorporated 2016
Share capital NOK 30,000

Signals

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

THINNITUS HOLDING AS is registered as a limited company in Bergen, Vestland with organisation number 917583072. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Eie aksjer i andre selskaper, samt å forvalte eierinteressene i disse.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −3,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −3,000
Equity
NOK 95,000
Est. value
NOK 400,000

Financial health · 2025

Liquidity
0.95
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
47.4%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns THINNITUS HOLDING AS?

ANDERS SKAGE THINN
THINNITUS HOLDING AS
NOK 0 rev. · NOK −3,000 profit

THINNITUS HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does THINNITUS HOLDING AS own?

THINNITUS HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about THINNITUS HOLDING AS

Who owns THINNITUS HOLDING AS?

ANDERS SKAGE THINN is the largest registered owner, with 100.0%.

What is the revenue of THINNITUS HOLDING AS?

THINNITUS HOLDING AS had revenue of NOK 0 in 2025.

Where is THINNITUS HOLDING AS based?

THINNITUS HOLDING AS has its business address in Bergen.

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.