BIZTRAC BETA
Masonry and bricklaying activities

VESTVIK MUR OG PUSS AS

Org. no. 935198348 Limited company (AS) Klepp Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 1.3m
Operating profit NOK 206,000
Equity NOK 191,000
Incorporated 2025
Share capital NOK 30,000

VESTVIK MUR OG PUSS AS is registered as a limited company in Klepp, Rogaland with organisation number 935198348. The business is classified under masonry and bricklaying activities (NACE 43.910). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen murerarbeid - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.3m in revenue and NOK 206,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.3m
Operating profit
NOK 206,000
Equity
NOK 191,000
Est. value
NOK 696,000

Financial health · 2025

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

Who owns VESTVIK MUR OG PUSS AS?

JESPER VESTVIK
VESTVIK MUR OG PUSS AS
NOK 1.3m rev. · NOK 206,000 profit

VESTVIK MUR OG PUSS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VESTVIK MUR OG PUSS AS

Who owns VESTVIK MUR OG PUSS AS?

JESPER VESTVIK is the largest registered owner, with 100.0%.

What is the revenue of VESTVIK MUR OG PUSS AS?

VESTVIK MUR OG PUSS AS had revenue of NOK 1.3m in 2025.

Who is the general manager of VESTVIK MUR OG PUSS AS?

Jesper Vestvik is registered as general manager of VESTVIK MUR OG PUSS AS.

Where is VESTVIK MUR OG PUSS AS based?

VESTVIK MUR OG PUSS AS has its business address in Kleppe.

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.