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

FROGNER DAGLIGVARE AS

Org. no. 932614529 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 7.4m
Operating profit NOK 170,000
Equity NOK 38,000
Incorporated 2023
Employees 6
Share capital NOK 30,000

FROGNER DAGLIGVARE AS is registered as a limited company in Oslo, Oslo with organisation number 932614529. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2023 and has 6 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Kioskhandel med bredt vareutvalg.”. The most recent filed accounts, for the 2025 financial year, show NOK 7.4m in revenue and NOK 170,000 in operating profit.

Key figures · 2025

Revenue
NOK 7.4m
Operating profit
NOK 170,000
Equity
NOK 38,000
Est. value
NOK 680,000

Financial health · 2025

Liquidity
0.44
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
3.3%
Weak
Equity as a share of total capital

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

Who owns FROGNER DAGLIGVARE AS?

SULTAN AHMED
FROGNER DAGLIGVARE AS
NOK 7.4m rev. · NOK 170,000 profit

FROGNER DAGLIGVARE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FROGNER DAGLIGVARE AS

Who owns FROGNER DAGLIGVARE AS?

SULTAN AHMED is the largest registered owner, with 100.0%.

What is the revenue of FROGNER DAGLIGVARE AS?

FROGNER DAGLIGVARE AS had revenue of NOK 7.4m in 2025.

Who is the general manager of FROGNER DAGLIGVARE AS?

Sultan Ahmed is registered as general manager of FROGNER DAGLIGVARE AS.

Where is FROGNER DAGLIGVARE AS based?

FROGNER DAGLIGVARE 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.