BIZTRAC BETA
Buying and selling of own real estate

GJ BOLIG AS

Org. no. 925246565 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −7,000
Equity NOK 6,000
Incorporated 2020
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−7k kr).

GJ BOLIG AS is registered as a limited company in Oslo, Oslo with organisation number 925246565. 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 30,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg, drift og renovering av fast eiendom, entreprenørvirksomhet innen bygg og anlegg samt hva hermed står i forbindelse samt ved kjøp av aksjer eller på annen måte delta i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −7,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −7,000
Equity
NOK 6,000
Est. value
NOK 6,000

Financial health · 2025

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

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

Who owns GJ BOLIG AS?

WATCHBIRD AS
GJ BOLIG AS
NOK 0 rev. · NOK −7,000 profit

GJ BOLIG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GJ BOLIG AS

Who owns GJ BOLIG AS?

WATCHBIRD AS is the largest registered owner, with 100.0%.

What is the revenue of GJ BOLIG AS?

GJ BOLIG AS had revenue of NOK 0 in 2025.

Who is the general manager of GJ BOLIG AS?

Rune Jomaas is registered as general manager of GJ BOLIG AS.

Where is GJ BOLIG AS based?

GJ BOLIG 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 15.06.2026.

Report a problem

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