BIZTRAC BETA
Wholesale of agricultural machinery, equipment and supplies

WEAR MASKIN AS

Org. no. 911875292 Limited company (AS) Asker Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 10.7m
Operating profit NOK 507,000
Equity NOK 668,000
Incorporated 2013
Share capital NOK 30,000

WEAR MASKIN AS is registered as a limited company in Asker, Akershus with organisation number 911875292. The business is classified under wholesale of agricultural machinery, equipment and supplies (NACE 46.610). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Handel, utleie og reparasjoner av maskiner og utstyr og alt som hører med i den forbindelse. Det skal være anledning til å eie aksjer og andeler i andre selskaper. Det skal være anledning til å drive med fremleie av lokaler.”. The most recent filed accounts, for the 2024 financial year, show NOK 10.7m in revenue and NOK 507,000 in operating profit.

Key figures · 2024

Revenue
NOK 10.7m
Operating profit
NOK 507,000
Equity
NOK 668,000
Est. value
NOK 2.3m

Financial health · 2024

Liquidity
1.34
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
26.5%
Good
Equity as a share of total capital

Who owns WEAR MASKIN AS?

SAGFOSS HOLDING AS
WEAR MASKIN AS
NOK 10.7m rev. · NOK 507,000 profit

WEAR MASKIN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about WEAR MASKIN AS

Who owns WEAR MASKIN AS?

SAGFOSS HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of WEAR MASKIN AS?

WEAR MASKIN AS had revenue of NOK 10.7m in 2024.

Who is the general manager of WEAR MASKIN AS?

Stein Wøien is registered as general manager of WEAR MASKIN AS.

Where is WEAR MASKIN AS based?

WEAR MASKIN AS has its business address in Røyken.

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.