BIZTRAC BETA
Business and other management consultancy activities

TIMETO AS

Org. no. 989239449 Limited company (AS) Tønsberg Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 3,000
Operating profit NOK −21,000
Equity NOK −87,000
Incorporated 2005
Share capital NOK 100,000

Signals

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

TIMETO AS is registered as a limited company in Tønsberg, Vestfold with organisation number 989239449. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 1 shares. The company's stated purpose is: “Konsulent- og investeringsvirksomhet, herunder å eie andeler i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 3,000 in revenue and NOK −21,000 in operating profit.

Key figures · 2025

Revenue
NOK 3,000
Operating profit
NOK −21,000
Equity
NOK −87,000

Financial health · 2025

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

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

Who owns TIMETO AS?

Thomas De Vries
TIMETO AS
NOK 3,000 rev. · NOK −21,000 profit

TIMETO AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TIMETO AS own?

TIMETO AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TIMETO AS

Who owns TIMETO AS?

Thomas De Vries is the largest registered owner, with 100.0%.

What is the revenue of TIMETO AS?

TIMETO AS had revenue of NOK 3,000 in 2025.

Where is TIMETO AS based?

TIMETO AS has its business address in Tolvsrød.

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.