BIZTRAC BETA
Masonry and bricklaying activities

MURER KURT PEDERSEN AS

Org. no. 917543194 Limited company (AS) Ringebu Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 3.6m
Operating profit NOK −262,000
Equity NOK 1.5m
Incorporated 2016
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−262k kr).

MURER KURT PEDERSEN AS is registered as a limited company in Ringebu, Innlandet with organisation number 917543194. The business is classified under masonry and bricklaying activities (NACE 43.910). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Muring- og flislegging, samt annet som naturlig står i den forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.6m in revenue and NOK −262,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.6m
Operating profit
NOK −262,000
Equity
NOK 1.5m
Est. value
NOK 1.9m

Financial health · 2024

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

Who owns MURER KURT PEDERSEN AS?

KURT HALVOR PEDERSEN
MURER KURT PEDERSEN AS
NOK 3.6m rev. · NOK −262,000 profit

MURER KURT PEDERSEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MURER KURT PEDERSEN AS

Who owns MURER KURT PEDERSEN AS?

KURT HALVOR PEDERSEN is the largest registered owner, with 100.0%.

What is the revenue of MURER KURT PEDERSEN AS?

MURER KURT PEDERSEN AS had revenue of NOK 3.6m in 2024.

Who is the general manager of MURER KURT PEDERSEN AS?

Kurt Halvor Pedersen is registered as general manager of MURER KURT PEDERSEN AS.

Where is MURER KURT PEDERSEN AS based?

MURER KURT PEDERSEN AS has its business address in Fåvang.

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.