BIZTRAC BETA
COMPANY REGISTER PROFILE
933450074 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Civil engineering activities

PROINSPECT AS

Org. no. 933450074 Limited company (AS) Kristiansund Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 12,000
Operating profit NOK −7,000
Equity NOK 420
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−7k kr).

PROINSPECT AS is registered as a limited company in Kristiansund, Møre og Romsdal with organisation number 933450074. 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 30000 shares. The company's stated purpose is: “Inspeksjon av anleggsdeler, bygg og infrastruktur.”. The most recent filed accounts, for the 2025 financial year, show NOK 12,000 in revenue and NOK −7,000 in operating profit.

Key figures · 2025

Revenue
NOK 12,000
Operating profit
NOK −7,000
Equity
NOK 420
Est. value
NOK 13,000

Financial health · 2025

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

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

Who owns PROINSPECT AS?

VIDAR SETTEMSDAL
PROINSPECT AS
NOK 12,000 rev. · NOK −7,000 profit

PROINSPECT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PROINSPECT AS

Who owns PROINSPECT AS?

VIDAR SETTEMSDAL is the largest registered owner, with 100.0%.

What is the revenue of PROINSPECT AS?

PROINSPECT AS had revenue of NOK 12,000 in 2025.

Who is the general manager of PROINSPECT AS?

Vidar Settemsdal is registered as general manager of PROINSPECT AS.

Where is PROINSPECT AS based?

PROINSPECT AS has its business address in Frei.

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.