BIZTRAC BETA
Wholesale of other machinery and equipment

VK SERTIFISERING AS

Org. no. 935862418 Limited company (AS) Verdal Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 784,000
Operating profit NOK 84,000
Equity NOK 158,000
Incorporated 2025
Share capital NOK 100,000

Signals

1 flags
  • Nylig endring 2026-03-11 Adresseendring registrert 2026-03-11.

VK SERTIFISERING AS is registered as a limited company in Verdal, Trøndelag with organisation number 935862418. The business is classified under wholesale of other machinery and equipment (NACE 46.640). The company was incorporated in 2025. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp og salg av varer. Videre kan selskapet foreta investering i andre selskaper samt hva dermed står i sammenheng.”. The most recent filed accounts, for the 2025 financial year, show NOK 784,000 in revenue and NOK 84,000 in operating profit.

Key figures · 2025

Revenue
NOK 784,000
Operating profit
NOK 84,000
Equity
NOK 158,000
Est. value
NOK 338,000

Financial health · 2025

Liquidity
1.10
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
30.2%
Good
Equity as a share of total capital

Who owns VK SERTIFISERING AS?

LYSØ VÅG AS
VK SERTIFISERING AS
NOK 784,000 rev. · NOK 84,000 profit

VK SERTIFISERING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about VK SERTIFISERING AS

Who owns VK SERTIFISERING AS?

LYSØ VÅG AS is the largest registered owner, with 50.0%.

What is the revenue of VK SERTIFISERING AS?

VK SERTIFISERING AS had revenue of NOK 784,000 in 2025.

Who is the general manager of VK SERTIFISERING AS?

Ketil Lysø Våg is registered as general manager of VK SERTIFISERING AS.

Where is VK SERTIFISERING AS based?

VK SERTIFISERING AS has its business address in Verdal.

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.