BIZTRAC BETA
Wholesale of wood, construction materials and sanitary equipment

BETOMUR AS

Org. no. 960670329 Limited company (AS) Bergen Incorporated 1991 Active
Ownership graph ↗
Revenue 2024 NOK 35.8m
Operating profit NOK −1.1m
Equity NOK 3.2m
Incorporated 1991
Employees 8
Share capital NOK 1.2m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,1 mill kr).

BETOMUR AS is registered as a limited company in Bergen, Vestland with organisation number 960670329. The business is classified under wholesale of wood, construction materials and sanitary equipment (NACE 46.830). The company was incorporated in 1991 and has 8 registered employees. Registered share capital is NOK 1.2m, divided into 12200 shares. The company's stated purpose is: “Handelsvirksomhet samt hva dermed står i forbindelse, herunder å delta i andre foretagender med tilsvarende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 35.8m in revenue and NOK −1.1m in operating profit.

Key figures · 2024

Revenue
NOK 35.8m
Operating profit
NOK −1.1m
Equity
NOK 3.2m
Est. value
NOK 13.2m

Financial health · 2024

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

Who owns BETOMUR AS?

WAAGE BEDRIFTSRÅDGIVNING AS
BETOMUR AS
NOK 35.8m rev. · NOK −1.1m profit

BETOMUR AS has 8 registered shareholders:

All shareholders and roles →

Frequently asked questions about BETOMUR AS

Who owns BETOMUR AS?

WAAGE BEDRIFTSRÅDGIVNING AS is the largest registered owner, with 45.9%.

What is the revenue of BETOMUR AS?

BETOMUR AS had revenue of NOK 35.8m in 2024.

Who is the general manager of BETOMUR AS?

Øystein Skarvatun Rygg is registered as general manager of BETOMUR AS.

Where is BETOMUR AS based?

BETOMUR AS has its business address in Bergen.

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.