biztrac. BETA
COMPANY REGISTER PROFILE
891081642 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Retail sale of clothing

VARNAVEIEN TEKSTIL AS

Org. no. 891081642 Limited company (AS) Moss Incorporated 2007 Active
Ownership graph ↗
Revenue 2025 NOK 8.8m
Operating profit NOK 191,000
Equity NOK 3.0m
Incorporated 2007
Share capital NOK 100,000

VARNAVEIEN TEKSTIL AS is registered as a limited company in Moss, Østfold with organisation number 891081642. The business is classified under retail sale of clothing (NACE 47.710). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Handel innen klær, manufaktur, samt investere i aksjer mv. samt hva herved måtte stå i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 8.8m in revenue and NOK 191,000 in operating profit.

Key figures · 2025

Revenue
NOK 8.8m
▼ −10 %
Operating profit
NOK 191,000
▼ −76 %
Equity
NOK 3.0m
▲ +7 %
Est. value
NOK 3.1m

Financial health · 2025

Liquidity
3.02
Very good
Current assets ÷ current liabilities
Profitability
5.4%
Weak
Return on total assets
Solidity
66.9%
Very good
Equity as a share of total capital

Who owns VARNAVEIEN TEKSTIL AS?

VARNAVEIEN TEKSTIL AS
NOK 8.8m rev. · NOK 191,000 profit

VARNAVEIEN TEKSTIL AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about VARNAVEIEN TEKSTIL AS

Who owns VARNAVEIEN TEKSTIL AS?

Lene Biancha Ågesen is the largest registered owner, with 50.0%.

What is the revenue of VARNAVEIEN TEKSTIL AS?

VARNAVEIEN TEKSTIL AS had revenue of NOK 8.8m in 2025.

Who is the general manager of VARNAVEIEN TEKSTIL AS?

Andrè Forsethlund Andersen is registered as general manager of VARNAVEIEN TEKSTIL AS.

Where is VARNAVEIEN TEKSTIL AS based?

VARNAVEIEN TEKSTIL AS has its business address in Moss.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

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