BIZTRAC BETA
Uoppgitt

GISMARVIK MUR AS

Org. no. 930799149 Limited company (AS) Tysvær Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 677,000
Operating profit NOK 245,000
Equity NOK 137,000
Incorporated 2023
Share capital NOK 30,000

GISMARVIK MUR AS is registered as a limited company in Tysvær, Rogaland with organisation number 930799149. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Alt innen mur og ovnsmontering og andre produkter/tjenester som naturlig hører til dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak. Selskapet kan også drive med kjøp/drift av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 677,000 in revenue and NOK 245,000 in operating profit.

Key figures · 2025

Revenue
NOK 677,000
Operating profit
NOK 245,000
Equity
NOK 137,000
Est. value
NOK 756,000

Financial health · 2025

Liquidity
1.31
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
41.9%
Very good
Equity as a share of total capital

Who owns GISMARVIK MUR AS?

ARILD GISMARVIK
GISMARVIK MUR AS
NOK 677,000 rev. · NOK 245,000 profit

GISMARVIK MUR AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about GISMARVIK MUR AS

Who owns GISMARVIK MUR AS?

ARILD GISMARVIK is the largest registered owner, with 80.0%.

What is the revenue of GISMARVIK MUR AS?

GISMARVIK MUR AS had revenue of NOK 677,000 in 2025.

Who is the general manager of GISMARVIK MUR AS?

Arild Gismarvik is registered as general manager of GISMARVIK MUR AS.

Where is GISMARVIK MUR AS based?

GISMARVIK MUR AS has its business address in Aksdal.

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.