BIZTRAC BETA
Construction of residential and non-residential buildings

3 G BYGG AS

Org. no. 923783091 Limited company (AS) Ullensaker Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 3.6m
Operating profit NOK −2.3m
Equity NOK −2.3m
Incorporated 2019
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−2,3 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−2,3 mill kr).

3 G BYGG AS is registered as a limited company in Ullensaker, Akershus with organisation number 923783091. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Byggearbeider til privatpersoner og bedrifter.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.6m in revenue and NOK −2.3m in operating profit.

Key figures · 2025

Revenue
NOK 3.6m
Operating profit
NOK −2.3m
Equity
NOK −2.3m

Financial health · 2025

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

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

Who owns 3 G BYGG AS?

HEIKKI EILEV GRANUM
3 G BYGG AS
NOK 3.6m rev. · NOK −2.3m profit

3 G BYGG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about 3 G BYGG AS

Who owns 3 G BYGG AS?

HEIKKI EILEV GRANUM is the largest registered owner, with 51.0%.

What is the revenue of 3 G BYGG AS?

3 G BYGG AS had revenue of NOK 3.6m in 2025.

Who is the general manager of 3 G BYGG AS?

Heikki Eilev Granum is registered as general manager of 3 G BYGG AS.

Where is 3 G BYGG AS based?

3 G BYGG AS has its business address in Kløfta.

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.