BIZTRAC BETA
Retail sale of clothing

TIMI HOLDING AS

Org. no. 988649813 Limited company (AS) Frogn Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −46,000
Equity NOK 1.5m
Incorporated 2005
Share capital NOK 608,000

Signals

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

TIMI HOLDING AS is registered as a limited company in Frogn, Akershus with organisation number 988649813. The business is classified under retail sale of clothing (NACE 47.710). The company was incorporated in 2005. Registered share capital is NOK 608,000, divided into 3800 shares. The company's stated purpose is: “Kjøp, salg, utvikling, utleie og drift av fast eiendom og andre driftsaktiva, samt å foreta investeringer i aksjer og andeler i andre virksomheter med samme eller lignende formål og annen virksomhet som hører naturlig hertil.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −46,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −46,000
Equity
NOK 1.5m
Est. value
NOK 3.7m

Financial health · 2025

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

Who owns TIMI HOLDING AS?

RANDI MELBY
TIMI HOLDING AS
NOK 0 rev. · NOK −46,000 profit

TIMI HOLDING AS has 3 registered shareholders:

All shareholders and roles →

Which companies does TIMI HOLDING AS own?

TIMI HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about TIMI HOLDING AS

Who owns TIMI HOLDING AS?

RANDI MELBY is the largest registered owner, with 50.5%.

What is the revenue of TIMI HOLDING AS?

TIMI HOLDING AS had revenue of NOK 0 in 2025.

Where is TIMI HOLDING AS based?

TIMI HOLDING AS has its business address in Drøbak.

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.