BIZTRAC BETA
Activities of agents involved in the wholesale of other particular products

WALGERMO AS

Org. no. 934860470 Limited company (AS) Ålesund Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 3.2m
Operating profit NOK 553,000
Equity NOK 526,000
Incorporated 2025
Share capital NOK 100,000

WALGERMO AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 934860470. The business is classified under activities of agents involved in the wholesale of other particular products (NACE 46.180). The company was incorporated in 2025. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.2m in revenue and NOK 553,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.2m
Operating profit
NOK 553,000
Equity
NOK 526,000
Est. value
NOK 2.0m

Financial health · 2025

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

Who owns WALGERMO AS?

LEIF HELGE WALGERMO
WALGERMO AS
NOK 3.2m rev. · NOK 553,000 profit

WALGERMO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about WALGERMO AS

Who owns WALGERMO AS?

LEIF HELGE WALGERMO is the largest registered owner, with 100.0%.

What is the revenue of WALGERMO AS?

WALGERMO AS had revenue of NOK 3.2m in 2025.

Who is the general manager of WALGERMO AS?

Leif Helge Walgermo is registered as general manager of WALGERMO AS.

Where is WALGERMO AS based?

WALGERMO AS has its business address in Ørskog.

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.