BIZTRAC BETA
Construction of residential and non-residential buildings

BYGGMESTER SINDRE FOSS HOPLAND AS

Org. no. 931849573 Limited company (AS) Alver Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 344,000
Operating profit NOK 11,000
Equity NOK 115,000
Incorporated 2023
Share capital NOK 30,000

BYGGMESTER SINDRE FOSS HOPLAND AS is registered as a limited company in Alver, Vestland with organisation number 931849573. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Tømrarverksemd, herunder oppføring og utvikling av bygg for sal og utleige. Samt annan verksemd som naturleg har samanheng med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 344,000 in revenue and NOK 11,000 in operating profit.

Key figures · 2025

Revenue
NOK 344,000
Operating profit
NOK 11,000
Equity
NOK 115,000
Est. value
NOK 77,000

Financial health · 2025

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

Who owns BYGGMESTER SINDRE FOSS HOPLAND AS?

MØNEÅS AS
BYGGMESTER SINDRE FOSS HOPLAND AS
NOK 344,000 rev. · NOK 11,000 profit

BYGGMESTER SINDRE FOSS HOPLAND AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BYGGMESTER SINDRE FOSS HOPLAND AS

Who owns BYGGMESTER SINDRE FOSS HOPLAND AS?

MØNEÅS AS is the largest registered owner, with 100.0%.

What is the revenue of BYGGMESTER SINDRE FOSS HOPLAND AS?

BYGGMESTER SINDRE FOSS HOPLAND AS had revenue of NOK 344,000 in 2025.

Where is BYGGMESTER SINDRE FOSS HOPLAND AS based?

BYGGMESTER SINDRE FOSS HOPLAND 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.