BIZTRAC BETA
Construction of residential and non-residential buildings

GT BYGG AS

Org. no. 929562550 Limited company (AS) Ullensaker Incorporated 2022 Active
Ownership graph ↗
Revenue 2023 NOK 0
Operating profit NOK −12,000
Equity NOK −157
Incorporated 2022
Share capital NOK 30,000

Signals

3 flags
  • Negativ egenkapital 2023 Bokført egenkapital er negativ (−157 kr).
  • Driftsunderskudd 2023 Siste driftsresultat er negativt (−12k kr).
  • Utdatert regnskap Siste registrerte regnskap er fra 2023.

GT BYGG AS is registered as a limited company in Ullensaker, Akershus with organisation number 929562550. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Oppføring av bygninger. Byggearbeider, landskapsarbeider samt annen virksomhet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2023 financial year, show NOK 0 in revenue and NOK −12,000 in operating profit.

Key figures · 2023

Revenue
NOK 0
Operating profit
NOK −12,000
Equity
NOK −157

Financial health · 2023

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

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

Who owns GT BYGG AS?

No shareholders are registered for GT BYGG AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about GT BYGG AS

What is the revenue of GT BYGG AS?

GT BYGG AS had revenue of NOK 0 in 2023.

Who is the general manager of GT BYGG AS?

Dovydas Zickevicius is registered as general manager of GT BYGG AS.

Where is GT BYGG AS based?

GT BYGG AS has its business address in Jessheim.

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.