BIZTRAC BETA
Civil engineering activities

MB BYGGELEDELSE AS

Org. no. 930983691 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 2.5m
Operating profit NOK 484,000
Equity NOK 422,000
Incorporated 2023
Share capital NOK 30,000

MB BYGGELEDELSE AS is registered as a limited company in Oslo, Oslo with organisation number 930983691. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge tjenester og varer innen prosjekt- og byggeledelse, rådgivning, elektro, jernbaneteknikk, byggteknikk - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.5m in revenue and NOK 484,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.5m
Operating profit
NOK 484,000
Equity
NOK 422,000
Est. value
NOK 2.3m

Financial health · 2024

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

Who owns MB BYGGELEDELSE AS?

MARTIN KRISTOFFER BONGO
MB BYGGELEDELSE AS
NOK 2.5m rev. · NOK 484,000 profit

MB BYGGELEDELSE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MB BYGGELEDELSE AS

Who owns MB BYGGELEDELSE AS?

MARTIN KRISTOFFER BONGO is the largest registered owner, with 100.0%.

What is the revenue of MB BYGGELEDELSE AS?

MB BYGGELEDELSE AS had revenue of NOK 2.5m in 2024.

Who is the general manager of MB BYGGELEDELSE AS?

Martin Kristoffer Bongo is registered as general manager of MB BYGGELEDELSE AS.

Where is MB BYGGELEDELSE AS based?

MB BYGGELEDELSE 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.