BIZTRAC BETA
Technical testing and analysis

SERTIFISERING VEST AS

Org. no. 914983371 Limited company (AS) Kinn Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 2.6m
Operating profit NOK 125,000
Equity NOK 985,000
Incorporated 2015
Share capital NOK 30,000

Signals

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

SERTIFISERING VEST AS is registered as a limited company in Kinn, Vestland with organisation number 914983371. The business is classified under technical testing and analysis (NACE 71.200). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Gi sertifisering, utleie av utstyr og utleie av personell til bedrifter, offentlige og privat personer.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.6m in revenue and NOK 125,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.6m
Operating profit
NOK 125,000
Equity
NOK 985,000
Est. value
NOK 1.1m

Financial health · 2024

Liquidity
1.89
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
53.0%
Very good
Equity as a share of total capital

Who owns SERTIFISERING VEST AS?

HANS-KRISTIAN KRIKEN
SERTIFISERING VEST AS
NOK 2.6m rev. · NOK 125,000 profit

SERTIFISERING VEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SERTIFISERING VEST AS

Who owns SERTIFISERING VEST AS?

HANS-KRISTIAN KRIKEN is the largest registered owner, with 100.0%.

What is the revenue of SERTIFISERING VEST AS?

SERTIFISERING VEST AS had revenue of NOK 2.6m in 2025.

Who is the general manager of SERTIFISERING VEST AS?

Hans-Kristian Kriken is registered as general manager of SERTIFISERING VEST AS.

Where is SERTIFISERING VEST AS based?

SERTIFISERING VEST AS has its business address in Måløy.

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.