BIZTRAC BETA
Repair and maintenance of machinery

BOTTEN MASKIN SERVICE AS

Org. no. 930089265 Limited company (AS) Nannestad Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 2.6m
Operating profit NOK 185,000
Equity NOK 376,000
Incorporated 2022
Share capital NOK 120,000

BOTTEN MASKIN SERVICE AS is registered as a limited company in Nannestad, Akershus with organisation number 930089265. The business is classified under repair and maintenance of machinery (NACE 33.120). The company was incorporated in 2022. Registered share capital is NOK 120,000, divided into 1000 shares. The company's stated purpose is: “Reparasjon og vedlikehold av bygg og anleggsmaskiner samt salg/utleie av maskiner og tilhørende delesalg.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.6m in revenue and NOK 185,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.6m
Operating profit
NOK 185,000
Equity
NOK 376,000
Est. value
NOK 506,000

Financial health · 2025

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

Who owns BOTTEN MASKIN SERVICE AS?

LUDVIG ELISON BOTTEN
BOTTEN MASKIN SERVICE AS
NOK 2.6m rev. · NOK 185,000 profit

BOTTEN MASKIN SERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BOTTEN MASKIN SERVICE AS

Who owns BOTTEN MASKIN SERVICE AS?

LUDVIG ELISON BOTTEN is the largest registered owner, with 100.0%.

What is the revenue of BOTTEN MASKIN SERVICE AS?

BOTTEN MASKIN SERVICE AS had revenue of NOK 2.6m in 2025.

Who is the general manager of BOTTEN MASKIN SERVICE AS?

Ludvig Elison Botten is registered as general manager of BOTTEN MASKIN SERVICE AS.

Where is BOTTEN MASKIN SERVICE AS based?

BOTTEN MASKIN SERVICE AS has its business address in Nannestad.

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.