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

MK BIL AS

Org. no. 922169543 Limited company (AS) Nannestad Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 549,000
Operating profit NOK 5,000
Equity NOK −68,000
Incorporated 2019
Share capital NOK 30,000

Signals

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

MK BIL AS is registered as a limited company in Nannestad, Akershus with organisation number 922169543. The business is classified under on-demand passenger transport service activities by vehicle with driver (NACE 49.330). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Drosjevirksomhet, kjøp og salg av lette motorvogner, transportvirksomhet og andre oppgaver som naturlig tilhører disse.”. The most recent filed accounts, for the 2024 financial year, show NOK 549,000 in revenue and NOK 5,000 in operating profit.

Key figures · 2024

Revenue
NOK 549,000
Operating profit
NOK 5,000
Equity
NOK −68,000
Est. value
NOK 28,000

Financial health · 2024

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

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

Who owns MK BIL AS?

RIZWAN ILYAS
MK BIL AS
NOK 549,000 rev. · NOK 5,000 profit

MK BIL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MK BIL AS

Who owns MK BIL AS?

RIZWAN ILYAS is the largest registered owner, with 100.0%.

What is the revenue of MK BIL AS?

MK BIL AS had revenue of NOK 549,000 in 2024.

Who is the general manager of MK BIL AS?

Rizwan Ilyas is registered as general manager of MK BIL AS.

Where is MK BIL AS based?

MK BIL AS has its business address in Nannestad.

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.