biztrac. BETA
COMPANY REGISTER PROFILE
917546355 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Construction of residential and non-residential buildings

2KVIK BYGG AS

Org. no. 917546355 Limited company (AS) Sandefjord Incorporated 2016 Active
Revenue 2025 NOK 6.5m
Operating profit NOK 350,000
Equity NOK 128,000
Incorporated 2016
Share capital NOK 30,000

2KVIK BYGG AS is registered as a limited company in Sandefjord, Vestfold with organisation number 917546355. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Håndverksvirksomhet, snekkerarbeid, maling og hva som ellers måtte stå i naturlig forbindelse med dette. Import, salg og montering av byggematerialer.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.5m in revenue and NOK 350,000 in operating profit.

Former names: KVIK BYGG AS

Key figures · 2025

Revenue
NOK 6.5m
▲ +13 %
Operating profit
NOK 350,000
▼ −34 %
Equity
NOK 128,000
▲ +132 %
Est. value
NOK 914,000

Financial health · 2025

Liquidity
1.01
Satisfactory
Current assets ÷ current liabilities
Profitability
26.2%
Very good
Return on total assets
Solidity
8.2%
Weak
Equity as a share of total capital

Who owns 2KVIK BYGG AS?

2KVIK BYGG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about 2KVIK BYGG AS

Who owns 2KVIK BYGG AS?

Vidas Vaitkevicius is the largest registered owner, with 50.0%.

What is the revenue of 2KVIK BYGG AS?

2KVIK BYGG AS had revenue of NOK 6.5m in 2025.

Who is the general manager of 2KVIK BYGG AS?

Vidas Vaitkevicius is registered as general manager of 2KVIK BYGG AS.

Where is 2KVIK BYGG AS based?

2KVIK BYGG AS has its business address in Melsomvik.

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.