BIZTRAC BETA
Architectural activities

KVIST ARKITEKTUR AS

Org. no. 926998951 Limited company (AS) Stavanger Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 969,000
Operating profit NOK 30,000
Equity NOK 67,000
Incorporated 2021
Share capital NOK 30,000

KVIST ARKITEKTUR AS is registered as a limited company in Stavanger, Rogaland with organisation number 926998951. The business is classified under architectural activities (NACE 71.110). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Arkitektkontor og andre produkter/tjenester som naturlig hører til dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak. Selskapet kan også drive med kjøp/drift av fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 969,000 in revenue and NOK 30,000 in operating profit.

Key figures · 2024

Revenue
NOK 969,000
Operating profit
NOK 30,000
Equity
NOK 67,000
Est. value
NOK 184,000

Financial health · 2024

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

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

Who owns KVIST ARKITEKTUR AS?

ARKIPRENOR AS
KVIST ARKITEKTUR AS
NOK 969,000 rev. · NOK 30,000 profit

KVIST ARKITEKTUR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KVIST ARKITEKTUR AS

Who owns KVIST ARKITEKTUR AS?

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

What is the revenue of KVIST ARKITEKTUR AS?

KVIST ARKITEKTUR AS had revenue of NOK 969,000 in 2024.

Where is KVIST ARKITEKTUR AS based?

KVIST ARKITEKTUR AS has its business address in Hafrsfjord.

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.