biztrac. BETA
COMPANY REGISTER PROFILE
917998396 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Wholesale of watches and jewellery

TIME TREND AS

Org. no. 917998396 Limited company (AS) Oslo Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −73,000
Equity NOK 103.9m
Incorporated 2016
Share capital NOK 4.3m

Signals

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

TIME TREND AS is registered as a limited company in Oslo, Oslo with organisation number 917998396. The business is classified under wholesale of watches and jewellery (NACE 46.480). The company was incorporated in 2016. Registered share capital is NOK 4.3m, divided into 4300000 shares. The company's stated purpose is: “Handel og agenturvirksomhet, drift og deltagelse i andre virksomheter som aksjonær eller på annen måte.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −73,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −73,000
▼ −4 %
Equity
NOK 103.9m
▼ −0 %
Est. value
NOK 129.9m

Financial health · 2025

Liquidity
34.40
Very good
Current assets ÷ current liabilities
Profitability
-0.5%
Not satisfactory
Return on total assets
Solidity
99.9%
Very good
Equity as a share of total capital

Who owns TIME TREND AS?

TIME TREND AS
NOK 0 rev. · NOK −73,000 profit

TIME TREND AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TIME TREND AS own?

TIME TREND AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about TIME TREND AS

Who owns TIME TREND AS?

ARIEL HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of TIME TREND AS?

TIME TREND AS had revenue of NOK 0 in 2025.

Where is TIME TREND AS based?

TIME TREND 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.