BIZTRAC BETA
Construction of residential and non-residential buildings

GROMGUTTA AS

Org. no. 911623463 Limited company (AS) Enebakk Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 5.0m
Operating profit NOK −90,000
Equity NOK 85,000
Incorporated 2013
Share capital NOK 30,000

Signals

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

GROMGUTTA AS is registered as a limited company in Enebakk, Akershus with organisation number 911623463. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Renovering av bygg og etablering av nybygg, samt salg av produkter til byggevirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.0m in revenue and NOK −90,000 in operating profit.

Key figures · 2024

Revenue
NOK 5.0m
Operating profit
NOK −90,000
Equity
NOK 85,000
Est. value
NOK 1.8m

Financial health · 2024

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

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

Who owns GROMGUTTA AS?

LARS HAKONSØNN BARFOD
GROMGUTTA AS
NOK 5.0m rev. · NOK −90,000 profit

GROMGUTTA AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about GROMGUTTA AS

Who owns GROMGUTTA AS?

LARS HAKONSØNN BARFOD is the largest registered owner, with 50.0%.

What is the revenue of GROMGUTTA AS?

GROMGUTTA AS had revenue of NOK 5.0m in 2024.

Who is the general manager of GROMGUTTA AS?

Diego Dario Olivares is registered as general manager of GROMGUTTA AS.

Where is GROMGUTTA AS based?

GROMGUTTA AS has its business address in Ytre Enebakk.

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.