BIZTRAC BETA
Landscape service activities

FREMGANG HOLDING AS

Org. no. 932951401 Limited company (AS) Frogn Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −3,000
Equity NOK 33,000
Incorporated 2024
Share capital NOK 42,000

Signals

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

FREMGANG HOLDING AS is registered as a limited company in Frogn, Akershus with organisation number 932951401. The business is classified under landscape service activities (NACE 81.300). The company was incorporated in 2024. Registered share capital is NOK 42,000, divided into 42000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet 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 foretagende.”.

Key figures · 2024

Operating profit
NOK −3,000
Equity
NOK 33,000
Est. value
NOK 47,000

Financial health · 2024

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

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

Who owns FREMGANG HOLDING AS?

DAVID JULIEN
FREMGANG HOLDING AS
· NOK −3,000 profit

FREMGANG HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FREMGANG HOLDING AS own?

FREMGANG HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about FREMGANG HOLDING AS

Who owns FREMGANG HOLDING AS?

DAVID JULIEN is the largest registered owner, with 100.0%.

Who is the general manager of FREMGANG HOLDING AS?

David Julien is registered as general manager of FREMGANG HOLDING AS.

Where is FREMGANG HOLDING AS based?

FREMGANG HOLDING AS has its business address in Nordre Frogn.

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.