BIZTRAC BETA
Construction of residential and non-residential buildings

MA TOTALBYGG AS

Org. no. 990250448 Limited company (AS) Oslo Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 159.9m
Operating profit NOK 2.9m
Equity NOK 26.7m
Incorporated 2006
Employees 30
Share capital NOK 1.0m

MA TOTALBYGG AS is registered as a limited company in Oslo, Oslo with organisation number 990250448. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2006 and has 30 registered employees. Registered share capital is NOK 1.0m, divided into 2000 shares. The company's stated purpose is: “Drive entreprenørvirksomhet, herunder bygge- og anleggsarbeid, eiendomsutvikling og andre aktiviteter som naturlig hører sammen med dette. Selskapet kan også investere i, eie og drive virksomhet innen relaterte områder.”. The most recent filed accounts, for the 2024 financial year, show NOK 159.9m in revenue and NOK 2.9m in operating profit.

Key figures · 2024

Revenue
NOK 159.9m
Operating profit
NOK 2.9m
Equity
NOK 26.7m
Est. value
NOK 23.4m

Financial health · 2024

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

Who owns MA TOTALBYGG AS?

MAKZ AS
MA TOTALBYGG AS
NOK 159.9m rev. · NOK 2.9m profit

MA TOTALBYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MA TOTALBYGG AS

Who owns MA TOTALBYGG AS?

MAKZ AS is the largest registered owner, with 100.0%.

What is the revenue of MA TOTALBYGG AS?

MA TOTALBYGG AS had revenue of NOK 159.9m in 2024.

Who is the general manager of MA TOTALBYGG AS?

Roar Beck is registered as general manager of MA TOTALBYGG AS.

Where is MA TOTALBYGG AS based?

MA TOTALBYGG AS has its business address in Oslo.

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.