biztrac. BETA
COMPANY REGISTER PROFILE
833840002 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Wholesale of waste and scrap

MAK METALL AS

Org. no. 833840002 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK −2,000
Incorporated 2024
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−2k kr).
  • Nylig endring 2026-05-22 Adresseendring registrert 2026-05-22.

MAK METALL AS is registered as a limited company in Oslo, Oslo with organisation number 833840002. The business is classified under wholesale of waste and scrap (NACE 46.870). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Pizza utsalg fra motorvogn.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Former names: PIZZA AS

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
▲ +100 %
Equity
NOK −2,000
▼ −110 %

Financial health · 2025

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

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

Who owns MAK METALL AS?

MAK METALL AS
NOK 0 rev. · NOK 0 profit

MAK METALL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MAK METALL AS

Who owns MAK METALL AS?

Christian Zschaebitz is the largest registered owner, with 100.0%.

What is the revenue of MAK METALL AS?

MAK METALL AS had revenue of NOK 0 in 2025.

Who is the general manager of MAK METALL AS?

Mehmet Ali Kalkan is registered as general manager of MAK METALL AS.

Where is MAK METALL AS based?

MAK METALL 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.