BIZTRAC BETA
Activities of agents involved in the wholesale of textiles, clothing, fur, footwear and leather goods

HAGTEX AS

Org. no. 966357797 Limited company (AS) Oslo Incorporated 1993 Active
Ownership graph ↗
Revenue 2025 NOK 260,000
Operating profit NOK −949
Equity NOK 155,000
Incorporated 1993
Share capital NOK 30,000

Signals

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

HAGTEX AS is registered as a limited company in Oslo, Oslo with organisation number 966357797. The business is classified under activities of agents involved in the wholesale of textiles, clothing, fur, footwear and leather goods (NACE 46.160). The company was incorporated in 1993. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Handels-, agentur- samt konsulentvirksomhet innen interiørbransjen, samt dertil hørende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 260,000 in revenue and NOK −949 in operating profit.

Key figures · 2025

Revenue
NOK 260,000
Operating profit
NOK −949
Equity
NOK 155,000
Est. value
NOK 158,000

Financial health · 2025

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

Who owns HAGTEX AS?

CATHRINE ADVOCAAT HVIDE
HAGTEX AS
NOK 260,000 rev. · NOK −949 profit

HAGTEX AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HAGTEX AS

Who owns HAGTEX AS?

CATHRINE ADVOCAAT HVIDE is the largest registered owner, with 100.0%.

What is the revenue of HAGTEX AS?

HAGTEX AS had revenue of NOK 260,000 in 2025.

Who is the general manager of HAGTEX AS?

Cathrine Advocaat Hvide is registered as general manager of HAGTEX AS.

Where is HAGTEX AS based?

HAGTEX 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 15.06.2026.

Report a problem

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