BIZTRAC BETA
Retail sale of clothing

TRONTEX AS

Org. no. 867210652 Limited company (AS) Bærum Incorporated 1993 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −387,000
Equity NOK 61,000
Incorporated 1993
Share capital NOK 100,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−387k kr).
  • Nylig endring 2026-03-10 Adresseendring registrert 2026-03-10.

TRONTEX AS is registered as a limited company in Bærum, Akershus with organisation number 867210652. The business is classified under retail sale of clothing (NACE 47.710). The company was incorporated in 1993. Registered share capital is NOK 100,000. The company's stated purpose is: “Markedsføring og salg av jeans og jeansrelaterte produkter.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −387,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −387,000
Equity
NOK 61,000
Est. value
NOK 77,000

Financial health · 2025

Liquidity
0.02
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 TRONTEX AS?

STIAN TRONSGÅRD
TRONTEX AS
NOK 0 rev. · NOK −387,000 profit

TRONTEX AS has 2 registered shareholders:

All shareholders and roles →

Which companies does TRONTEX AS own?

TRONTEX AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about TRONTEX AS

Who owns TRONTEX AS?

STIAN TRONSGÅRD is the largest registered owner, with 80.0%.

What is the revenue of TRONTEX AS?

TRONTEX AS had revenue of NOK 0 in 2025.

Who is the general manager of TRONTEX AS?

Eilif Tronsgård is registered as general manager of TRONTEX AS.

Where is TRONTEX AS based?

TRONTEX AS has its business address in Sandvika.

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.