BIZTRAC BETA
Rental and leasing of other machinery, equipment and tangible goods n.e.c.

VIDAR BOTN AS

Org. no. 935366135 Limited company (AS) Ålesund Incorporated 1984 Active
Ownership graph ↗
Revenue 2025 NOK 35,000
Operating profit NOK 10,000
Equity NOK 1.5m
Incorporated 1984
Share capital NOK 102,000

VIDAR BOTN AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 935366135. The business is classified under rental and leasing of other machinery, equipment and tangible goods n.e.c. (NACE 77.390). The company was incorporated in 1984. Registered share capital is NOK 102,000, divided into 120 shares. The company's stated purpose is: “Å drive blikkenslagerverksted, oppføring av stålbygg og produksjon.”. The most recent filed accounts, for the 2025 financial year, show NOK 35,000 in revenue and NOK 10,000 in operating profit.

Key figures · 2025

Revenue
NOK 35,000
Operating profit
NOK 10,000
Equity
NOK 1.5m
Est. value
NOK 794,000

Financial health · 2025

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

Who owns VIDAR BOTN AS?

PROSESS CONSULT AS
VIDAR BOTN AS
NOK 35,000 rev. · NOK 10,000 profit

VIDAR BOTN AS has 3 registered shareholders:

All shareholders and roles →

Which companies does VIDAR BOTN AS own?

VIDAR BOTN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about VIDAR BOTN AS

Who owns VIDAR BOTN AS?

PROSESS CONSULT AS is the largest registered owner, with 50.0%.

What is the revenue of VIDAR BOTN AS?

VIDAR BOTN AS had revenue of NOK 35,000 in 2025.

Who is the general manager of VIDAR BOTN AS?

Vidar Botn is registered as general manager of VIDAR BOTN AS.

Where is VIDAR BOTN AS based?

VIDAR BOTN AS has its business address in Ålesund.

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.