BIZTRAC BETA
Wholesale of textiles

UNIPRO TEXSTYLE AS

Org. no. 921150687 Limited company (AS) Nordre Follo Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 4.0m
Operating profit NOK −163,000
Equity NOK −209,000
Incorporated 2018
Share capital NOK 30,000

Signals

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

UNIPRO TEXSTYLE AS is registered as a limited company in Nordre Follo, Akershus with organisation number 921150687. The business is classified under wholesale of textiles (NACE 46.410). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Handel med tekstiler og innredning.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.0m in revenue and NOK −163,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.0m
Operating profit
NOK −163,000
Equity
NOK −209,000

Financial health · 2025

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

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

Who owns UNIPRO TEXSTYLE AS?

Lars Magnus Helander
UNIPRO TEXSTYLE AS
NOK 4.0m rev. · NOK −163,000 profit

UNIPRO TEXSTYLE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about UNIPRO TEXSTYLE AS

Who owns UNIPRO TEXSTYLE AS?

Lars Magnus Helander is the largest registered owner, with 60.0%.

What is the revenue of UNIPRO TEXSTYLE AS?

UNIPRO TEXSTYLE AS had revenue of NOK 4.0m in 2025.

Who is the general manager of UNIPRO TEXSTYLE AS?

Margaret Martinsen is registered as general manager of UNIPRO TEXSTYLE AS.

Where is UNIPRO TEXSTYLE AS based?

UNIPRO TEXSTYLE AS has its business address in Oppegård.

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.