BIZTRAC BETA
Wholesale of waste and scrap

MAWI AS

Org. no. 914138841 Limited company (AS) Karmøy Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 59,000
Operating profit NOK 24,000
Equity NOK −232,000
Incorporated 2014
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−232k kr).

MAWI AS is registered as a limited company in Karmøy, Rogaland with organisation number 914138841. The business is classified under wholesale of waste and scrap (NACE 46.870). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Utleie av personell, prosjektservice, arbeidstjenester, varehandel og import / eksport av varer, samt skraphandel, samt hva hermed står i forbindelse, herunder å kunne delta i foretak som driver tilsvarende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 59,000 in revenue and NOK 24,000 in operating profit.

Key figures · 2025

Revenue
NOK 59,000
Operating profit
NOK 24,000
Equity
NOK −232,000
Est. value
NOK 127,000

Financial health · 2025

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

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

Who owns MAWI AS?

MARCIN WINCENTY BANAS
MAWI AS
NOK 59,000 rev. · NOK 24,000 profit

MAWI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MAWI AS

Who owns MAWI AS?

MARCIN WINCENTY BANAS is the largest registered owner, with 100.0%.

What is the revenue of MAWI AS?

MAWI AS had revenue of NOK 59,000 in 2025.

Who is the general manager of MAWI AS?

Marcin Wincenty Banas is registered as general manager of MAWI AS.

Where is MAWI AS based?

MAWI AS has its business address in Torvastad.

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.