BIZTRAC BETA
Other specialised construction activities in construction of buildings

MURMESTER WIIK AS

Org. no. 924456396 Limited company (AS) Alver Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 1.0m
Operating profit NOK −132,000
Equity NOK 309,000
Incorporated 2020
Share capital NOK 30,000

Signals

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

MURMESTER WIIK AS is registered as a limited company in Alver, Vestland with organisation number 924456396. The business is classified under other specialised construction activities in construction of buildings (NACE 43.420). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Murerarbeid og salg av varer og tjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.0m in revenue and NOK −132,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.0m
Operating profit
NOK −132,000
Equity
NOK 309,000
Est. value
NOK 483,000

Financial health · 2025

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

Who owns MURMESTER WIIK AS?

SONDRE OLIVER FINSETH WIIK
MURMESTER WIIK AS
NOK 1.0m rev. · NOK −132,000 profit

MURMESTER WIIK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MURMESTER WIIK AS

Who owns MURMESTER WIIK AS?

SONDRE OLIVER FINSETH WIIK is the largest registered owner, with 100.0%.

What is the revenue of MURMESTER WIIK AS?

MURMESTER WIIK AS had revenue of NOK 1.0m in 2025.

Who is the general manager of MURMESTER WIIK AS?

Sondre Oliver Finseth Wiik is registered as general manager of MURMESTER WIIK AS.

Where is MURMESTER WIIK AS based?

MURMESTER WIIK AS has its business address in Seim.

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.