BIZTRAC BETA
Freight transport by road

MBC TRANSPORT AS

Org. no. 934365631 Limited company (AS) Horten Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 1.6m
Operating profit NOK 102,000
Equity NOK 76,000
Incorporated 2024
Share capital NOK 30,000

MBC TRANSPORT AS is registered as a limited company in Horten, Vestfold with organisation number 934365631. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen godstransport på vei - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.6m in revenue and NOK 102,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.6m
Operating profit
NOK 102,000
Equity
NOK 76,000
Est. value
NOK 352,000

Financial health · 2025

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

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

Who owns MBC TRANSPORT AS?

MORGAN BASBERG CHRISTOFFERSEN
MBC TRANSPORT AS
NOK 1.6m rev. · NOK 102,000 profit

MBC TRANSPORT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MBC TRANSPORT AS

Who owns MBC TRANSPORT AS?

MORGAN BASBERG CHRISTOFFERSEN is the largest registered owner, with 100.0%.

What is the revenue of MBC TRANSPORT AS?

MBC TRANSPORT AS had revenue of NOK 1.6m in 2025.

Who is the general manager of MBC TRANSPORT AS?

Morgan Basberg Christoffersen is registered as general manager of MBC TRANSPORT AS.

Where is MBC TRANSPORT AS based?

MBC TRANSPORT AS has its business address in Horten.

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.