BIZTRAC BETA
Development of building projects

QVARTAL 1 HOLDING AS

Org. no. 923467017 Limited company (AS) Kristiansand Incorporated 2019 Active
Ownership graph ↗
Operating profit NOK −64,000
Equity NOK 71.5m
Incorporated 2019
Share capital NOK 150,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−64k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

QVARTAL 1 HOLDING AS is registered as a limited company in Kristiansand, Agder with organisation number 923467017. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2019. Registered share capital is NOK 150,000, divided into 1000 shares. The company's stated purpose is: “Investere i andre selskaper herunder kjøp, salg og utvikling av eiendom, samt annen virksomhet som naturlig hører inn under dette.”.

Key figures · 2024

Operating profit
NOK −64,000
Equity
NOK 71.5m
Est. value
NOK 65.3m

Financial health · 2024

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

Who owns QVARTAL 1 HOLDING AS?

GUMPEN EIENDOM AS
QVARTAL 1 HOLDING AS
· NOK −64,000 profit

QVARTAL 1 HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does QVARTAL 1 HOLDING AS own?

QVARTAL 1 HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about QVARTAL 1 HOLDING AS

Who owns QVARTAL 1 HOLDING AS?

GUMPEN EIENDOM AS is the largest registered owner, with 50.0%.

Who is the general manager of QVARTAL 1 HOLDING AS?

Arild Skeie is registered as general manager of QVARTAL 1 HOLDING AS.

Where is QVARTAL 1 HOLDING AS based?

QVARTAL 1 HOLDING AS has its business address in Kristiansand S.

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.