BIZTRAC BETA
Uoppgitt

TEASK HOLDING AS

Org. no. 933697657 Limited company (AS) Øvre Eiker Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −7,000
Equity NOK 10.5m
Incorporated 2024
Share capital NOK 30,000

Signals

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

TEASK HOLDING AS is registered as a limited company in Øvre Eiker, Buskerud with organisation number 933697657. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Investere i, eie, forvalte og selge andeler i andre selskaper, samt å utøve aktiviteter som er komplementær til disse, inkludert, men ikke begrenset til, finansiell rådgivning og forvaltning.”. 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 10.5m
Est. value
NOK 12.0m

Financial health · 2025

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

Who owns TEASK HOLDING AS?

TONJE ESPSETH ASK
TEASK HOLDING AS
NOK 0 rev. · NOK −7,000 profit

TEASK HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TEASK HOLDING AS own?

TEASK HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TEASK HOLDING AS

Who owns TEASK HOLDING AS?

TONJE ESPSETH ASK is the largest registered owner, with 100.0%.

What is the revenue of TEASK HOLDING AS?

TEASK HOLDING AS had revenue of NOK 0 in 2025.

Where is TEASK HOLDING AS based?

TEASK HOLDING AS has its business address in Hokksund.

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.