biztrac. BETA
COMPANY REGISTER PROFILE
920595324 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
In liquidation UPDATED 03.10.2026
⚠WM AUTO AS is registered as “In liquidation” with the Brønnøysund Register Centre.
Retail sale of motor vehicles

WM AUTO AS

Org. no. 920595324 Limited company (AS) Nes Incorporated 2018 In liquidation
Revenue 2025 NOK 675,000
Operating profit NOK −16,000
Equity NOK −1.1m
Incorporated 2018
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1,1 mill kr).

WM AUTO AS is registered as a limited company in Nes, Akershus with organisation number 920595324. The business is classified under retail sale of motor vehicles (NACE 47.810). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Kjøp og salg av nye og brukte biler.”. The most recent filed accounts, for the 2025 financial year, show NOK 675,000 in revenue and NOK −16,000 in operating profit.

Former names: WP BYGGFORNYER AS, WP MØBEL & BYGGFORNYER AS

Key figures · 2025

Revenue
NOK 675,000
▼ −18 %
Operating profit
NOK −16,000
▲ +90 %
Equity
NOK −1.1m
▼ −116 %

Financial health · 2025

Liquidity
0.10
Not satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
-1271.3%
Weak
Equity as a share of total capital

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

Who owns WM AUTO AS?

WM AUTO AS
NOK 675,000 rev. · NOK −16,000 profit

WM AUTO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about WM AUTO AS

Who owns WM AUTO AS?

Svein Willy Pettersen is the largest registered owner, with 100.0%.

What is the revenue of WM AUTO AS?

WM AUTO AS had revenue of NOK 675,000 in 2025.

Where is WM AUTO AS based?

WM AUTO AS has its business address in Vormsund.

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.