BIZTRAC BETA
Retail sale of clothing

M+B WEB AS

Org. no. 971189843 Limited company (AS) Bærum Incorporated 1994 Active
Ownership graph ↗
Revenue 2025 NOK 1.2m
Operating profit NOK −139,000
Equity NOK −2.5m
Incorporated 1994
Share capital NOK 300,000

Signals

3 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−2,5 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−139k kr).
  • Nylig endring 2026-06-15 Konkurs registrert 2026-06-15.

M+B WEB AS is registered as a limited company in Bærum, Akershus with organisation number 971189843. The business is classified under retail sale of clothing (NACE 47.710). The company was incorporated in 1994. Registered share capital is NOK 300,000, divided into 300 shares. The company's stated purpose is: “Drifte nettsiden markandbrandy.no samt hva som herved står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK −139,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.2m
Operating profit
NOK −139,000
Equity
NOK −2.5m

Financial health · 2025

Liquidity
0.09
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-1014.4%
Weak
Equity as a share of total capital

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

Who owns M+B WEB AS?

TRONTEX AS
M+B WEB AS
NOK 1.2m rev. · NOK −139,000 profit

M+B WEB AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about M+B WEB AS

Who owns M+B WEB AS?

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

What is the revenue of M+B WEB AS?

M+B WEB AS had revenue of NOK 1.2m in 2025.

Who is the general manager of M+B WEB AS?

Stian Tronsgård is registered as general manager of M+B WEB AS.

Where is M+B WEB AS based?

M+B WEB AS has its business address in Sandvika.

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.