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

G. BERGGREN AS

Org. no. 920731910 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 227.6m
Operating profit NOK 2.4m
Equity NOK 4.2m
Incorporated 2018
Employees 40
Share capital NOK 750,000

G. BERGGREN AS is registered as a limited company in Oslo, Oslo with organisation number 920731910. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2018 and has 40 registered employees. Registered share capital is NOK 750,000, divided into 1 shares. The company's stated purpose is: “Selv, gjennom hel- eller deleide selskaper eller ved samarbeide med andre virksomheter, å forestå drift av dagligvareforretning og annen virksomhet beslektet med denne.”. The most recent filed accounts, for the 2025 financial year, show NOK 227.6m in revenue and NOK 2.4m in operating profit.

Key figures · 2025

Revenue
NOK 227.6m
Operating profit
NOK 2.4m
Equity
NOK 4.2m
Est. value
NOK 11.5m

Financial health · 2024

Liquidity
1.06
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
15.0%
Satisfactory
Equity as a share of total capital

Who owns G. BERGGREN AS?

G. BERGGREN HOLDING AS
G. BERGGREN AS
NOK 227.6m rev. · NOK 2.4m profit

G. BERGGREN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about G. BERGGREN AS

Who owns G. BERGGREN AS?

G. BERGGREN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of G. BERGGREN AS?

G. BERGGREN AS had revenue of NOK 227.6m in 2025.

Who is the general manager of G. BERGGREN AS?

Glenn Berggren is registered as general manager of G. BERGGREN AS.

Where is G. BERGGREN AS based?

G. BERGGREN 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.