BIZTRAC BETA
Uoppgitt

TIC HOLDING AS

Org. no. 932558866 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −7,000
Equity NOK −120,000
Incorporated 2023
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−120k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−7k kr).

TIC HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 932558866. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investeringsvirksomhet, herunder investeringer i aksjer og andre verdipapirer, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −7,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −7,000
Equity
NOK −120,000

Financial health · 2025

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

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

Who owns TIC HOLDING AS?

Torsten Stangeland Thune
TIC HOLDING AS
NOK 0 rev. · NOK −7,000 profit

TIC HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TIC HOLDING AS own?

TIC HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TIC HOLDING AS

Who owns TIC HOLDING AS?

Torsten Stangeland Thune is the largest registered owner, with 100.0%.

What is the revenue of TIC HOLDING AS?

TIC HOLDING AS had revenue of NOK 0 in 2025.

Where is TIC HOLDING AS based?

TIC 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.