BIZTRAC BETA
Other specialised construction activities n.e.c.

MIMAX BETONGSAGING AS

Org. no. 934267745 Limited company (AS) Bergen Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 126,000
Operating profit NOK −13,000
Equity NOK 11,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−13k kr).

MIMAX BETONGSAGING AS is registered as a limited company in Bergen, Vestland with organisation number 934267745. The business is classified under other specialised construction activities n.e.c. (NACE 43.990). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Skal drive med betongarbeid, saging og boring i betong med diamantverktøy samt rivning.”. The most recent filed accounts, for the 2024 financial year, show NOK 126,000 in revenue and NOK −13,000 in operating profit.

Key figures · 2024

Revenue
NOK 126,000
Operating profit
NOK −13,000
Equity
NOK 11,000
Est. value
NOK 48,000

Financial health · 2024

Liquidity
1.32
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
24.4%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns MIMAX BETONGSAGING AS?

ØRJAN BERTHELSEN
MIMAX BETONGSAGING AS
NOK 126,000 rev. · NOK −13,000 profit

MIMAX BETONGSAGING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MIMAX BETONGSAGING AS

Who owns MIMAX BETONGSAGING AS?

ØRJAN BERTHELSEN is the largest registered owner, with 100.0%.

What is the revenue of MIMAX BETONGSAGING AS?

MIMAX BETONGSAGING AS had revenue of NOK 126,000 in 2024.

Where is MIMAX BETONGSAGING AS based?

MIMAX BETONGSAGING AS has its business address in Laksevåg.

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.