biztrac. BETA
COMPANY REGISTER PROFILE
930088234 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Repair and maintenance of motor vehicles

BZAW AS

Org. no. 930088234 Limited company (AS) Gjøvik Incorporated 2022 Active
Revenue 2025 NOK 2.4m
Operating profit NOK 67,000
Equity NOK −75,000
Incorporated 2022
Employees 8
Share capital NOK 30,000

Signals

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

BZAW AS is registered as a limited company in Gjøvik, Innlandet with organisation number 930088234. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2022 and has 8 registered employees. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Drive med bilvask, bilpleie og lignende tjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.4m in revenue and NOK 67,000 in operating profit.

Former names: AFAS 300922-21 AS

Key figures · 2025

Revenue
NOK 2.4m
▲ +26 %
Operating profit
NOK 67,000
▲ +5 %
Equity
NOK −75,000
▼ −129 %
Est. value
NOK 281,000

Financial health · 2025

Liquidity
0.12
Not satisfactory
Current assets ÷ current liabilities
Profitability
3.5%
Weak
Return on total assets
Solidity
-4.0%
Weak
Equity as a share of total capital

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

Who owns BZAW AS?

BZAW AS
NOK 2.4m rev. · NOK 67,000 profit

BZAW AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BZAW AS

Who owns BZAW AS?

BMZ EIENDOM AS is the largest registered owner, with 70.0%.

What is the revenue of BZAW AS?

BZAW AS had revenue of NOK 2.4m in 2025.

Who is the general manager of BZAW AS?

Bashar Mohammed Zabin is registered as general manager of BZAW AS.

Where is BZAW AS based?

BZAW AS has its business address in Gjøvik.

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.