biztrac. BETA
COMPANY REGISTER PROFILE
816766052 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
In liquidation UPDATED 03.10.2026
⚠GJETTUM UTVIKLING AS is registered as “In liquidation” with the Brønnøysund Register Centre.
Development of building projects

GJETTUM UTVIKLING AS

Org. no. 816766052 Limited company (AS) Oslo Incorporated 2016 In liquidation
Ownership graph ↗
Operating profit NOK −136,000
Equity NOK 110,000
Incorporated 2016
Share capital NOK 100,000

Signals

3 flags
  • Under avvikling Selskapet er under frivillig avvikling.
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−136k kr).
  • Nylig endring 2026-10-06 Under avvikling registrert 2026-10-06.

GJETTUM UTVIKLING AS is registered as a limited company in Oslo, Oslo with organisation number 816766052. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2016. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Erverve, utvikle, drive og avhende fast eiendom, samt all annen naturlig tilhørende virksomhet. Selskapet kan eie aksjer i andre selskaper.”.

Former names: PRO LIII AS

Key figures · 2025

Operating profit
NOK −136,000
▲ +99 %
Equity
NOK 110,000
▲ +0 %
Est. value
NOK 100,000

Financial health · 2025

Liquidity
1.01
Satisfactory
Current assets ÷ current liabilities
Profitability
-0.4%
Not satisfactory
Return on total assets
Solidity
0.6%
Not satisfactory
Equity as a share of total capital

Who owns GJETTUM UTVIKLING AS?

GJETTUM UTVIKLING AS
· NOK −136,000 profit

GJETTUM UTVIKLING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GJETTUM UTVIKLING AS

Who owns GJETTUM UTVIKLING AS?

GJELSTEN BOLIG AS is the largest registered owner, with 100.0%.

Where is GJETTUM UTVIKLING AS based?

GJETTUM UTVIKLING AS has its business address in Oslo.

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.