BIZTRAC BETA
Uoppgitt

GCTA AS

Org. no. 936492150 Limited company (AS) Oslo Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −14,000
Equity NOK 11,000
Incorporated 2025
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−14k kr).
  • Nystiftet selskap Selskapet ble stiftet 2025-10-09.

GCTA AS is registered as a limited company in Oslo, Oslo with organisation number 936492150. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −14,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −14,000
Equity
NOK 11,000
Est. value
NOK 13,000

Financial health · 2025

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

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

Who owns GCTA AS?

CHRISTOPHER JAMES PADDON
GCTA AS
NOK 0 rev. · NOK −14,000 profit

GCTA AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GCTA AS own?

GCTA AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about GCTA AS

Who owns GCTA AS?

CHRISTOPHER JAMES PADDON is the largest registered owner, with 100.0%.

What is the revenue of GCTA AS?

GCTA AS had revenue of NOK 0 in 2025.

Where is GCTA AS based?

GCTA 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.