biztrac. BETA
COMPANY REGISTER PROFILE
925193305 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Buying and selling of own real estate

TG BYGG EIENDOM AS

Org. no. 925193305 Limited company (AS) Hol Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 42,000
Operating profit NOK 27,000
Equity NOK 1.4m
Incorporated 2020
Share capital NOK 1.4m

TG BYGG EIENDOM AS is registered as a limited company in Hol, Buskerud with organisation number 925193305. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2020. Registered share capital is NOK 1.4m, divided into 100 shares. The company's stated purpose is: “Kjøp, utvikling, salg og utleie av fast eiendom samt andre produkter/tjenester som naturlig hører sammen med dette, herunder deltagelse i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 42,000 in revenue and NOK 27,000 in operating profit.

Key figures · 2025

Revenue
NOK 42,000
▲ +0 %
Operating profit
NOK 27,000
▲ +2 %
Equity
NOK 1.4m
▲ +1 %
Est. value
NOK 968,000

Financial health · 2025

Liquidity
3.23
Very good
Current assets ÷ current liabilities
Profitability
1.6%
Weak
Return on total assets
Solidity
78.7%
Very good
Equity as a share of total capital

Who owns TG BYGG EIENDOM AS?

TG BYGG EIENDOM AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about TG BYGG EIENDOM AS

Who owns TG BYGG EIENDOM AS?

JGG INVEST AS is the largest registered owner, with 58.0%.

What is the revenue of TG BYGG EIENDOM AS?

TG BYGG EIENDOM AS had revenue of NOK 42,000 in 2025.

Who is the general manager of TG BYGG EIENDOM AS?

Jo G Grøslandsbråten is registered as general manager of TG BYGG EIENDOM AS.

Where is TG BYGG EIENDOM AS based?

TG BYGG EIENDOM AS has its business address in Geilo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.