BIZTRAC BETA
Other specialised construction activities n.e.c.

G-B EIENDOM AS

Org. no. 917403074 Limited company (AS) Midtre Gauldal Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 4.4m
Operating profit NOK 3.5m
Equity NOK 361,000
Incorporated 2016
Share capital NOK 361,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

G-B EIENDOM AS is registered as a limited company in Midtre Gauldal, Trøndelag with organisation number 917403074. The business is classified under other specialised construction activities n.e.c. (NACE 43.990). The company was incorporated in 2016. Registered share capital is NOK 361,000, divided into 361449 shares. The company's stated purpose is: “Investering og drift av eiendommer, investering i aksjer og andre selskaper, konsulentvirksomhet samt annen virksomhet som faller naturlig under slike virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.4m in revenue and NOK 3.5m in operating profit.

Key figures · 2025

Revenue
NOK 4.4m
Operating profit
NOK 3.5m
Equity
NOK 361,000
Est. value
NOK 9.3m

Financial health · 2025

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

Who owns G-B EIENDOM AS?

GAULDAL BETONG HOLDING AS
G-B EIENDOM AS
NOK 4.4m rev. · NOK 3.5m profit

G-B EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about G-B EIENDOM AS

Who owns G-B EIENDOM AS?

GAULDAL BETONG HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of G-B EIENDOM AS?

G-B EIENDOM AS had revenue of NOK 4.4m in 2025.

Where is G-B EIENDOM AS based?

G-B EIENDOM AS has its business address in Soknedal.

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.