BIZTRAC BETA
Retail sale of clothing

PAUL TEKSTIL AS

Org. no. 997117093 Limited company (AS) Holmestrand Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 5.6m
Operating profit NOK −4,000
Equity NOK −450,000
Incorporated 2011
Employees 6
Share capital NOK 100,000

Signals

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

PAUL TEKSTIL AS is registered as a limited company in Holmestrand, Vestfold with organisation number 997117093. The business is classified under retail sale of clothing (NACE 47.710). The company was incorporated in 2011 and has 6 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Import og detaljsalg av klær.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.6m in revenue and NOK −4,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.6m
Operating profit
NOK −4,000
Equity
NOK −450,000

Financial health · 2025

Liquidity
1.41
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-32.7%
Weak
Equity as a share of total capital

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

Who owns PAUL TEKSTIL AS?

SUSHIL KANTA
PAUL TEKSTIL AS
NOK 5.6m rev. · NOK −4,000 profit

PAUL TEKSTIL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PAUL TEKSTIL AS

Who owns PAUL TEKSTIL AS?

SUSHIL KANTA is the largest registered owner, with 100.0%.

What is the revenue of PAUL TEKSTIL AS?

PAUL TEKSTIL AS had revenue of NOK 5.6m in 2025.

Who is the general manager of PAUL TEKSTIL AS?

Sushil Kanta is registered as general manager of PAUL TEKSTIL AS.

Where is PAUL TEKSTIL AS based?

PAUL TEKSTIL AS has its business address in Holmestrand.

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.