BIZTRAC BETA
Repair and maintenance of machinery

WALSTAD MASKINSERVICE AS

Org. no. 911749807 Limited company (AS) Nes Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 393,000
Operating profit NOK 179,000
Equity NOK 944,000
Incorporated 2013
Share capital NOK 100,000

WALSTAD MASKINSERVICE AS is registered as a limited company in Nes, Akershus with organisation number 911749807. The business is classified under repair and maintenance of machinery (NACE 33.120). The company was incorporated in 2013. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Reparasjon av anleggs- og landbruksmaskiner, og salg av maskiner og deler. I tillegg hva styret finner interessant for selskapet.”. The most recent filed accounts, for the 2025 financial year, show NOK 393,000 in revenue and NOK 179,000 in operating profit.

Key figures · 2025

Revenue
NOK 393,000
Operating profit
NOK 179,000
Equity
NOK 944,000
Est. value
NOK 1.2m

Financial health · 2025

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

Who owns WALSTAD MASKINSERVICE AS?

RAGNAR WALSTAD
WALSTAD MASKINSERVICE AS
NOK 393,000 rev. · NOK 179,000 profit

WALSTAD MASKINSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about WALSTAD MASKINSERVICE AS

Who owns WALSTAD MASKINSERVICE AS?

RAGNAR WALSTAD is the largest registered owner, with 100.0%.

What is the revenue of WALSTAD MASKINSERVICE AS?

WALSTAD MASKINSERVICE AS had revenue of NOK 393,000 in 2025.

Who is the general manager of WALSTAD MASKINSERVICE AS?

Ragnar Walstad is registered as general manager of WALSTAD MASKINSERVICE AS.

Where is WALSTAD MASKINSERVICE AS based?

WALSTAD MASKINSERVICE AS has its business address in Årnes.

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.