BIZTRAC BETA
Masonry and bricklaying activities

MURMESTRENE GARPESTAD & GAUSLAND AS

Org. no. 968325809 Limited company (AS) Strand Incorporated 1993 Active
Ownership graph ↗
Revenue 2025 NOK 3.4m
Operating profit NOK 350,000
Equity NOK −336,000
Incorporated 1993
Share capital NOK 100,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−336k kr).

MURMESTRENE GARPESTAD & GAUSLAND AS is registered as a limited company in Strand, Rogaland with organisation number 968325809. The business is classified under masonry and bricklaying activities (NACE 43.910). The company was incorporated in 1993. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Murmesterforretning.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.4m in revenue and NOK 350,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.4m
Operating profit
NOK 350,000
Equity
NOK −336,000
Est. value
NOK 1.7m

Financial health · 2024

Liquidity
0.72
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-32.7%
Weak
Equity as a share of total capital

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

Who owns MURMESTRENE GARPESTAD & GAUSLAND AS?

GAUSLAND HOLDING AS
MURMESTRENE GARPESTAD & GAUSLAND AS
NOK 3.4m rev. · NOK 350,000 profit

MURMESTRENE GARPESTAD & GAUSLAND AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MURMESTRENE GARPESTAD & GAUSLAND AS

Who owns MURMESTRENE GARPESTAD & GAUSLAND AS?

GAUSLAND HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of MURMESTRENE GARPESTAD & GAUSLAND AS?

MURMESTRENE GARPESTAD & GAUSLAND AS had revenue of NOK 3.4m in 2025.

Where is MURMESTRENE GARPESTAD & GAUSLAND AS based?

MURMESTRENE GARPESTAD & GAUSLAND AS has its business address in Tau.

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.