biztrac. BETA
COMPANY REGISTER PROFILE
971130202 ORG. NO. 2025 ACCOUNTS 12 SECTIONS
Active UPDATED 03.10.2026
Construction of residential and non-residential buildings

BOTN MASKIN AS

Org. no. 971130202 Limited company (AS) Alstahaug Incorporated 1994 Active
Ownership graph ↗
Revenue 2025 NOK 14.1m
Operating profit NOK 355,000
Equity NOK 4.7m
Incorporated 1994
Share capital NOK 100,000

BOTN MASKIN AS is registered as a limited company in Alstahaug, Nordland with organisation number 971130202. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 1994. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg og utleie av maskiner innen entreprenørbransjen og hva som hører inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 14.1m in revenue and NOK 355,000 in operating profit.

Former names: APOLLON AS

Key figures · 2025

Revenue
NOK 14.1m
▼ −4 %
Operating profit
NOK 355,000
▲ +12 %
Equity
NOK 4.7m
▲ +4 %
Est. value
NOK 3.1m

Financial health · 2025

Liquidity
1.57
Good
Current assets ÷ current liabilities
Profitability
1.9%
Weak
Return on total assets
Solidity
15.4%
Satisfactory
Equity as a share of total capital

Who owns BOTN MASKIN AS?

BOTN MASKIN AS
NOK 14.1m rev. · NOK 355,000 profit

BOTN MASKIN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BOTN MASKIN AS

Who owns BOTN MASKIN AS?

TORSTEIN BOTN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of BOTN MASKIN AS?

BOTN MASKIN AS had revenue of NOK 14.1m in 2025.

Who is the general manager of BOTN MASKIN AS?

Torstein Bengt Botn is registered as general manager of BOTN MASKIN AS.

Where is BOTN MASKIN AS based?

BOTN MASKIN AS has its business address in Sandnessjøen.

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.