BIZTRAC BETA
Uoppgitt

T.S.K HOLDING AS

Org. no. 933175022 Limited company (AS) Ålesund Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 45,000
Operating profit NOK 21,000
Equity NOK 86,000
Incorporated 2024
Share capital NOK 30,000

T.S.K HOLDING AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 933175022. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i, eie, forvalte og selge andeler i andre selskaper, samt å utøve aktiviteter som er komplementære til disse, inkludert, men ikke begrenset til, finansiell rådgivning og forvaltning.”. The most recent filed accounts, for the 2025 financial year, show NOK 45,000 in revenue and NOK 21,000 in operating profit.

Key figures · 2025

Revenue
NOK 45,000
Operating profit
NOK 21,000
Equity
NOK 86,000
Est. value
NOK 99,000

Financial health · 2025

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

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

Who owns T.S.K HOLDING AS?

TERJE STEINSBU KJØLSØY
T.S.K HOLDING AS
NOK 45,000 rev. · NOK 21,000 profit

T.S.K HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does T.S.K HOLDING AS own?

T.S.K HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about T.S.K HOLDING AS

Who owns T.S.K HOLDING AS?

TERJE STEINSBU KJØLSØY is the largest registered owner, with 100.0%.

What is the revenue of T.S.K HOLDING AS?

T.S.K HOLDING AS had revenue of NOK 45,000 in 2025.

Where is T.S.K HOLDING AS based?

T.S.K HOLDING AS has its business address in Ålesund.

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.