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

BAKIR INVEST AS

Org. no. 928627705 Limited company (AS) Lillestrøm Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 1.1m
Operating profit NOK −4,000
Equity NOK 10,000
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−4k kr).

BAKIR INVEST AS is registered as a limited company in Lillestrøm, Akershus with organisation number 928627705. The business is classified under on-demand passenger transport service activities by vehicle with driver (NACE 49.330). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Drosjebiltransport og privatsjåfør.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.1m in revenue and NOK −4,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.1m
Operating profit
NOK −4,000
Equity
NOK 10,000
Est. value
NOK 389,000

Financial health · 2024

Liquidity
1.51
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
2.2%
Weak
Equity as a share of total capital

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

Who owns BAKIR INVEST AS?

NIDAL AKRAM NAZMI BAKIR
BAKIR INVEST AS
NOK 1.1m rev. · NOK −4,000 profit

BAKIR INVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BAKIR INVEST AS

Who owns BAKIR INVEST AS?

NIDAL AKRAM NAZMI BAKIR is the largest registered owner, with 100.0%.

What is the revenue of BAKIR INVEST AS?

BAKIR INVEST AS had revenue of NOK 1.1m in 2024.

Who is the general manager of BAKIR INVEST AS?

Nidal Akram Nazmi Bakir is registered as general manager of BAKIR INVEST AS.

Where is BAKIR INVEST AS based?

BAKIR INVEST AS has its business address in Frogner.

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.