BIZTRAC BETA
Non-specialised retail sale of predominately food, beverages or tobacco

NY OLIVEN FRUKT OG GRØNT AS

Org. no. 826354682 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 5.3m
Operating profit NOK 30,000
Equity NOK 189,000
Incorporated 2020
Share capital NOK 30,000

NY OLIVEN FRUKT OG GRØNT AS is registered as a limited company in Oslo, Oslo with organisation number 826354682. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Drive dagligvarebutikk.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.3m in revenue and NOK 30,000 in operating profit.

Key figures · 2024

Revenue
NOK 5.3m
Operating profit
NOK 30,000
Equity
NOK 189,000
Est. value
NOK 208,000

Financial health · 2024

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

Who owns NY OLIVEN FRUKT OG GRØNT AS?

AHMAD JAMSHID AKBARZADH
NY OLIVEN FRUKT OG GRØNT AS
NOK 5.3m rev. · NOK 30,000 profit

NY OLIVEN FRUKT OG GRØNT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NY OLIVEN FRUKT OG GRØNT AS

Who owns NY OLIVEN FRUKT OG GRØNT AS?

AHMAD JAMSHID AKBARZADH is the largest registered owner, with 100.0%.

What is the revenue of NY OLIVEN FRUKT OG GRØNT AS?

NY OLIVEN FRUKT OG GRØNT AS had revenue of NOK 5.3m in 2024.

Who is the general manager of NY OLIVEN FRUKT OG GRØNT AS?

Ahmad Jamshid Akbarzadh is registered as general manager of NY OLIVEN FRUKT OG GRØNT AS.

Where is NY OLIVEN FRUKT OG GRØNT AS based?

NY OLIVEN FRUKT OG GRØNT 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.