BIZTRAC BETA
Wholesale of clothing and footwear

3X WORKWEAR AS

Org. no. 930079073 Limited company (AS) Nannestad Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 17.1m
Operating profit NOK −4.0m
Equity NOK 3.9m
Incorporated 2022
Employees 14
Share capital NOK 2.5m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−4,0 mill kr).

3X WORKWEAR AS is registered as a limited company in Nannestad, Akershus with organisation number 930079073. The business is classified under wholesale of clothing and footwear (NACE 46.420). The company was incorporated in 2022 and has 14 registered employees. Registered share capital is NOK 2.5m, divided into 25000 shares. The company's stated purpose is: “Engroshandel med klær og skotøy, og salg av samme mot provisjonsinntekter.”. The most recent filed accounts, for the 2024 financial year, show NOK 17.1m in revenue and NOK −4.0m in operating profit.

Key figures · 2024

Revenue
NOK 17.1m
Operating profit
NOK −4.0m
Equity
NOK 3.9m
Est. value
NOK 4.8m

Financial health · 2024

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

Who owns 3X WORKWEAR AS?

BEKKEN 3X AS
3X WORKWEAR AS
NOK 17.1m rev. · NOK −4.0m profit

3X WORKWEAR AS has 1 registered shareholder:

All shareholders and roles →

Group structure

3X WORKWEAR AS er morselskap for 1 datterselskap:

Frequently asked questions about 3X WORKWEAR AS

Who owns 3X WORKWEAR AS?

BEKKEN 3X AS is the largest registered owner, with 100.0%.

What is the revenue of 3X WORKWEAR AS?

3X WORKWEAR AS had revenue of NOK 17.1m in 2024.

Who is the general manager of 3X WORKWEAR AS?

Odin Bekken is registered as general manager of 3X WORKWEAR AS.

Where is 3X WORKWEAR AS based?

3X WORKWEAR AS has its business address in Nannestad.

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.