BIZTRAC BETA
Wholesale of clothing and footwear

STAUT ARBEIDSKLÆR AS

Org. no. 916069685 Limited company (AS) Lillestrøm Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 45.1m
Operating profit NOK 2.2m
Equity NOK 9.1m
Incorporated 2015
Employees 11
Share capital NOK 100,000

STAUT ARBEIDSKLÆR AS is registered as a limited company in Lillestrøm, Akershus with organisation number 916069685. The business is classified under wholesale of clothing and footwear (NACE 46.420). The company was incorporated in 2015 and has 11 registered employees. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Import/eksport, salg av handelsvarer innen arbeidsklær, verneutstyr og tilhørende produkter, rådgivning og kurs innenfor samme segment.”. The most recent filed accounts, for the 2025 financial year, show NOK 45.1m in revenue and NOK 2.2m in operating profit.

Key figures · 2025

Revenue
NOK 45.1m
Operating profit
NOK 2.2m
Equity
NOK 9.1m
Est. value
NOK 13.6m

Financial health · 2025

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

Who owns STAUT ARBEIDSKLÆR AS?

PERSEN INVEST AS
STAUT ARBEIDSKLÆR AS
NOK 45.1m rev. · NOK 2.2m profit

STAUT ARBEIDSKLÆR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STAUT ARBEIDSKLÆR AS

Who owns STAUT ARBEIDSKLÆR AS?

PERSEN INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of STAUT ARBEIDSKLÆR AS?

STAUT ARBEIDSKLÆR AS had revenue of NOK 45.1m in 2025.

Who is the general manager of STAUT ARBEIDSKLÆR AS?

Anders Persvangen is registered as general manager of STAUT ARBEIDSKLÆR AS.

Where is STAUT ARBEIDSKLÆR AS based?

STAUT ARBEIDSKLÆR AS has its business address in Skjetten.

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.