BIZTRAC BETA
Construction of residential and non-residential buildings

VESTHOR BYGG AS

Org. no. 989401416 Limited company (AS) Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 5.1m
Operating profit NOK 431,000
Equity NOK 946,000
Incorporated 2006
Share capital NOK 100,000

VESTHOR BYGG AS is registered as a limited company in Hå, Rogaland with organisation number 989401416. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2006. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Handel, entreprenør - og byggvirksomhet, salg og kjøp av eiendom, tjenesteyting, utleie av enhver art, kjøp og salg av aksjer, og hva dermed står i forbindelse, herunder deltakelse i beslektet eller annen virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.1m in revenue and NOK 431,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.1m
Operating profit
NOK 431,000
Equity
NOK 946,000
Est. value
NOK 1.9m

Financial health · 2025

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

Who owns VESTHOR BYGG AS?

PER SIGVE VESTLY
VESTHOR BYGG AS
NOK 5.1m rev. · NOK 431,000 profit

VESTHOR BYGG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about VESTHOR BYGG AS

Who owns VESTHOR BYGG AS?

PER SIGVE VESTLY is the largest registered owner, with 50.0%.

What is the revenue of VESTHOR BYGG AS?

VESTHOR BYGG AS had revenue of NOK 5.1m in 2025.

Who is the general manager of VESTHOR BYGG AS?

Per Sigve Vestly is registered as general manager of VESTHOR BYGG AS.

Where is VESTHOR BYGG AS based?

VESTHOR BYGG AS has its business address in Nærbø.

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.