BIZTRAC BETA
On-demand passenger transport service activities by vehicle with driver

MAJABE AS

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

Signals

3 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−7k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−7k kr).
  • Nystiftet selskap Selskapet ble stiftet 2025-10-22.

MAJABE AS is registered as a limited company in Oslo, Oslo with organisation number 936517153. The business is classified under on-demand passenger transport service activities by vehicle with driver (NACE 49.330). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Persontransport.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −7,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −7,000
Equity
NOK −7,000

Financial health · 2025

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

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

Who owns MAJABE AS?

Abdulwahid Yassin Wardere
MAJABE AS
NOK 0 rev. · NOK −7,000 profit

MAJABE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MAJABE AS

Who owns MAJABE AS?

Abdulwahid Yassin Wardere is the largest registered owner, with 100.0%.

What is the revenue of MAJABE AS?

MAJABE AS had revenue of NOK 0 in 2025.

Who is the general manager of MAJABE AS?

Abdulwahid Yassin Wardere is registered as general manager of MAJABE AS.

Where is MAJABE AS based?

MAJABE 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 15.06.2026.

Report a problem

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