biztrac. BETA
COMPANY REGISTER PROFILE
934420020 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Repair and maintenance of machinery

BØRSEBAKKE MASKIN AS

Org. no. 934420020 Limited company (AS) Moss Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 6.6m
Operating profit NOK 632,000
Equity NOK 739,000
Incorporated 2024
Share capital NOK 50,000

BØRSEBAKKE MASKIN AS is registered as a limited company in Moss, Østfold with organisation number 934420020. The business is classified under repair and maintenance of machinery (NACE 33.120). The company was incorporated in 2024. Registered share capital is NOK 50,000, divided into 500 shares. The company's stated purpose is: “Import og salg av maskiner, utstyr og deler. Kjøp, salg og formidling av utstyr. Reparasjon, service og vedlikehold på maskiner og utstyr. Kjøp og salg av bruktbiler. Konsulenttjenester innen landbruk og anlegg.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.6m in revenue and NOK 632,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.6m
▲ +431 %
Operating profit
NOK 632,000
▲ +120 %
Equity
NOK 739,000
▲ +171 %
Est. value
NOK 2.6m

Financial health · 2025

Liquidity
1.68
Good
Current assets ÷ current liabilities
Profitability
33.3%
Very good
Return on total assets
Solidity
43.4%
Very good
Equity as a share of total capital

Who owns BØRSEBAKKE MASKIN AS?

BØRSEBAKKE MASKIN AS
NOK 6.6m rev. · NOK 632,000 profit

BØRSEBAKKE MASKIN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BØRSEBAKKE MASKIN AS

Who owns BØRSEBAKKE MASKIN AS?

Vidar Børsebakke Aas-Hveem is the largest registered owner, with 100.0%.

What is the revenue of BØRSEBAKKE MASKIN AS?

BØRSEBAKKE MASKIN AS had revenue of NOK 6.6m in 2025.

Where is BØRSEBAKKE MASKIN AS based?

BØRSEBAKKE MASKIN AS has its business address in Dilling.

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.