biztrac. BETA
COMPANY REGISTER PROFILE
933884732 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Civil engineering activities

KONSTRUKSJON PARTNER AS

Org. no. 933884732 Limited company (AS) Vindafjord Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 6.0m
Operating profit NOK 708,000
Equity NOK 365,000
Incorporated 2024
Share capital NOK 30,000

KONSTRUKSJON PARTNER AS is registered as a limited company in Vindafjord, Rogaland with organisation number 933884732. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Prosjektledelse, prosjektering og byggeledelse, og naturlig tilhørende aktiviteter.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.0m in revenue and NOK 708,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.0m
▲ +297 %
Operating profit
NOK 708,000
▲ +2333 %
Equity
NOK 365,000
▲ +801 %
Est. value
NOK 4.3m

Financial health · 2025

Liquidity
1.14
Satisfactory
Current assets ÷ current liabilities
Profitability
30.3%
Very good
Return on total assets
Solidity
15.5%
Satisfactory
Equity as a share of total capital

Who owns KONSTRUKSJON PARTNER AS?

KONSTRUKSJON PARTNER AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about KONSTRUKSJON PARTNER AS

Who owns KONSTRUKSJON PARTNER AS?

SIVILINGENIØR KJETIL KVITTINGEN AS is the largest registered owner, with 42.0%.

What is the revenue of KONSTRUKSJON PARTNER AS?

KONSTRUKSJON PARTNER AS had revenue of NOK 6.0m in 2025.

Who is the general manager of KONSTRUKSJON PARTNER AS?

Kjetil Kvittingen is registered as general manager of KONSTRUKSJON PARTNER AS.

Where is KONSTRUKSJON PARTNER AS based?

KONSTRUKSJON PARTNER AS has its business address in Ølensvåg.

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.