BIZTRAC BETA
Uoppgitt

G.BERG AS

Org. no. 918990178 Limited company (AS) Frogn Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 232,000
Operating profit NOK 61,000
Equity NOK 5.0m
Incorporated 2017
Share capital NOK 30,000

G.BERG AS is registered as a limited company in Frogn, Akershus with organisation number 918990178. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Holding Selskap og andre tjenester og produkter som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender samt kjøp, salg og utleie av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 232,000 in revenue and NOK 61,000 in operating profit.

Key figures · 2025

Revenue
NOK 232,000
Operating profit
NOK 61,000
Equity
NOK 5.0m
Est. value
NOK 3.1m

Financial health · 2025

Liquidity
6.54
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
67.0%
Very good
Equity as a share of total capital

Who owns G.BERG AS?

GLENN ROBERT BERG
G.BERG AS
NOK 232,000 rev. · NOK 61,000 profit

G.BERG AS has 1 registered shareholder:

All shareholders and roles →

Which companies does G.BERG AS own?

G.BERG AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about G.BERG AS

Who owns G.BERG AS?

GLENN ROBERT BERG is the largest registered owner, with 100.0%.

What is the revenue of G.BERG AS?

G.BERG AS had revenue of NOK 232,000 in 2025.

Who is the general manager of G.BERG AS?

Glenn Robert Berg is registered as general manager of G.BERG AS.

Where is G.BERG AS based?

G.BERG AS has its business address in Drøbak.

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.